@zhivex-ai/harness 1.0.0 → 1.1.0-rc.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (181) hide show
  1. package/CHANGELOG.md +97 -1
  2. package/README.md +52 -306
  3. package/SECURITY.md +1 -1
  4. package/SUPPORT.md +7 -3
  5. package/benchmarks/README.md +3 -3
  6. package/contracts/client-protocol-v1.schema.json +341 -0
  7. package/contracts/public-api.json +100 -1
  8. package/contracts/stable-api-signatures.json +14 -14
  9. package/dist/approval-diff.d.ts +45 -0
  10. package/dist/approval-history.d.ts +38 -0
  11. package/dist/approval-preview.d.ts +26 -0
  12. package/dist/cli-credentials.d.ts +38 -0
  13. package/dist/cli-help.d.ts +3 -0
  14. package/dist/cli-options.d.ts +1 -1
  15. package/dist/cli-stream.d.ts +3 -3
  16. package/dist/cli.d.ts +15 -69
  17. package/dist/cli.js +13796 -10032
  18. package/dist/client-contract.d.ts +208 -0
  19. package/dist/console-commands.d.ts +6 -0
  20. package/dist/console-context.d.ts +5 -1
  21. package/dist/console-input.d.ts +44 -4
  22. package/dist/console-model-catalog.d.ts +25 -0
  23. package/dist/console-navigation.d.ts +27 -0
  24. package/dist/console-presentation.d.ts +18 -0
  25. package/dist/console-welcome.d.ts +13 -0
  26. package/dist/execution-environment.d.ts +4 -0
  27. package/dist/harness.d.ts +3 -0
  28. package/dist/hostile-repository-demo.js +1913 -798
  29. package/dist/index.d.ts +7 -0
  30. package/dist/index.js +7908 -6330
  31. package/dist/local-service.d.ts +34 -0
  32. package/dist/operations.d.ts +23 -1
  33. package/dist/orchestration.d.ts +3 -0
  34. package/dist/persistence-secrets.d.ts +2 -0
  35. package/dist/recorded-workspace.d.ts +4 -0
  36. package/dist/run-document.d.ts +91 -0
  37. package/dist/runtime-policy.d.ts +4 -4
  38. package/dist/service-cli.d.ts +2 -0
  39. package/dist/service-cli.js +10858 -0
  40. package/dist/service-client-cli.d.ts +2 -0
  41. package/dist/service-events.d.ts +50 -0
  42. package/dist/sessions.d.ts +3 -0
  43. package/dist/sqlite-access.d.ts +26 -0
  44. package/dist/sqlite-database.d.ts +2 -0
  45. package/dist/state-backup.d.ts +8 -0
  46. package/dist/task-memory.d.ts +2 -2
  47. package/dist/terminal-continuation.d.ts +3 -0
  48. package/dist/terminal-markdown.d.ts +1 -0
  49. package/dist/terminal-ui.d.ts +5 -0
  50. package/dist/usage-ledger.d.ts +84 -0
  51. package/dist/verify-historical-migrations.js +5699 -5191
  52. package/dist/workspace.d.ts +22 -0
  53. package/dist/zhx.js +13796 -10032
  54. package/docs/CLI.md +136 -30
  55. package/docs/CLIENT_PROTOCOL.md +212 -0
  56. package/docs/CREDENTIALS.md +59 -0
  57. package/docs/DURABLE_OPERATIONS.md +2 -2
  58. package/docs/FIRST_USE.md +82 -0
  59. package/docs/FIRST_USE_EXAMPLE.md +40 -0
  60. package/docs/HOSTILE_REPOSITORY_DEMO.md +1 -1
  61. package/docs/LOCAL_SERVICE.md +142 -0
  62. package/docs/README.md +24 -23
  63. package/docs/THREAT_MODEL.md +1 -1
  64. package/docs/TIME_TO_SAFE_FIX.md +2 -2
  65. package/docs/USAGE.md +181 -0
  66. package/evaluations/daily-cli-cohort.json +33 -0
  67. package/evaluations/representative-assembly-matrix.json +19 -1
  68. package/examples/README.md +26 -0
  69. package/examples/first-use/greeting.test.ts +3 -0
  70. package/examples/first-use/greeting.ts +1 -0
  71. package/examples/first-use/package.json +7 -0
  72. package/package.json +34 -9
  73. package/ROADMAP.md +0 -414
  74. package/benchmarks/baselines/context-navigation-2026-09-09.json +0 -94
  75. package/benchmarks/baselines/efficiency-2026-09-08.json +0 -233
  76. package/benchmarks/baselines/external-final-2026-09-08.json +0 -588
  77. package/benchmarks/baselines/external-intermediate-2026-09-08.json +0 -116
  78. package/benchmarks/baselines/external-matched-openai-2026-09-08.json +0 -1922
  79. package/benchmarks/baselines/external-matched-qwen-2026-09-08.json +0 -1706
  80. package/benchmarks/baselines/external-pilot-2026-09-08.json +0 -439
  81. package/benchmarks/baselines/external-qwen-flash-2026-09-08.json +0 -1570
  82. package/benchmarks/baselines/external-qwen-remediation-2026-09-09.json +0 -1509
  83. package/benchmarks/baselines/external-qwen-sdk-114-progress-2026-09-09.json +0 -2509
  84. package/benchmarks/baselines/external-sdk-upgrade-2026-09-08.json +0 -564
  85. package/benchmarks/baselines/external-verifier-recovery-2026-09-09.json +0 -794
  86. package/benchmarks/baselines/full-harness-review-2026-09-10.json +0 -134
  87. package/benchmarks/baselines/harness-audit-2026-09-09.json +0 -136
  88. package/benchmarks/baselines/harness-remediation-2026-09-09.json +0 -160
  89. package/benchmarks/baselines/oci-remediation-2026-09-10.json +0 -535
  90. package/benchmarks/baselines/rc14-holdout-2026-09-10.json +0 -854
  91. package/benchmarks/baselines/repair-architecture-audit-2026-09-09.json +0 -75
  92. package/benchmarks/baselines/time-to-safe-fix-live-expanded-2026-08-21.json +0 -186
  93. package/benchmarks/baselines/time-to-safe-fix-live-smoke-2026-08-21.json +0 -186
  94. package/docs/GA_READINESS.md +0 -29
  95. package/docs/GEMINI_1_0_DECISION.md +0 -9
  96. package/docs/LIVE_CERTIFICATION.md +0 -107
  97. package/docs/RC13_SECURITY_REVIEW.md +0 -28
  98. package/docs/RC14_DELEGATED_SECURITY_DECISION.md +0 -80
  99. package/docs/RC14_SECURITY_REVIEW.md +0 -40
  100. package/docs/RELEASE.md +0 -96
  101. package/docs/ROLLBACK.md +0 -9
  102. package/docs/SECURITY_REVIEW_EVIDENCE.md +0 -17
  103. package/docs/ga-readiness.json +0 -366
  104. package/docs/reports/EFFICIENCY_REVIEW.md +0 -156
  105. package/docs/reports/EXTERNAL_COMPARISON.md +0 -434
  106. package/docs/reports/FULL_HARNESS_REVIEW_2026-09-10.md +0 -200
  107. package/docs/reports/GA_BUDGET_REMEDIATION_2026-09-19.md +0 -38
  108. package/docs/reports/GA_REPAIR_RECOVERY_2026-09-19.md +0 -700
  109. package/docs/reports/GA_VALIDATION_2026-09-19.md +0 -111
  110. package/docs/reports/HARNESS_ARCHITECTURE_REVIEW_2026-09-09.md +0 -202
  111. package/docs/reports/HARNESS_AUDIT_2026-09-09.md +0 -306
  112. package/docs/reports/HARNESS_REMEDIATION_2026-09-09.md +0 -74
  113. package/docs/reports/HARNESS_REMEDIATION_2026-09-10.md +0 -90
  114. package/docs/reports/MODEL_COMPARISON_2026-09-09.md +0 -184
  115. package/docs/reports/QWEN_REMEDIATION_COMPARISON_2026-09-09.md +0 -142
  116. package/docs/reports/RC14_VALIDATION_2026-09-10.md +0 -45
  117. package/docs/reports/README.md +0 -26
  118. package/docs/reports/evidence/ga-budget-remediation-2026-09-19.json +0 -133
  119. package/docs/reports/evidence/ga-catalog-ablation-2026-09-19.json +0 -699
  120. package/docs/reports/evidence/ga-catalog-ablation-plan-2026-09-19.json +0 -40
  121. package/docs/reports/evidence/ga-catalog-observed-2026-09-19.json +0 -985
  122. package/docs/reports/evidence/ga-catalog-observed-plan-2026-09-19.json +0 -28
  123. package/docs/reports/evidence/ga-catalog-observed-status-2026-09-19.json +0 -15
  124. package/docs/reports/evidence/ga-complete-local-check-2026-09-19.json +0 -47
  125. package/docs/reports/evidence/ga-completion-reminder-2026-09-19.json +0 -22
  126. package/docs/reports/evidence/ga-fresh-cohort-plan-2026-09-19.json +0 -54
  127. package/docs/reports/evidence/ga-fresh-cohort-preparation-2026-09-19.json +0 -242
  128. package/docs/reports/evidence/ga-fresh-cohort-result-2026-09-19.json +0 -4318
  129. package/docs/reports/evidence/ga-local-validation-followup-2026-09-19.json +0 -66
  130. package/docs/reports/evidence/ga-node-consumers-2026-09-19.json +0 -31
  131. package/docs/reports/evidence/ga-package-content-validation-2026-09-19.json +0 -22
  132. package/docs/reports/evidence/ga-plan-completion-2026-09-19.json +0 -39
  133. package/docs/reports/evidence/ga-plan-reserve-2026-09-19.json +0 -573
  134. package/docs/reports/evidence/ga-plan-reserve-plan-2026-09-19.json +0 -24
  135. package/docs/reports/evidence/ga-plan-transition-2026-09-19.json +0 -19
  136. package/docs/reports/evidence/ga-private-verifier-plan-2026-09-19.json +0 -24
  137. package/docs/reports/evidence/ga-private-verifier-root-cause-2026-09-19.json +0 -41
  138. package/docs/reports/evidence/ga-published-sdk-2026-09-19.json +0 -35
  139. package/docs/reports/evidence/ga-python-checkout-imports-2026-09-19.json +0 -95
  140. package/docs/reports/evidence/ga-python-origin-delivery-2026-09-19.json +0 -211
  141. package/docs/reports/evidence/ga-python-origin-delivery-plan-2026-09-19.json +0 -27
  142. package/docs/reports/evidence/ga-qwen-patched-package-2026-09-19.json +0 -1092
  143. package/docs/reports/evidence/ga-qwen-patched-package-plan-2026-09-19.json +0 -18
  144. package/docs/reports/evidence/ga-qwen-published-2026-09-19.json +0 -571
  145. package/docs/reports/evidence/ga-qwen-published-plan-2026-09-19.json +0 -18
  146. package/docs/reports/evidence/ga-qwen-tool-choice-2026-09-19.json +0 -85
  147. package/docs/reports/evidence/ga-qwen-tool-choice-patched-2026-09-19.json +0 -85
  148. package/docs/reports/evidence/ga-recovery-development-2026-09-19.json +0 -1066
  149. package/docs/reports/evidence/ga-recovery-graded-development-2026-09-19.json +0 -1313
  150. package/docs/reports/evidence/ga-recovery-graded-v2-2026-09-19.json +0 -1151
  151. package/docs/reports/evidence/ga-recovery-v3-2026-09-19.json +0 -3943
  152. package/docs/reports/evidence/ga-recovery-v4-2026-09-19.json +0 -1055
  153. package/docs/reports/evidence/ga-recovery-v5-2026-09-19.json +0 -1245
  154. package/docs/reports/evidence/ga-recovery-v6-2026-09-19.json +0 -699
  155. package/docs/reports/evidence/ga-recovery-v7-2026-09-19.json +0 -854
  156. package/docs/reports/evidence/ga-recovery-v8-2026-09-19.json +0 -596
  157. package/docs/reports/evidence/ga-required-delivery-2026-09-19.json +0 -25
  158. package/docs/reports/evidence/ga-required-delivery-live-2026-09-19.json +0 -1337
  159. package/docs/reports/evidence/ga-required-delivery-live-plan-2026-09-19.json +0 -25
  160. package/docs/reports/evidence/ga-retained-candidate-grading-2026-09-19.json +0 -30
  161. package/docs/reports/evidence/ga-tool-selection-live-2026-09-19.json +0 -559
  162. package/docs/reports/evidence/ga-tool-selection-live-plan-2026-09-19.json +0 -28
  163. package/docs/reports/evidence/ga-tool-selection-recovery-2026-09-19.json +0 -27
  164. package/docs/reports/evidence/ga-validation-2026-09-19.json +0 -236
  165. package/docs/reports/evidence/ga-verifier-discovery-live-2026-09-19.json +0 -1369
  166. package/docs/reports/evidence/ga-verifier-discovery-plan-2026-09-19.json +0 -29
  167. package/docs/reports/evidence/ga-verifier-failure-identification-2026-09-19.json +0 -30
  168. package/docs/reports/evidence/ga-verifier-feedback-2026-09-19.json +0 -65
  169. package/docs/reports/evidence/ga-verifier-hints-live-2026-09-19.json +0 -1297
  170. package/docs/reports/evidence/ga-verifier-hints-plan-2026-09-19.json +0 -27
  171. package/docs/reports/evidence/ga-work-boundary-context-analysis-2026-09-19.json +0 -113
  172. package/docs/reports/evidence/ga-work-boundary-live-2026-09-19.json +0 -301
  173. package/docs/reports/evidence/ga-work-boundary-live-plan-2026-09-19.json +0 -84
  174. package/docs/reports/evidence/ga-work-budget-planning-2026-09-19.json +0 -32
  175. package/docs/reports/evidence/ga-working-context-2026-09-19.json +0 -22
  176. package/docs/reports/evidence/rc14-delegated-security-review-2026-09-20.json +0 -81
  177. package/docs/reports/evidence/rc14-ga-gate-2026-09-20.json +0 -18
  178. package/docs/reports/evidence/rc14-representative-2026-09-20.json +0 -509
  179. package/docs/reports/evidence/rc14-security-regressions-2026-09-20.json +0 -64
  180. package/docs/reports/evidence/security-current-2026-09-19.json +0 -91
  181. package/docs/reports/evidence/security-remediation-2026-09-19.json +0 -97
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zhivex-ai/harness",
3
- "version": "1.0.0",
3
+ "version": "1.1.0-rc.2",
4
4
  "description": "Governed, provider-portable runtime for coding agents with durable approvals and isolated repository execution.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -49,24 +49,43 @@
49
49
  "files": [
50
50
  "dist",
51
51
  "README.md",
52
- "ROADMAP.md",
53
52
  "CHANGELOG.md",
54
53
  "SECURITY.md",
55
54
  "SUPPORT.md",
56
55
  "LICENSE",
57
- "docs",
56
+ "docs/CHANGE_ENVELOPES.md",
57
+ "docs/CLI.md",
58
+ "docs/CLIENT_PROTOCOL.md",
59
+ "docs/CONTEXT_ENGINEERING.md",
60
+ "docs/CREDENTIALS.md",
61
+ "docs/DEPRECATIONS.md",
62
+ "docs/DURABLE_OPERATIONS.md",
63
+ "docs/EXECUTION_ENVIRONMENTS.md",
64
+ "docs/EXTENSIBILITY.md",
65
+ "docs/FIRST_USE.md",
66
+ "docs/FIRST_USE_EXAMPLE.md",
67
+ "docs/HOSTILE_REPOSITORY_DEMO.md",
68
+ "docs/LOCAL_SERVICE.md",
69
+ "docs/PUBLIC_SECURITY.md",
70
+ "docs/README.md",
71
+ "docs/REPOSITORY_EDITING.md",
72
+ "docs/STABILITY.md",
73
+ "docs/SUPPORT_MATRIX.md",
74
+ "docs/THREAT_MODEL.md",
75
+ "docs/TIME_TO_SAFE_FIX.md",
76
+ "docs/USAGE.md",
77
+ "docs/support-matrix.json",
58
78
  "contracts",
59
79
  "examples",
60
80
  "fixtures",
61
81
  "evaluations/*.json",
62
82
  "evaluations/*.jsonl",
63
- "benchmarks/README.md",
64
- "benchmarks/baselines/*.json"
83
+ "benchmarks/README.md"
65
84
  ],
