docs(contracts): stop synced contract docs linking to unsynced siblings - #2875
Conversation
docs/contracts/run-contract-v1.md and identity-map-conventions.md are synced to
consumer repos, but carried relative links to research-backplane-contract.md and
langsmith-fleet-v1.md, which are deliberately Workflows-only ("intentionally NOT
synced ... single source of truth", .github/sync-manifest.yml:803-806). In any
consumer the links therefore dangle.
That broke the very first sync PR to deliver these docs to a repo with a
docs-link test: stranske/Collab-Admin#961 failed
tests/test_docs_links.py::test_docs_links_are_resolvable on exactly those three
links, blocking an otherwise config-only sync.
Point the three links at the canonical Workflows URLs instead, and note inline
that those docs are Workflows-only. This keeps the deliberate no-sync decision
intact while making the synced docs self-contained.
Verified with a scan over the compiled manifest: every relative .md link in every
synced doc now resolves to another synced doc. Only these three were broken;
research-backplane-contract.md and langsmith-observability-contract.md keep their
relative links because they are not synced.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 12 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
Workflow source neededPR #2875 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely. Please do one of:
Once a valid source is present, this warning will not be reposted. |
|
Gate fast-pass: docs-only change detected; heavy checks skipped. |
Automated Status SummaryHead SHA: ac0e806
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
There was a problem hiding this comment.
Pull request overview
Updates synced contract documentation so consumer repos don’t receive dangling relative links to Workflows-only (intentionally unsynced) contract siblings, avoiding downstream doc-link test failures in consumers.
Changes:
- Replaces relative links to
research-backplane-contract.mdandlangsmith-fleet-v1.mdwith canonicalgithub.com/stranske/Workflows/blob/main/...URLs in synced docs. - Adds inline “Workflows-only; not synced to participants” notes where the linked targets are intentionally unsynced.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/contracts/run-contract-v1.md | Switches two sibling-doc references from relative to canonical GitHub URLs and adds “Workflows-only” notes. |
| docs/contracts/identity-map-conventions.md | Switches the ownership-doc reference from relative to a canonical GitHub URL. |
Why
docs/contracts/run-contract-v1.mdanddocs/contracts/identity-map-conventions.mdare synced to consumer repos, but they carried relative links toresearch-backplane-contract.mdandlangsmith-fleet-v1.md, which are deliberately not synced —.github/sync-manifest.yml:803-806:So in every consumer those links dangle. It went unnoticed until the first sync PR delivered these docs to a repo that actually tests links: stranske/Collab-Admin#961 failed
tests/test_docs_links.py::test_docs_links_are_resolvableon exactly those three links —— blocking an otherwise config-only sync PR (all four of those docs are absent from Collab-Admin today, so this sync was their first delivery).
What changed
The three links now point at canonical
github.com/stranske/Workflows/blob/main/...URLs, with an inline note that those docs are Workflows-only. This keeps the deliberate no-sync decision fully intact while making the synced docs self-contained.Untouched:
research-backplane-contract.mdandlangsmith-observability-contract.mdkeep their relative links, because they are not synced and their siblings are local to this repo. The bare`research-backplane-contract.md`code reference atrun-contract-v1.md:203is not a link and needed no change.Verification
Rather than fix only the three reported links, I scanned every synced doc against the compiled manifest:
pytest tests/docs/→ 34 passed.Follow-up
Once this merges, Collab-Admin's sync PR needs the refreshed docs to go green — a
maint-68run will update its sync branch.A guard for this class of defect (assert no synced doc relative-links to an unsynced target, using the same compiled-manifest scan) would stop it recurring; not added here to keep the fix reviewable.
🤖 Generated with Claude Code