Repository navigation
fix(knowledge): stop witnessing Cargo.toml, which every release rewrites - #185
Conversation
Two repository-knowledge records (the naming decision and start-here #3) witnessed Cargo.toml. release-please bumps its version on every release PR, so "source witness changed: Cargo.toml" failed release PR #176's Repository pendant source controls. The release's own share build would fail the same way on the tagged tree. No tambo release with a share could ever pass. Both records now point at docs/book/src/compatibility.md, which states the same contract in prose (the caboodle command, crate imports, state paths and vocabulary IRIs remain valid). The records are otherwise unchanged: same kind, type and properties, start-here order 3. A new test refuses any witness on a release-managed file (Cargo.toml, Cargo.lock, CHANGELOG.md, .release-please-manifest.json). It also renders after all four are rewritten. With main's registry restored, that test fails; with this change it passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185RxTpLsPCQFB9ni72Nzac
|
POST-MERGE SOURCE REVIEW — no blocking finding on exact9193dce0ab79fc1a5da1125d2cc20cfe10053c5d/base8ed2f2d8b5fa8cdba2b3ee6d911877d20a460cc3. ONE full two-path inspection by Ian after exactheadcompletegreen. The two decision/start-here records now witness the existing compatibility contract, with exact sourcehash; kind/type/properties/order remain. New guard rejects release-managed witnesses; render still succeeds after all four managedfiles change. Knowledge suite10 cases(1native-schema skip) plus sharepublication12 PASS/HOME157+5CLEAN. Independent inverse restores the old registry against new test: expected1FAIL/0ERROR, then current suitePASS. Timing qualification: liveforge says MERGED154fbb05c6b90948bcf69d2df6e619ad92667123 at2026-10-23T19:01:28Z. Native classification REFUSED PRnotopenandready; retained, no native approval artifact minted, no claim this review authorized that earlier merge. Merge actor identity is sharedGitHubscbrown; actual agent attribution unestablished. No second audit requested. Tim/Wu notified; nextrelease/regeneration/publication acceptance remains separate. |
Problem
Release PR #176 (0.6.0) fails Repository pendant source controls with
source witness changed: Cargo.toml.Two records in
docs/knowledge/repository-knowledge.jsonwitnessCargo.toml, and release-please bumps itsversionon every release PR. The release workflow's share build reads the tagged tree, so it would fail the same check. As things stand, no tambo release can pass this check or publish its share.Change
docs/book/src/compatibility.md. That page states the same contract: thecaboodlecommand, crate imports, state paths and vocabulary IRIs remain valid. Kind, type, properties and order are unchanged.Cargo.toml,Cargo.lock,CHANGELOG.md,.release-please-manifest.json). It also renders successfully after all four are rewritten.Evidence
test-repository-knowledge.py: OK (1 skipped, the native schema arm).test-repository-share-publication.py: OK.After this merges, release-please regenerates #176 from main.
🤖 Generated with Claude Code
https://claude.ai/code/session_0185RxTpLsPCQFB9ni72Nzac