Skip to content

docs: README and site links for HarnessMD/munder-difflin - #668

Open
chaitanyagiri wants to merge 2 commits into
mainfrom
bob/org-links
Open

chaitanyagiri wants to merge 2 commits into
mainfrom
bob/org-links

Conversation

@chaitanyagiri

Copy link
Copy Markdown
Collaborator

What & why

The public repo moved to the HarnessMD organisation. This points the README and the site at the real address instead of a redirect, and adds a link row and a first paragraph that say what the project is. Markdown, HTML and the blog source only. No app code.

  • README: a link row under the title (Website, Download, Discord, Contributing). The first paragraph keeps "Free, open source and performant" and now names the agent harness, Claude Code, Codex and the ten other engines in the README's own Supported agents list. All 12 owner links now point at HarnessMD, badges included. The 6 mentions that mean the current release go from 0.5.3 to 0.5.5: the version badge, the download line, three release links and "builds of". The 6 that date a feature stay at 0.5.3, because those features shipped in 0.5.3.
  • docs/ and blog/src: chaitanyagiri/munder-difflin becomes HarnessMD/munder-difflin, on URLs only, in 364 files. blog/src changes too, so the next blog build does not undo docs/blog.
  • Not touched: docs/hires, docs/hero.json and docs/model-catalog.json, which the shipped app reads. That change goes in 0.5.6 with its own test. docs/r is also left alone.
  • CONTRIBUTING.md: the dead #what-gets-a-pr-closed anchor now goes to #where-the-bar-is, and "Questions" links to Discussions and Issues instead of ../../issues.
  • Issue forms: the version placeholders move from 0.4.5 and 0.4.6 to 0.5.5.

Type of change

  • Bug fix
  • New feature
  • Refactor / cleanup
  • Docs
  • Build / CI

Evidence

Before

README top before

After

README top after

How I tested it

  • OS: macOS
  • Steps:
    1. A script compared every changed line in docs/ and blog/src with its old line. 532 lines changed, and 0 of them differ by anything other than the owner string. No file changed its line count.
    2. A request to every unique URL on a changed line (81 URLs), following redirects: all 81 returned 200, including releases/tag/v0.5.5.
    3. npm run check:links: "release links consistent at v0.4.6".
    4. A grep of the diff for munder-difflin-pro: 0 hits. No file changed outside README.md, CONTRIBUTING.md, .github/ISSUE_TEMPLATE, docs/ and blog/src.
    5. Typecheck was not run locally (the worktree has no node_modules). CI runs Typecheck and Build on this PR.

Checklist

  • Before and after evidence is attached above, under both headings.
  • npm run typecheck passes. (CI)
  • npm run test:focused passes. (no code changed)
  • npm run build succeeds. (CI)
  • This PR is one change: the address move and the README top.
  • I read the diff myself before opening this.
  • No new UI.
  • No new art.

🤖 Generated with Claude Code

chaitanyagiri and others added 2 commits October 2, 2026 15:49
The public repo moved to the HarnessMD organisation. Links now go to the
real address instead of a redirect.

README: a link row under the title (site, download, Discord, contributing),
a first paragraph that names the agent harness and the engines, the 12
owner links, and the 6 mentions that mean the current release moved from
0.5.3 to 0.5.5. Mentions that date a feature stay at 0.5.3.

docs/ and blog/src: the owner swap only, on URLs. blog/src is changed too
so the next blog build does not undo docs/blog. docs/hires, hero.json and
model-catalog.json are left alone because the shipped app reads them.

CONTRIBUTING: the dead #what-gets-a-pr-closed anchor and the Questions
link. Issue forms: version placeholders to 0.5.5.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant