docs apply: the v4 re-baseline refuses a v3 manifest that has minimumRendererVersion #579

Activity

1. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   An independent reproduction, carried over from #581, the duplicate that the #574 design pass found:

   • repo-harness docs/architecture/.projection-manifest.json is archcontext.architecture-docs-projection-manifest/v3 and records "minimumRendererVersion": "archcontext.docs-renderer/v6".
   • architectureDocsProjectionCompatibilityIssues (packages/contracts/src/projection-manifest.ts:506-507) reports "projection manifest floors require the current schema" for any non-v4 manifest with a floor.
   • Two callers refuse on that issue:
     • previousArchitectureDocsProjectionManifest (packages/core/projection-engine/src/index.ts, about :974);
     • assertProjectionWriteCompatibility (packages/core/changeset-engine/src/index.ts:588, :593), which raises AC_PRECONDITION_FAILED / projection-manifest-incompatible.
   • On a throwaway clone of repo-harness at 48cae2d58, docs apply --approved refused until the floor was removed by hand.

   Seat: orchestrator t7
2. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Decision (owner → advisor, pane t12, 2026-11-13; the owner delegated the fix of #579 and #580 to the advisor: "下游提了一个issue，你接手修"). Tier Medium, one GPT review. Part of archctx 0.14.1.

   • Fix it in the shared function, not by reordering one caller. architectureDocsProjectionCompatibilityIssues (packages/contracts/src/projection-manifest.ts:506-507) has two callers that refuse:

     • previousArchitectureDocsProjectionManifest (projection-engine, about :974);
     • assertProjectionWriteCompatibility (changeset-engine :588, :593).

     The rule becomes "floors require a current or superseded declared schema". A floor key with no declared schema, or with an unsupported one, is still refused.

   • Floor semantics. A superseded manifest's floors are evaluated against this engine, the same way as v4 floors. A floor that the engine does not meet still refuses with projection-manifest-incompatible. The floors are not carried into v4: the re-baseline writes a fresh v4 with the floors that this writer sets. The old manifest is not a baseline, so its floors only decide whether this engine may replace it.

   • Tests.

     • Extend the existing re-baseline test. It starts from a real 0.13.0 v3 manifest with minimumRendererVersion archcontext.docs-renderer/v6, as repo-harness's is, runs docs apply --approved, and ends with a v4 manifest.
     • Add one case: a v3 manifest whose floor is above the engine refuses.

   • No compatibility code. No skip flag, no reordering-only fix, no second path.

   Seat: orchestrator t7
3. Ancienttwo

   added a parent issue on Nov 13, 2026

   • 0.14.1: unblock the repo-harness archctx 0.14 pin (#579, #580) #583
4. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Claim: writer and head owner is the Pi worker seat t2k5 (magpie Opus 5.5), on branch fix/579-superseded-floors from main f381b51. Medium tier, one GPT review.

   Seat: orchestrator t7
5. Ancienttwo

   closed this as completedin ee3eaf3on Nov 13, 2026