@orion-agents/orion-code 0.1.9 → 0.2.0

package/docs/plan/v0.2.0-release-checklist.md

@@ -0,0 +1,91 @@
+# Orion Code v0.2.0 release checklist
+
+Status: `candidate`; this checklist distinguishes implementation evidence from commit, CI, tag,
+GitHub Release, npm publication, and dist-tag promotion. Pending delivery receipts are not passes.
+
+## Identity and package
+
+- [x] Branch is `v0.2.0`; `package.json` and root `npm-shrinkwrap.json` identity are `0.2.0`.
+- [x] README, migration guide, CHANGELOG, main plan, and package manifest describe the same breaking
+      runtime and command surface.
+- [ ] Release artifact is built from a clean immutable source SHA.
+- [ ] Exact tarball contains only the allowlisted package manifest and is within entry/size budgets.
+- [ ] `release:check --expected-version 0.2.0` passes against that exact source.
+
+## Core goal gates (G1–G6)
+
+- [x] **G1 Lean by default:** frozen v0.1.9 baseline is 33 schemas / 20,596 bytes; the ordinary
+      v0.2.0 coding step exposes 7 schemas / 3,947 bytes. Unselected Skill definition/resource and
+      MCP connection/process/socket counts are zero.
+- [x] **G2 Higher task efficiency:** the deterministic successful-task corpus records no success
+      or false-completion regression, no model-request growth, and a successful-task input-token
+      median reduction above 30%.
+- [x] **G3 One trustworthy execution path:** root, nested batch, long-tail, MCP, Skill, and subagent
+      calls use Capability → Policy → Approval → Sandbox → Execute with durable lineage.
+- [x] **G4 Crash-safe recovery:** event projection, TurnCommit, Compact, Goal, importer, and
+      parent/child fork boundaries have deterministic crash/replay tests.
+- [x] **G5 Predictable interaction:** TUI, terminal, print, Goal, Plan, Compact, and subagent share
+      versioned runtime events and bounded replay/backpressure.
+- [x] **G6 Maintainable foundation:** public/tarball legacy owners are absent; composition has one
+      runtime, one Agent Loop implementation, and one TaskContext completion owner; 1,000 scope
+      churn leaves no fake resources.
+
+The checked implementation items above still require the source and artifact gates below before
+release. Machine receipts, not this prose, are authoritative.
+
+## Source gates
+
+- [ ] `npm run lint`
+- [ ] `npm run build`
+- [ ] `npm test -- --runInBand`
+- [ ] `npm run test:coverage -- --runInBand` with the configured threshold
+- [ ] `npm run test:harness-confluence`
+- [ ] `npm run bench:harness:compare -- <baseline> <candidate>`
+- [ ] `npm run bench:harness:eval -- --baseline <baseline> --candidate <candidate>`
+- [ ] `npm run prepublishOnly`
+- [ ] `git diff --check`
+- [ ] clean release worktree
+
+## Exact artifact and runtime matrix
+
+One tarball SHA must be built once and installed unchanged in every runtime job. Rebuilding per Node
+version is not equivalent evidence.
+
+- [ ] Node 20 exact-tarball matrix passes all required probes.
+- [ ] Node 22 exact-tarball matrix passes all required probes.
+- [ ] Node 24 exact-tarball matrix passes all required probes.
+- [ ] Each matrix verifies install/package/bin identity, version/help, public exports, built-in Skill
+      assets, and native SQLite.
+- [ ] Installed-tarball TUI, terminal, print, Goal, subagent, Skill, MCP, and compact/resume journeys
+      pass with runner and target digests bound to the tarball.
+- [ ] `ReleaseReceiptV1` verifies artifact, all runtime matrices, benchmark comparison, task eval,
+      confluence, and full-test receipt; missing, skipped, dirty, mismatched, or failed evidence is
+      No-Go.
+
+## Acceptance contract
+
+- [x] AC1–AC22 have executable contract, integration, chaos, architecture, or product E2E coverage.
+- [x] PLAN writes a PlanReceipt in the same TurnCommit and implementation starts only on the next
+      logical turn.
+- [x] A productive Goal can continue beyond 20 turns, completes through evidence audit, and exits
+      automatically; no fixed continuation-count stop or ghost shutdown continuation remains.
+- [x] Nested `batch_read` children re-enter ToolGateway under the same frozen snapshot and retain
+      parent/child invocation lineage.
+- [x] Legacy session cutover is side-by-side, atomic at the index, replay-verified, and fail closed.
+- [x] Public exports/config/help do not expose a plugin SDK, marketplace, service locator, dynamic
+      third-party JavaScript loader, or legacy Harness owner.
+
+## Delivery receipts
+
+| Receipt               | Expected evidence                              | Result  |
+| --------------------- | ---------------------------------------------- | ------- |
+| Source SHA            | immutable commit on `v0.2.0`                   | pending |
+| Pull request          | URL, head SHA, required CI conclusion          | pending |
+| Git tag               | signed/annotated `v0.2.0` at the release SHA   | pending |
+| GitHub Release        | release URL bound to the same tag              | pending |
+| npm immutable version | registry readback for `@orion-agents/orion-code@0.2.0` | pending |
+| npm dist-tag          | explicitly authorized tag readback             | pending |
+| ReleaseReceiptV1      | verified digest and `status=go`                | pending |
+
+Rollback follows [the v0.1.9 → v0.2.0 migration guide](../migration/v0.1.9-to-v0.2.0.md). Never
+infer npm publication from a Git tag, or a clean CI run from a locally built tarball.

package/docs/readme.md

@@ -6,7 +6,8 @@
   direction, and product/runtime contracts.
 - [`goals/`](goals/orion-code-项目级目标.md) — durable product goals and Goal evidence/recovery
   guidance.
-- [`plan/`](plan/v0.1.9-plan.md) — active execution plans, current release gates, and future roadmap.
+- [`plan/`](plan/v0.2.0-dsh-harness-redesign-plan.md) — active execution plans, current release
+  gates, and future roadmap.
 - [`archive/releases/v0.1.x/`](archive/releases/v0.1.x/README.md) — immutable historical plans,
   audits, freeze boundaries, and release receipts.
 - `test/` — maintained manual test references that do not belong in the Jest suite.
@@ -17,11 +18,10 @@ The repository release history is canonical in [`CHANGELOG.md`](../CHANGELOG.md)
 link into the archive, but historical evidence is not moved back into `plan/` merely to satisfy an
 old relative path.
 
-## v0.1.9 release set
+## v0.2.0 release set
 
-- [Autonomous agent plan](plan/v0.1.9-plan.md)
-- [Mature-agent Compact benchmark](architecture/compact-benchmark.md)
-- [Health ledger](plan/v0.1.9-health-ledger.md)
-- [Release checklist](plan/v0.1.9-release-checklist.md)
-- [Migration and rollback](migration/v0.1.8-to-v0.1.9.md)
-- [Durable product goal](goals/v0.1.9-autonomous-agent-goal.md)
+- [DSH + Codex-informed Lean Harness redesign](plan/v0.2.0-dsh-harness-redesign-plan.md)
+- [Release checklist](plan/v0.2.0-release-checklist.md)
+- [Migration and rollback](migration/v0.1.9-to-v0.2.0.md)
+- [DSH architecture reference](architecture/dsh/DeepSeek-Harness与Cordis插件机制科普.md)
+- [Durable product goal](goals/orion-code-项目级目标.md)