docs(agents): align websources with the shared cross-repo conventions #20
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/cross-repo-conventions-pointer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Addresses #1. Most of the finding was already resolved — this closes the real
remainder.
Already resolved on main (verified, no change needed)
[REMOTE-FORM]— §4 already uses the canonicalssh://git@code.clawdie.si:2222/clawdie/websources.git.scripts/jev-classify.pyalready loads the sharedjev_eval(TypeSafe-first with fallback) viaJEV_TRIAGE_ROOT/PATH, passescaller_attribution, and recordsprovider/provider_attempts/usage/cost. The Vercel-hardcoded transport is gone.DOCUMENTATION_REPOS = ("websources",), i.e. the recommended satelliterole, and §1 already says websources must link to component sources rather
than duplicate their contracts.
python3 colibri/scripts/cross-repo-consistency.py→ 0 findings across 6repos.
Fixed here
classified_by/status, which the sharedgate does not use and this file's own frontmatter does not carry. Now names
source_of_truth/last_verified(30-day window) /verified_by, plusplatform_noteswhere the source touches platform-specific code.that the local never push without explicit instruction rule is stricter
than the shared
main-is-merge-only workflow and wins here.divergence is reconciled canonically instead of silently copied.
wiki 8); a real build produces 98 (agents 57, wiki 10). Corrected, and
reworded so the total reads as a smoke signal rather than a contract.
Verification
npm run check:all✅ (boundaries, links, portal, wiki tests, preview) ·npm run build✅ (5 workspaces, 98 pages) · okf freshness bumped to08.oct.2026.
Not decided here
The
sites/docs↔ component-repodocs/wiki/overlap is left to §1's existingrule (link, don't duplicate). Say the word if you want that stated more
explicitly in §3.