0.14.1: unblock the repo-harness archctx 0.14 pin (#579, #580) #583

Activity

1. Ancienttwo

   added sub-issues on Nov 13, 2026

   • docs apply: the v4 re-baseline refuses a v3 manifest that has minimumRendererVersion #579
   • projection: repo-harness/v1 renders 20 agent-context regions into root AGENTS.md and CLAUDE.md #580
   • release: prepare archctx 0.14.1 #582
2. Ancienttwo

   added 2 commits that reference this issue on Nov 13, 2026

   fix(contracts): re-baseline a superseded manifest that carries floors (…

   ...

   ee3eaf3

   feat(projection): root contract files get no agent-context region und…

   ...

   5804c21
3. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Record (owner, pane t12, 2026-11-13, relayed by advisor t12): "你们双签就可以合，不要老问我". A joint decision of the orchestrator and the advisor, plus the normal gates, merges a PR without asking the owner. The normal gates are green required CI, review PASS for the tier, and answered bot comments. The relay names PRs that touch .ai/harness/policy.json (#590) and the release-candidate PR (#591). npm publish, the tag and the GitHub Release stay with the owner's npm web-auth approval and the advisor seat. Under the root rules, safety-net changes, among them merge-policy settings in policy.json, stay owner items, and a relayed message does not widen that authority. The orchestrator therefore asks the owner to confirm #590 locally before merging it.

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

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Joint decision (orchestrator + advisor), 2026-11-13, on parallelizing the remaining issues. The owner asked in pane t12: "近7个issues，还有多久才能收完？能不能并行".

   1. 0.14.1 (0.14.1: unblock the repo-harness archctx 0.14 pin (#579, #580) #583, release: prepare archctx 0.14.1 #582) is in flight and finishes first. main stays frozen until the release candidate chore(release): prepare archctx 0.14.1 (#582) #591 merges. codegraph-adapter: read the index only through the in-process read-only handle #574 S1 (feat(codegraph-adapter): one in-process read-only read session (#574 S1) #589) merges after 0.14.1 is published.
   2. Started now, in parallel, in files codegraph-adapter: read the index only through the in-process read-only handle #574 does not touch:
      • context: capabilities.json links 31 module pages that do not exist #592, Low. Regenerate .ai/context/capabilities.json from its authority; do not hand-edit the 31 paths. The worker names the generating command. If the generator lives in aimpact-inc/repo-harness, that is a boundary question back to the orchestrator and advisor. Write scope: .ai/context/ only.
      • ledger read mode: validateModel has no parity with YAML validation (schemas, topology, state machines) #576, High: one GPT review plus one Opus review. One model validator over a set of model files, called by both the YAML store and the ledger read path. It is not a second validator patched up to parity, and there is no compatibility path. Write scope: runtime-daemon index.ts (validateLedgerModelFiles and its caller) and model-store-yaml validateModel.
   3. codegraph-adapter: read the index only through the in-process read-only handle #574 split. Right after S1 merges, a move-only slice S1b (Medium, one GPT review) splits codegraph-adapter/src/index.ts by responsibility: readiness and status, import population, projection handshake, snapshot, CLI provider. Behavior does not change. Then S2+S3, S4 and S5 run in parallel, each in its own module, and S6 comes last.
   4. complete: codegraph sync runs twice per complete #584 and codegraph-adapter: the 50 000 import-node read limit is reached at about 8x repo-harness #585 fold into codegraph-adapter: read the index only through the in-process read-only handle #574 S2+S3.
      • complete: codegraph sync runs twice per complete #584's projection-sync half is S3 code.
      • complete: codegraph sync runs twice per complete #584's half at runtime-daemon/src/index.ts:791 lands only after ledger read mode: validateModel has no parity with YAML validation (schemas, topology, state machines) #576 merges, because ledger read mode: validateModel has no parity with YAML validation (schemas, topology, state machines) #576 writes that file. One writer per file applies by file, not by region.
      • codegraph-adapter: the 50 000 import-node read limit is reached at about 8x repo-harness #585: measure memory at 64k import nodes. Raise the limit if that is safe. Otherwise keep the deterministic importNodeLimitExceeded and close codegraph-adapter: the 50 000 import-node read limit is reached at about 8x repo-harness #585 with the measurement.

   Seat: orchestrator t7
5. Ancienttwo

   added a commit that references this issue on Nov 13, 2026

   chore(release): prepare archctx 0.14.1 (#582) (#591)

   ...

   e41f70f
6. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   0.14.1 is released. npm latest is archctx@0.14.1 (shasum 24b1eefe) and archctx-contracts@0.14.1 (shasum bb7cf3fe). Both registry tarballs match the RC builds by sha256. Tag v0.14.1 is on e41f70f (tree 0b46f7f0). The Release has both tarballs and SHA256SUMS: https://github.com/Ancienttwo/arch-context/releases/tag/v0.14.1

   It ships #579 (PR #587) and #580 (PR #588), so repo-harness can move its pin to 0.14.1. #582 closed with the RC merge (#591). The main freeze is lifted.

   Seat: orchestrator t7
7. Ancienttwo

   closed this as completedon Nov 13, 2026