chore: prepare 0.28.0 release

[mohanagy]

Summary

• Bump @lubab/madar from 0.27.9 to 0.28.0 in package.json and package-lock.json.
• Update README/npm-facing copy with the proof-backed 6/6 public TypeScript explain-runtime legacy benchmark table and scoped caveats.
• Add the 0.28.0 changelog entry and align MCP Registry metadata plus README honesty tests.

Merge order

• This is stacked on Merge next into main for 0.28.0 release #521.
• Merge Merge next into main for 0.28.0 release #521 (next into main) first.
• Then merge this PR so the release metadata commit lands on top of the released code.
• After this PR is merged into main, create/push tag v0.28.0 on the merge commit and publish from main.

Verification

• npm run release:verify
• npm run registry:validate
• npm run typecheck
• npm run build
• CI=1 npx vitest run tests/unit/mcp-registry-metadata.test.ts tests/unit/why-madar-doc.test.ts
• CI=1 npm run test:run (188 files, 2539 passed, 1 skipped)
• npm run pack:dry-run (@lubab/madar@0.28.0)

Summary by CodeRabbit

• Documentation

  • Released version 0.28.0 with updated proof-backed benchmark evidence.
  • Added "What Agents Get" section describing agent-relevant context capabilities.
  • Updated TypeScript benchmark evidence with performance metrics and explicit scope limitations.

• Chores

  • Version bumped to 0.28.0 in package metadata and registry.

• Tests

  • Updated test expectations for new release version and benchmark evidence assertions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0fed968f-e607-4b8a-b81f-f91c3fb1f5a1

📥 Commits

Reviewing files that changed from the base of the PR and between 2199d48 and e1dc751.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• CHANGELOG.md
• README.md
• docs/mcp-registry/server.json
• package.json
• tests/unit/why-madar-doc.test.ts

---

📝 Walkthrough

Walkthrough

This PR prepares the 0.28.0 release by updating public documentation (CHANGELOG and README), bumping version metadata across package files, and adjusting test assertions to validate documentation consistency and benchmark claim integrity.

Changes

0.28.0 Release Preparation

Layer / File(s)	Summary
Release changelog and README documentation CHANGELOG.md, README.md	CHANGELOG.md adds the 0.28.0 release entry (proof-backed public TypeScript benchmark receipts, stricter runtime-proof requirements, evidence-handling fixes). README.md adds proof-backed full_win claim for 6/6 legacy rows, new "What Agents Get" section describing repo context delivery, replaces prior evidence text with TypeScript benchmark table and scope note, updates "What's New" section to 0.28.0.
Version metadata bumps package.json, docs/mcp-registry/server.json	Version field updated from 0.27.9 to 0.28.0 in both package.json and MCP server registry metadata.
Documentation honesty test assertions tests/unit/why-madar-doc.test.ts	Test assertions updated to check for 0.28.0 version references in README stable-release pointers, and updated expectations for new explain-runtime legacy row wording, benchmark evidence table rows, and SPI arms tracking disclaimer.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• mohanagy/madar#334: The main PR follows up on #334's "align public claims with evidence" work by updating README/CHANGELOG and adjusting test expectations for the same explain-runtime evidence/claim-boundary honesty rules (now for v0.28.0).
• mohanagy/madar#506: Both PRs update the README-related evidence/trust-boundary copy and shared tests/unit/why-madar-doc.test.ts assertions, with the main PR's README/test changes building directly on that PR's refresh work.
• mohanagy/madar#475: Both PRs modify tests/unit/why-madar-doc.test.ts to adjust doc "honesty" assertions tied to the README's release-bound explain-runtime evidence text and versioned expectations.

Poem

🐰 A new release hops into view,
With proof-backed claims and evidence true,
Benchmarks shine on six legacy rows,
Version bumps everywhere—watch knowledge flow,
Tests stand guard where claims are made,
Truth in docs, forever displayed! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: prepare 0.28.0 release' directly and clearly summarizes the main change: preparing a release for version 0.28.0.
Description check	✅ Passed	The PR description includes a comprehensive summary of changes, detailed merge/release instructions, and extensive verification commands with results. All required template sections are present and well-filled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-0.28.0

Warning

Review ran into problems

🔥 Problems

Stopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a @coderabbit review after the pipeline has finished.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}