66
85
  "scripts": {
67
- "dev": "bun run src/cli.ts",
86
+ "dev": "bun run build && node --env-file-if-exists=.env dist/cli.js",
68
87
  "start": "node dist/cli.js",
69
- "build": "bun run scripts/clean-dist.ts && bun build ./src/index.ts ./src/cli.ts --outdir ./dist --target node --packages external && cp ./dist/cli.js ./dist/zhx.js && bun build ./scripts/verify-historical-migrations.ts --outfile ./dist/verify-historical-migrations.js --target node --packages external && bun build ./scripts/hostile-repository-demo.ts --outfile ./dist/hostile-repository-demo.js --target node --packages external && tsc --emitDeclarationOnly",
88
+ "build": "bun run scripts/clean-dist.ts && bun build ./src/index.ts ./src/cli.ts ./src/service-cli.ts --outdir ./dist --target node --packages external && cp ./dist/cli.js ./dist/zhx.js && bun build ./scripts/verify-historical-migrations.ts --outfile ./dist/verify-historical-migrations.js --target node --packages external && bun build ./scripts/hostile-repository-demo.ts --outfile ./dist/hostile-repository-demo.js --target node --packages external && tsc --emitDeclarationOnly",
70
89
  "prepack": "bun run build",
71
90
  "docs:check": "bun run scripts/check-docs.ts",
72
91
  "contract:check": "bun run scripts/check-1-0-readiness.ts",
@@ -108,7 +127,10 @@
108
127
  "evaluate:continuity": "bun test tests/compaction.test.ts tests/harness.test.ts",
109
128
  "benchmark:swebench": "bun run scripts/benchmark-swebench.ts",
110
129
  "benchmark:swebench:test": "bun test tests/swebench.test.ts",
111
- "typecheck:tooling": "tsc -p tsconfig.tooling.json"
130
+ "typecheck:tooling": "tsc -p tsconfig.tooling.json",
131
+ "service": "node dist/service-cli.js",
132
+ "smoke:console": "bun run build && python3 scripts/console-pty-smoke.py && python3 scripts/console-entry-smoke.py",
133
+ "smoke:credentials": "node --experimental-strip-types scripts/credential-store-smoke.ts"
112
134
  },
113
135
  "dependencies": {
114
136
  "@zhivex-ai/agents": "1.8.0",
@@ -133,5 +155,8 @@
133
155
  "node": ">=22.13.0",
134
156
  "bun": ">=1.4.0"
135
157
  },
136
- "packageManager": "bun@1.4.0"
158
+ "packageManager": "bun@1.4.0",
159
+ "optionalDependencies": {
160
+ "@napi-rs/keyring": "2.1.0"
161
+ }
137
162
  }
