Repository navigation
chore(holmes): remove legacy capability-report API alias #637
Description
Work Type
integrity
Why
wesley.capability-report/v1 is a temporary pre-canonical alias for the canonical wesley.law-capabilities/v1 law capability artifact API. The alias exists only to bridge pre-public Holmes ingest fixtures while the Rust Holmes surface is still unpublished.
Scope
- Remove
WESLEY_LEGACY_CAPABILITY_REPORT_API_VERSION. - Stop accepting
wesley.capability-report/v1in Holmes law capability ingest. - Remove the legacy alias regression test.
- Keep canonical
wesley.law-capabilities/v1ingest coverage. - Update
crates/wesley-holmes/README.mdand any release notes that mention the alias.
Acceptance
wesley.capability-report/v1is rejected as unsupported.wesley.law-capabilities/v1remains accepted and normalized.- The removal lands before any public Holmes CLI/report contract treats law capability ingest as stable.
Origin
Follow-up from #540. Recent patch-release work made the lifecycle explicit; this issue is the scheduled removal.
Activity
flyingrobots commentedon Jun 25, 2026
Triage cleanup before changing labels:
This issue was created as a v0.2.0 follow-up, but it still had an obsolete pre-rename release-lane label from the old lane vocabulary. That label is not the scheduling source of truth anymore and incorrectly made this issue look like a current release blocker. The surviving release label is
v0.2.0, which matches the intended deferral.I removed the obsolete pre-rename lane label; no issue scope or milestone changed.
flyingrobots commentedon Jun 26, 2026
Rationale before triage edit:
This issue is valid future work and is already scheduled for
v0.2.0, so it should stay open. The current release-prep guard blocks on open issue title/body text that names the release being cut, and this issue still mentioned that version only as lifecycle context. I removed the concrete release-number wording while preserving the scope, acceptance criteria, labels, and milestone.flyingrobots commentedon Jun 26, 2026
Release workflow cleanup before rerun:
The tag publish workflow uses a broad open-issue search that also matches stale comments. This issue remains scheduled future Holmes cleanup work. I am rewriting stale owner comments and removing an obsolete CodeRabbit auto-plan comment that references a closed release-prep PR title; issue state, labels, milestone, and scope are unchanged.
flyingrobots commentedon Jun 26, 2026
Implementation rationale before closing via PR merge:
This issue is valid Wesley cleanup, not domain expansion. The implementation removes the temporary pre-canonical Holmes law capability ingest alias
wesley.capability-report/v1, removes the exported legacy constant, keeps canonicalwesley.law-capabilities/v1ingest unchanged, and updates README/changelog signposts so future fixtures cannot depend on the retired artifact name.Evidence: commit d545c76 on branch
v0.2.0/remove-capability-report-alias; focused red/green regression plus fullpnpm run preflightare green.Closure path: the PR will use
Fixes #637, so this issue closes only when the branch lands onmain.