package/ROADMAP.md DELETED
@@ -1,414 +0,0 @@
1
- # Zhivex Harness Roadmap
2
-
3
- - Status: active
4
- - Baseline date: 2026-08-21
5
-
6
- This roadmap takes the harness from its `0.1.0` MVP to a stable CLI and library contract. The `0.2.0` source baseline is tagged locally, `0.3.0` and `0.4.0` are private checkpoints, and `0.5.0` through `0.11.1` are published on npm. Version `0.11.1` delivers file and release hardening without a `0.11.x` contract change; registry publication, supply-chain provenance, and provider certification remain separate evidence boundaries. Releases are ordered by dependency and safety risk, not by calendar date. A version ships only when its exit criteria are satisfied.
7
-
8
- Version `1.0.0` is the local source release candidate. It is not yet tagged or published as a new artifact. Its protected stable certification and publication remain pending; published RC.14 evidence supports preparation, not a claim that stable bytes have shipped.
9
-
10
- ## Planning principles
11
-
12
- RC.13 is published to npm `next` with 42/42 representative cases, protected live certification, and independently verified registry integrity and SLSA provenance. Its [reviewer dossier](docs/RC13_SECURITY_REVIEW.md) remains historical context.
13
-
14
- RC.14 is published to npm `next` with all protected live gates and 42/42 representative cases passed; independent verification matched registry integrity and SLSA provenance. RC.14 now has a completed Codex security review under an explicit [user-delegated AI exception](docs/RC14_DELEGATED_SECURITY_DECISION.md), with no identified open critical/high findings. This is not an independent human audit; use the [current reviewer dossier](docs/RC14_SECURITY_REVIEW.md). The separate failed exploratory SWE-bench cohort is preserved and does not become passing evidence.
15
-
16
- - Make the harness distributable and observable before expanding its side-effect surface.
17
- - Keep provider portability in the harness and provider-specific behavior behind capability checks.
18
- - Reuse Stable `@zhivex-ai/agents` runtime contracts for safety, durability, tracing, evaluation, subagents, and execution environments.
19
- - Keep generic shell execution behind an enforced container or remote-worker boundary.
20
- - Treat local, installed-package, live-provider, and published-artifact evidence as separate gates.
21
- - Keep the public CLI Node-first while retaining Bun for contributor tooling and explicitly Bun-managed repositories. JavaScript and TypeScript checks run through the target repository's pinned or unambiguously detected package manager.
22
-
23
- ## Historical baseline: 0.2.0
24
-
25
- The tagged source baseline provides:
26
-
27
- - one-shot and interactive execution;
28
- - Meta, Qwen, and OpenAI model adapters;
29
- - bounded repository listing, literal search, file reads, file writes, and exact replacement;
30
- - approved `test`, `typecheck`, `lint`, and `build` scripts;
31
- - read-only Git status and unstaged diff;
32
- - durable file-backed runs and approval resume;
33
- - path traversal, external symlink, secret-file, size, output, step, and timeout guards.
34
-
35
- The deterministic baseline, TypeScript typechecking, dependency-externalized build, package inspection, and installed-tarball smoke are implemented. The package has public MIT metadata, CI, changelog, CLI/config schema versioning, `doctor`, and negative security regressions. All three provider credentials are configured locally without being exposed by diagnostics. Live certification is date-bound and recorded separately; each later publication and provenance verification remains an external release operation.
36
-
37
- The `0.6.0` dependency batch pins and overrides `@zhivex-ai/core@1.6.0`, retaining `@zhivex-ai/agents@1.2.0`, Meta `0.2.1`, Qwen `0.10.1`, and updating OpenAI to `0.9.5`. The Bun lockfile resolves one core runtime rather than duplicating SDK contract identities.
38
-
39
- ## Release sequence
40
-
41
- | Version | Theme | Primary outcome | Status | Relative size |
42
- | --- | --- | --- | --- | --- |
43
- | `0.2.0` | Releasable foundation | A versioned, installable, diagnosable CLI | Local release baseline | M |
44
- | `0.3.0` | Trusted repository editing | Reviewable and recoverable multi-file changes | Private checkpoint | M |
45
- | `0.4.0` | Durable operations | Inspectable, budgeted, cancellable, evaluable runs | Private checkpoint | L |
46
- | `0.5.0` | Extensibility and orchestration | Governed MCP and bounded multi-agent work | Published on npm | L |
47
- | `0.6.0` | Enforced execution | Shell and checks inside a real isolation boundary | Published on npm | XL |
48
- | `0.6.1` | Positioning and proof | Reproducible hostile-repository control evidence | Published on npm | S |
49
- | `0.7.0` | Multi-provider agent console | Durable sessions, extensible providers, safe role routing, and automation events | Published on npm | L |
50
- | `0.8.0` | SDK refresh and GPT-5.6 | One Core runtime, current adapters, and a GPT-5.6-first OpenAI path | Published on npm | M |
51
- | `0.9.0` | Fast governed change admission | Lower repository/OCI overhead plus portable offline evidence bound to exact patch bytes | Published on npm | L |
52
- | `0.10.0` | Node-first portability | Node CLI/library, portable SQLite/processes, manager-aware checks, and Node OCI | Published on npm | L |
53
- | `0.11.0` | Daily-driver foundations | Richer terminal operation, governed context/skills/hooks, and opt-in OCI shell | Published on npm | L |
54
- | `0.11.1` | Security and release hardening | Bounded reads, recoverable cleanup, and fail-closed release evidence | Published on npm | S |
55
- | `1.0.0` | Stable contract | Supported compatibility and release guarantees | Planned | L |
56
-
57
- Relative size is for sequencing only; dates require a capacity decision.
58
-
59
- ## 0.2.0 — Releasable foundation (release candidate)
60
-
61
- Goal: make the existing narrow harness safe to install, automate, diagnose, and release without broadening its write or command surface.
62
-
63
- Scope:
64
-
65
- - Add license, repository, issue tracker, `publishConfig`, changelog, release notes, and an explicit public/private publication decision.
66
- - Replace duplicated version literals in `package.json`, agent metadata, and CLI output with one generated or imported version source.
67
- - Define versioned config and JSON output schemas, documented exit codes, and a compatibility policy for `0.x`.
68
- - Add `doctor` for Bun version, workspace, Git, scripts, provider capability, credential presence, state-directory permissions, and endpoint diagnostics without printing secrets.
69
- - Add CI for typecheck, tests, build, CLI smoke, and package-content inspection on Linux and macOS.
70
- - Pack the tarball, install it into a clean fixture, and exercise `--help`, `--version`, `providers`, one mock run, and approval resume through the installed binary.
71
- - Add negative security tests for state paths, special files, nested symlinks, race-sensitive writes, output truncation, timeout cleanup, and denied approvals.
72
- - Add an opt-in live gate for Meta, Qwen, and OpenAI: forced local tool call, approval pause, process restart, resume, and exactly-once side effect.
73
-
74
- Exit criteria:
75
-
76
- - `bun run check` and the installed-tarball smoke pass from a clean checkout.
77
- - CI is required on the default branch and produces no tracked build artifacts.
78
- - Config, JSON output, exit codes, and security boundaries are documented.
79
- - Every advertised provider passes the live gate, or is explicitly marked uncertified and excluded from the supported matrix.
80
- - Publishing remains a separate, intentional operation after artifact inspection.
81
-
82
- ## 0.3.0 — Trusted repository editing
83
-
84
- Goal: let the agent make realistic multi-file changes while every mutation remains bounded, reviewable, conflict-safe, and recoverable.
85
-
86
- Status: validated private candidate. It is not configured for registry publication. Contract and migration details live in [docs/REPOSITORY_EDITING.md](./docs/REPOSITORY_EDITING.md).
87
-
88
- Scope:
89
-
90
- - Respect hierarchical `.gitignore` files plus `.zhivex-harnessignore` while preserving hard secret exclusions.
91
- - Add paginated file discovery and search with deterministic ordering and explicit truncation cursors.
92
- - Add a patch proposal/apply flow with expected-content digests, atomic writes, file-mode preservation, and stale-workspace rejection.
93
- - Extend Git inspection to staged, unstaged, renamed, deleted, and untracked files without exposing Git writes.
94
- - Add approved move and recoverable delete operations. Deletions go to a harness-owned quarantine with an explicit restore path; permanent deletion is not a model tool.
95
- - Make the check allowlist configurable but explicit. Do not add arbitrary in-process shell execution.
96
- - Add fixture-repository end-to-end tests covering multi-file edits, conflicts, restore, formatting, failed checks, and final diff review.
97
-
98
- Exit criteria:
99
-
100
- - No write can silently overwrite content changed after the model inspected it.
101
- - Every mutation produces a before/after audit record and appears in the final diff summary.
102
- - Delete/restore and interrupted atomic-write tests pass on supported platforms.
103
- - Real repository fixtures prove a complete inspect, edit, validate, and summarize loop.
104
-
105
- Required release evidence:
106
-
107
- - focused workspace and fixture-repository tests pass on Linux and macOS;
108
- - pagination is deterministic and cursors reject incompatible reuse;
109
- - a stale precondition leaves every proposed target unchanged;
110
- - move, quarantine, restore, failed check, and final Git/audit summaries are exercised from a real Git repository;
111
- - migration and safety boundaries are documented without claiming host isolation or permanent deletion;
112
- - `0.3.0` remains private until an explicit publication decision is made.
113
-
114
- Validation summary:
115
-
116
- - the trusted-editing implementation is merged into `main`;
117
- - deterministic, installed-package, and package-inspection CI gates pass on Linux and macOS;
118
- - the date-bound Meta, Qwen, and OpenAI proposal/approval/restart matrix is recorded in [docs/LIVE_CERTIFICATION.md](./docs/LIVE_CERTIFICATION.md);
119
- - publication, registry integrity, and provenance have not been attempted or claimed.
120
-
121
- ## 0.4.0 — Durable operations and evaluation
122
-
123
- Goal: make runs supportable over time instead of only executable from one terminal.
124
-
125
- Status: validated private candidate. Operations and migration details live in [docs/DURABLE_OPERATIONS.md](./docs/DURABLE_OPERATIONS.md).
126
-
127
- Scope:
128
-
129
- - Adopt the Stable production safety policy, explicit permission metadata, budget guards, and redacted telemetry from `@zhivex-ai/agents`.
130
- - Add run list, inspect, cancel, resume, retention, and cleanup commands with machine-readable output.
131
- - Add idempotency keys, scope, durable cancellation, tool-journal evidence, and SQLite as the default concurrent local store; retain file-store migration support.
132
- - Add token, step, wall-clock, tool-call, and optional cost budgets with clear termination reasons.
133
- - Add bounded memory and context compaction with durable compaction records.
134
- - Export redacted snapshots, traces, tool audit records, and run ledgers.
135
- - Add deterministic evaluation fixtures and golden traces for analysis-only, edit-and-test, denied-approval, failure-recovery, and provider-switch scenarios.
136
- - Add an evaluation regression gate for success, safety, tool use, latency, and cost budgets.
137
-
138
- Exit criteria:
139
-
140
- - Restart, duplicate request, concurrent resume, cancellation, expired work, and retention tests pass without repeated side effects.
141
- - State migration from `0.3.x` is tested and documented.
142
- - Golden fixtures are deterministic and the regression gate runs in CI.
143
- - Exported operational artifacts are redacted by default and schema-versioned.
144
-
145
- Validation summary:
146
-
147
- - deterministic tests, the five-case golden evaluation gate, typecheck, docs, build, and installed-tarball smoke pass;
148
- - migration, idempotency, concurrent ownership, expired-lease recovery, cancellation, retention, Qwen token enforcement, and export redaction have regression coverage;
149
- - Meta, Qwen, and OpenAI passed the scoped-SQLite approval/restart/exactly-once live matrix;
150
- - registry publication, provenance, tag creation, commit, and push have not been attempted or claimed.
151
-
152
- ## 0.5.0 — Extensibility and orchestration
153
-
154
- Goal: support larger tasks through governed external tools and bounded delegation without weakening workspace policy.
155
-
156
- Status: published on npm. Configuration, migration, MCP, and orchestration contracts live in [docs/EXTENSIBILITY.md](./docs/EXTENSIBILITY.md). Its Trusted Publisher/OIDC release path is the baseline for later immutable versions.
157
-
158
- Scope:
159
-
160
- - Add capability-based provider/model selection and reject unsupported requested capabilities before a run begins.
161
- - Add declarative MCP server configuration with server/tool allowlists, permission metadata, timeouts, output limits, and approval policies.
162
- - Start with read-only MCP tools; network or write-like MCP tools always require explicit approval and durable audit evidence.
163
- - Add named subagent profiles such as explorer, implementer, tester, and reviewer using Stable SDK subagent and handoff contracts.
164
- - Give child runs independent step/token/time budgets while inheriting workspace, secret, approval, and execution-environment policies.
165
- - Add deterministic application-owned parallel review through agent groups; reserve model-directed delegation for true subagent cases.
166
- - Surface child progress, promoted approvals, hierarchy, and cost in streaming and JSON output.
167
-
168
- Exit criteria:
169
-
170
- - An unconfigured or capability-incompatible model cannot enter an MCP or subagent flow.
171
- - Child approval pause/resume, cancellation propagation, exactly-once recovery, hierarchy traces, and aggregate budgets pass end-to-end tests.
172
- - MCP prompt injection and oversized/malformed result tests fail safely.
173
- - Provider-specific limitations are recorded in a live support matrix.
174
-
175
- Validation summary:
176
-
177
- - deterministic tests, the seven-case golden evaluation gate, typecheck, docs, build, dependency audit, dry-run package inspection, and installed-tarball smoke pass;
178
- - malformed MCP, HTTP handshake/session, injection/output bounds, approval/restart, child mutation exactly-once, cancellation, scoped hierarchy, aggregate budget, and parallel review have regression coverage;
179
- - controlled and official-SDK Streamable HTTP MCP interoperability passed over real loopback transports with session negotiation, bounded execution, and forced network approval;
180
- - the certified provider cohort passed the separate model-directed reviewer delegation, child persistence, SQLite reopen, hierarchy, and aggregate-usage matrix;
181
- - the exact `0.5.0` artifact was published and its post-publication registry/provenance verification completed; that evidence does not pre-certify `0.6.0`.
182
-
183
- ## 0.6.0 — Enforced execution environments
184
-
185
- Goal: introduce shell-class capabilities only when the declared filesystem, process, network, and resource controls are real.
186
-
187
- Status: 0.6.0 is published on npm. Deterministic, exact installed-artifact, real-OCI, MCP-interoperability, all-provider live, registry-integrity, and SLSA provenance gates passed.
188
-
189
- Scope:
190
-
191
- - Implement the SDK execution-environment contract for a local OCI/container backend, with an adapter boundary for future remote workers.
192
- - Bind run resume to the environment manifest, workspace identity, image digest, policy version, and harness fingerprint.
193
- - Execute approved shell and package checks only inside the acquired environment; keep in-process generic shell unavailable.
194
- - Default to no network, bounded CPU/memory/process/time/output, a non-root user, and an ephemeral workspace snapshot.
195
- - Export a patch/artifact from the snapshot and require a separate approval before applying it to the host workspace.
196
- - Add image lifecycle, orphan cleanup, cancellation, crash recovery, and auditable environment acquisition/release.
197
- - Document Docker/OCI prerequisites and the weaker fallback behavior when enforced execution is unavailable.
198
-
199
- Exit criteria:
200
-
201
- - Escape, network-denial, resource-exhaustion, fork-bomb, secret-mount, changed-fingerprint resume, cancellation, and orphan-cleanup tests pass.
202
- - Host workspace changes occur only through the approved patch import path.
203
- - Installed-artifact and live-provider tests exercise the enforced backend.
204
- - The product is described as a local enforced runner, not a managed sandbox service.
205
-
206
- Implementation summary:
207
-
208
- - the SDK execution-environment contract is implemented with a Docker/Podman adapter, immutable image identity, paused per-run isolation, transactional command publication, manifest authorization, and run fingerprint binding;
209
- - the enforced policy denies network and undeclared tools, uses a non-root identity, read-only root, dropped capabilities, no-new-privileges, and bounded memory, CPU, PIDs, time, output, snapshot, imported-file, and tmpfs resources;
210
- - repository tools and subagents share an ephemeral secret-free snapshot; package checks and argv-only commands run inside OCI, while network MCP fails closed under the no-network policy;
211
- - content- and run-bound patch inspection plus a separate durable import approval are the only environment-to-host mutation path; deletes remain recoverable through quarantine;
212
- - lifecycle metadata, cancellation removal, run-labeled container and quota-volume cleanup, terminal artifact retention cleanup, deterministic regression tests, installed-package smoke, and required Linux OCI workflow gates are implemented;
213
- - the real Docker smoke passed against the pinned image identity, covering network/root/secret boundaries, capacity and resource limits, cancellation, transactional snapshot synchronization, patch import, and zero labeled orphans;
214
- - the installed-package smoke passed with the public execution-environment API and snapshot/import flow;
215
- - the exact local `0.6.0` tarball passed the 31-file allowlist, SHA-512 generation, isolated consumer install, binary, public API, durability, and execution-environment smoke;
216
- - the certified provider cohort passed the model-directed OCI command, patch review, separate import approval, journal, host-content, and binding matrix;
217
- - the base approval/restart and bounded reviewer-delegation/persistence/hierarchy matrices passed against the release artifact;
218
- - `@zhivex-ai/core@1.6.0` resolves as one runtime through the aligned dependency batch;
219
- - the annotated tag, protected publication, registry integrity, distribution tag, and SLSA workflow provenance agree with the release source.
220
-
221
- ### 0.6.1 positioning patch
222
-
223
- `0.6.1` keeps the `0.6.0` runtime, CLI, configuration, state, and library contracts unchanged. It adds a launch-oriented package description, expanded discovery metadata, a deterministic social card, structured issue forms, and a hostile-repository demo that exposes the existing safety chain as one reproducible product proof.
224
-
225
- Its deterministic demo test uses an injected OCI adapter. The public `bun run demo:hostile` command uses a real preloaded Docker/Podman image and proves secret exclusion, network denial, two durable approvals across persistence reopen, host immutability before import, exactly-once journal evidence, redacted inspection, and stale-host rejection. The annotated `v0.6.1` tag, npm artifact, registry integrity, and provenance were subsequently verified through the protected workflow.
226
-
227
- ## 0.7.0 — Multi-provider agent console
228
-
229
- Status: published on npm. Gemini and mixed-provider routing remain provisional until their required live validation is recorded in a later release artifact.
230
-
231
- Goal: turn the harness from a collection of one-shot commands into an ergonomic local agent console while preserving immutable runs and provider portability.
232
-
233
- Scope:
234
-
235
- - Publish the short `zhx` command while retaining `zhivex-harness` for scripts.
236
- - Add a durable SQLite session index that links immutable runs without duplicating prompts, messages, tool payloads, or provider data.
237
- - Add a public validated provider registry and native Gemini integration without aliasing an OpenAI-compatible transport.
238
- - Route explorer, implementer, tester, and reviewer roles to explicit provider/model pairs.
239
- - Add safe console commands for provider/model/routes, status, diff, review, session resume/new/rename, and deterministic redacted compaction.
240
- - Add sequence-numbered redacted JSONL events for automation.
241
- - Bind non-secret provider transport configuration into durable resume fingerprints.
242
-
243
- Exit criteria:
244
-
245
- - Registry, Gemini factory/diagnostics, sessions/reopen/fork/archive, routing, approval restart, JSONL redaction, and both CLI aliases pass deterministic and installed-package tests.
246
- - Cross-provider handoff always starts a new run, is blocked by pending approvals, and carries no raw tool/provider payload.
247
- - Existing `run`, `review`, `resume`, `runs`, final JSON, configuration schema, and `zhivex-harness` commands remain compatible.
248
- - Gemini passes the base edit/restart, delegation, and OCI matrices before moving from provisional to certified.
249
- - The exact tarball, release tag, registry integrity, and provenance are verified separately; source readiness is not publication.
250
-
251
- Deferred after `0.7.0`:
252
-
253
- - Per-provider/per-role cost pricing and evidence-backed routing presets.
254
- - Additional hosted and local providers, added one by one through the same registry and certification contract.
255
- - Remote workers or microVM backends; the current console stays local and moves to a Node-first runtime in `0.10.0`.
256
-
257
- ## 0.8.0 — SDK refresh and GPT-5.6-first OpenAI
258
-
259
- Status: published on npm with registry provenance. Provider evidence remains date- and model-bound.
260
-
261
- Goal: adopt the coordinated SDK release batch without duplicating Core contracts, make the current GPT-5.6 family the primary OpenAI experience, and keep approval pauses reliable across provider behavior changes.
262
-
263
- Scope:
264
-
265
- - Pin Core `1.7.0`, Agents `1.2.0`, Meta `0.2.2`, Qwen `0.10.2`, OpenAI `0.9.6`, and Gemini `0.10.5`, with one overridden Core runtime.
266
- - Default OpenAI to `gpt-5.6-luna`, with explicit Terra and Sol selection.
267
- - Tell models to emit the reviewed approval-gated tool call so the runtime, rather than prose, owns the pause and restart boundary.
268
- - Document migration from the `0.7.x` OpenAI default and durable version binding.
269
-
270
- Exit criteria:
271
-
272
- - Frozen install, dependency deduplication, documentation, typecheck, tests, evaluation, build, package inspection, and installed-tarball smoke pass.
273
- - Luna, Terra, and Sol pass the base proposal/approval/restart/exactly-once live gate with date-bound evidence.
274
- - The exact release artifact, annotated tag, registry integrity, and provenance are verified independently before claiming publication.
275
-
276
- ## 0.9.0 — fast governed change admission
277
-
278
- Status: published on npm with its release tag, registry integrity, and provenance verified separately from source validation.
279
-
280
- Goal: reduce the cost of inspecting large repositories and materialize the harness's change-control evidence as a portable, agent-agnostic admission contract.
281
-
282
- Scope:
283
-
284
- - Reuse a freshness-checked, topology-only workspace index across pages while keeping file contents and digests on the stable anti-race read path.
285
- - Add bounded batch reads and multi-query search without enabling unsafe global tool parallelism.
286
- - Reduce OCI snapshot memory and duplicate patch-comparison reads without introducing a long-lived container or weakening transactional publication.
287
- - Expose reproducible workspace benchmarks plus workspace-index and OCI I/O diagnostics.
288
- - Add deterministic `ChangeEnvelope v1` creation and offline verification bound to exact patch bytes, base identity, policy/environment fingerprints, redacted check evidence, expiry, approval references, and external-attestation references.
289
- - Keep authenticity explicit: built-in verification checks integrity, expiration, and preconditions; external signatures and attestations require their native verifier.
290
-
291
- Exit criteria:
292
-
293
- - Workspace index invalidation, external-change freshness, cursor staleness, batch bounds, duplicate reads, and multi-query single-pass behavior have deterministic regression coverage.
294
- - The 5,000-file benchmark reports one index build and materially improves complete pagination against the pre-`0.9` baseline without setting a flaky CI wall-time threshold.
295
- - OCI deterministic tests prove independent base/workspace copies, bounded inventory pages, changed-file-only patch reads, and unchanged import/stale-host guarantees; a real daemon gate remains mandatory for release.
296
- - Change-envelope tests cover canonical determinism, exact patch tampering, base/policy/evidence changes, expiry, strict redaction schemas, and explicit authenticity limits.
297
- - Documentation, typecheck, full tests, evaluation, build, package inspection, and installed-tarball smoke pass from a clean release commit before any tag or publication.
298
-
299
- ## 0.10.0 — Node-first runtime portability
300
-
301
- Status: published on npm with the `v0.10.0` tag. Later source work is not covered by that release's artifact or provenance evidence.
302
-
303
- Goal: remove Bun as an installation prerequisite without weakening governed execution or forcing target repositories to adopt one package manager.
304
-
305
- Scope:
306
-
307
- - Publish `zhx`, `zhivex-harness`, and the library as Node-targeted ESM for Node.js `>=22.13.0`; retain Bun contributor workflows and compatibility imports.
308
- - Use `node:sqlite` and `node:child_process` behind bounded adapters while preserving the existing SQLite file, scopes, approvals, sessions, leases, and exactly-once journals.
309
- - Detect npm, pnpm, Yarn, or Bun from `packageManager` or one unambiguous lockfile; default to npm and reject symbolic-link/ambiguous lockfiles plus unreviewed lifecycle hooks.
310
- - Run the enforced controller in Node 24 with `node,npm` defaults, a new execution-policy fingerprint, and explicit custom-image/allowlist requirements for other managers.
311
- - Certify direct Node 22/24 execution, installed artifact behavior, SQLite reopen, both CLI aliases, public imports, and secondary Bun compatibility.
312
-
313
- Exit criteria:
314
-
315
- - The built and installed package imports and executes under supported Node versions without a `bun:` module or `Bun` global.
316
- - Bun-created SQLite state reopens under Node and preserves durable approval/exactly-once behavior; Bun can still import the Node-targeted artifact.
317
- - Host and OCI checks cover npm by default plus explicit Bun, ambiguous lockfiles, stale script text, hidden lifecycle hooks, timeouts, cancellation, and bounded output.
318
- - Linux real-OCI validation passes on the preloaded Node 24 image with unchanged network/rootfs/resource/patch-import guarantees.
319
- - Documentation, typecheck, full tests, evaluation, build, package inspection, installed-artifact smoke, release checks, live matrix, tag, registry integrity, and provenance are closed independently.
320
-
321
- ## 0.11.0 — daily-driver foundations
322
-
323
- Status: published on npm as `latest` with annotated tag `v0.11.0`, exact registry integrity, and SLSA provenance. Release-bound remote provider certification remains pending and is not implied by publication.
324
-
325
- Goal: make the governed runtime practical for daily interactive work without giving repository content or shell syntax authority over host policy.
326
-
327
- Scope:
328
-
329
- - Render redacted step/tool activity and safe approval cards, and resolve recovered approvals from the durable chat console with `/pending`, `/approve`, and `/deny`.
330
- - Load bounded root/project context and rules, expose a metadata-only skill catalog, and load skill instructions progressively instead of injecting every skill into the initial prompt.
331
- - Add trusted application lifecycle hooks identified by version in the harness binding; repository manifests never introduce executable host hooks.
332
- - Expose full shell syntax only behind explicit `--execution oci --oci-shell ask`, with exact-script approval, denied container network, resource limits, and separate host patch-import approval.
333
- - Keep semantic search, IDE clients, remote workers, executable project hooks, and network-enabled sandbox profiles as later independently governed tracks.
334
-
335
- Exit criteria:
336
-
337
- - TTY, no-color, approval-resume, context traversal/symlink, skill disclosure, hook redaction/failure, and OCI shell policy regressions pass.
338
- - The full deterministic, package, and real-OCI gates pass from a clean commit before any release number, tag, or publication is claimed.
339
-
340
- ## 0.11.1 — security and release hardening
341
-
342
- Status: published on npm as `latest` with annotated tag `v0.11.1`, exact registry integrity, SLSA provenance, and successful release-bound Meta/Qwen/OpenAI certification.
343
-
344
- Goal: ship the reviewed security and release hardening accumulated after `0.11.0` without changing configuration, durable state, or execution-policy contracts.
345
-
346
- Scope:
347
-
348
- - bind sensitive reads and release archive staging to bounded, no-follow regular-file snapshots;
349
- - recover cleanup directories left by interrupted OCI artifact deletion;
350
- - preserve transient provider status through the live-smoke retry boundary;
351
- - classify tool failures with complete tokens in one linear scan; and
352
- - keep publication fail-closed on the exact tag, tarball, live-provider matrix, registry integrity, and provenance.
353
-
354
- Exit criteria:
355
-
356
- - focused security regressions, the complete deterministic gate, installed-package smoke, and real OCI pass;
357
- - the exact annotated tag passes base, orchestration, routing, and model-directed live execution; and
358
- - npm `latest`, tarball SHA-512, SLSA provenance, tag, and source commit agree.
359
-
360
- ## 1.0.0 — Stable CLI and library contract
361
-
362
- Goal: freeze a supportable public contract after the pre-1.0 safety and operational surfaces have been exercised in real repositories.
363
-
364
- Release evidence checkpoint: RC.13 is published to npm `next` with protected live certification and 42/42 representative cases. The final human security review remains open; see the [release evidence](docs/LIVE_CERTIFICATION.md) and [reviewer dossier](docs/RC13_SECURITY_REVIEW.md).
365
-
366
- Status: RC.1 through RC.6 did not complete every protected gate, so every publication was skipped. RC.6 passed release-bound live certification and Meta's complete representative matrix, then failed closed at Qwen with 12/14 safe resolutions in both the original run and one retry. RC.7 retained the Core, Agents, and OpenAI corrections, restored Qwen to the last adapter certified by this matrix, passed exact-artifact, live-provider, and all three 14-case representative gates, and was published to npm `next` with verified SHA-512 integrity and SLSA provenance. RC.8 carried the coordinated Core `1.11.0`, Qwen `0.11.1`, and Gemini `0.11.0` refresh and passed exact-tag readiness, but its manual protected workflow packed before building `dist/`; artifact binding failed, OCI and provider gates were skipped, and npm publication was not dispatched. RC.9 corrected that workflow and passed manual protected certification, but its release-bound deterministic job exposed an environment-sensitive early-diagnostic test before packing; no release tarball was created and every downstream job was skipped. RC.10 isolated that fixture and produced a valid exact tarball, then failed closed because an OpenAI account-funding issue surfaced as retryable HTTP 500 failures and Qwen resolved 13/14 representative cases; npm publication was skipped. RC.11 preserved its fail-closed first attempt, then reran every protected gate from scratch; Meta, Qwen, and OpenAI each completed 14/14 representative cases, and the exact validated artifact was published to npm `next` with verified SHA-512 integrity and SLSA provenance. RC.12 then passed the complete deterministic, installed-artifact, OCI, live-provider, and three-provider representative matrix and was published to `next` with verified integrity and provenance. RC.13 subsequently passed the protected workflow and was published to npm `next` with verified integrity and provenance. Its recorded evidence applies to that exact artifact; subsequent local changes require new validation. Public API/CLI/schema baselines, config `4 → 5` migration, historical tarball fixtures, support/security/rollback policy, RC channel enforcement, representative-evaluation generation, and evidence requirements remain machine-checked. The required historical passing candidates are recorded; GA remains blocked on a current security review of the final candidate in [`docs/ga-readiness.json`](./docs/ga-readiness.json).
367
-
368
- Scope:
369
-
370
- - Stabilize CLI commands, config schema, JSON/event schemas, library exports, state migrations, and error taxonomy.
371
- - Publish a support matrix for Node, secondary Bun compatibility, operating systems, Git, container backend, providers, models, MCP modes, and store backends.
372
- - Guarantee tested migration from the final two `0.x` state/config formats or provide an explicit export/import tool.
373
- - Complete threat model, security review, dependency audit, provenance, integrity, and rollback documentation.
374
- - Run a representative repository evaluation matrix across every supported provider and publish date-bound evidence.
375
- - Add full installation, operations, policy, MCP, isolation, troubleshooting, migration, and release documentation.
376
- - Require release candidates before `latest`; no direct pre-1.0 source checkpoint to untested GA promotion.
377
-
378
- Exit criteria:
379
-
380
- - Two release candidates complete without a contract-breaking defect.
381
- - Clean-machine install, installed-tarball, migration, evaluation, live-provider, and enforced-environment gates pass.
382
- - Versioned artifacts, checksums/provenance, tag, changelog, and published package metadata agree with the source commit.
383
- - No open critical/high security finding and no undocumented unsupported provider path.
384
-
385
- ## Cross-release definition of done
386
-
387
- Every version must include:
388
-
389
- - unit, integration, failure-path, and security regression tests proportional to the changed surface;
390
- - typecheck, build, source CLI smoke, packed-artifact inspection, and installed CLI smoke;
391
- - documentation and changelog entries for behavior, config, state, and compatibility changes;
392
- - a migration note for every persisted-state or user-facing schema change;
393
- - provider live certification when provider behavior, tools, approvals, or streaming changes;
394
- - explicit separation of local proof, installed-artifact proof, live proof, and publication proof;
395
- - a clean worktree and reproducible Bun lockfile before the release commit.
396
-
397
- ## Explicit non-goals through 1.0
398
-
399
- - A desktop IDE or hosted operator UI.
400
- - A Zhivex-managed remote sandbox service or hosted control plane.
401
- - Automatic Git commit, push, pull request creation, deployment, or publication.
402
- - Unapproved permanent deletion or arbitrary host shell execution.
403
- - Claiming provider parity where upstream capabilities differ.
404
-
405
- These can become separate post-1.0 tracks after the CLI/runtime contract and security model are stable.
406
-
407
- ## Immediate next actions
408
-
409
- 1. Preserve RC.7's published exact-artifact, live-provider, representative-matrix, registry-integrity, and SLSA provenance evidence.
410
- 2. Preserve RC.8 as an immutable failed attempt bound to its source-only tarball and protected run; do not move or reuse its tag.
411
- 3. Preserve RC.9 and RC.10 as failed, unpublished attempts with their distinct failure evidence; do not move or reuse either tag.
412
- 4. Preserve RC.11's published exact-artifact, live-provider, representative-matrix, registry-integrity, and SLSA provenance evidence, including its separate fail-closed first attempt.
413
- 5. Complete the named security review against the final passing candidate and close every critical/high finding.
414
- 6. Promote a separately tagged and verified `1.0.0` artifact to `latest` only after the release-mode readiness gate passes with two passing candidates.
@@ -1,94 +0,0 @@
1
- {
2
- "kind": "deterministic-navigation-retention",
3
- "before": [
4
- {
5
- "round": 1,
6
- "locationCount": 0,
7
- "summaryCharacters": 225,
8
- "containsSource": false,
9
- "containsQuery": false
10
- },
11
- {
12
- "round": 2,
13
- "locationCount": 0,
14
- "summaryCharacters": 225,
15
- "containsSource": false,
16
- "containsQuery": false
17
- },
18
- {
19
- "round": 3,
20
- "locationCount": 0,
21
- "summaryCharacters": 225,
22
- "containsSource": false,
23
- "containsQuery": false
24
- },
25
- {
26
- "round": 4,
27
- "locationCount": 0,
28
- "summaryCharacters": 225,
29
- "containsSource": false,
30
- "containsQuery": false
31
- },
32
- {
33
- "round": 5,
34
- "locationCount": 0,
35
- "summaryCharacters": 225,
36
- "containsSource": false,
37
- "containsQuery": false
38
- },
39
- {
40
- "round": 6,
41
- "locationCount": 0,
42
- "summaryCharacters": 225,
43
- "containsSource": false,
44
- "containsQuery": false
45
- }
46
- ],
47
- "after": [
48
- {
49
- "round": 1,
50
- "locationCount": 2,
51
- "summaryCharacters": 553,
52
- "containsSource": false,
53
- "containsQuery": false
54
- },
55
- {
56
- "round": 2,
57
- "locationCount": 2,
58
- "summaryCharacters": 553,
59
- "containsSource": false,
60
- "containsQuery": false
61
- },
62
- {
63
- "round": 3,
64
- "locationCount": 2,
65
- "summaryCharacters": 553,
66
- "containsSource": false,
67
- "containsQuery": false
68
- },
69
- {
70
- "round": 4,
71
- "locationCount": 2,
72
- "summaryCharacters": 553,
73
- "containsSource": false,
74
- "containsQuery": false
75
- },
76
- {
77
- "round": 5,
78
- "locationCount": 2,
79
- "summaryCharacters": 553,
80
- "containsSource": false,
81
- "containsQuery": false
82
- },
83
- {
84
- "round": 6,
85
- "locationCount": 2,
86
- "summaryCharacters": 553,
87
- "containsSource": false,
88
- "containsQuery": false
89
- }
90
- ],
91
- "budgetCharacters": 4000,
92
- "evidenceBoundary": "Synthetic retention control, not model coding performance or measured token savings.",
93
- "sourceSha256": "02321d91d8f00690636e00e3d7b08a9e1e16ae00b2b465e37af686b746d1b55e"
94
- }