@holmes-lab/holmes-kit 0.38.0 → 0.40.0
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.
- package/CHANGELOG.md +370 -6
- package/README.md +58 -40
- package/dist/.build-id +1 -1
- package/dist/holmes/admission/core/admission-policy.d.ts +37 -0
- package/dist/holmes/admission/core/admission-policy.js +147 -0
- package/dist/holmes/admission/core/bounded-reader.d.ts +56 -0
- package/dist/holmes/admission/core/bounded-reader.js +135 -0
- package/dist/holmes/admission/core/change-classifier.d.ts +34 -0
- package/dist/holmes/admission/core/change-classifier.js +278 -0
- package/dist/holmes/admission/core/config-loader.d.ts +30 -0
- package/dist/holmes/admission/core/config-loader.js +145 -0
- package/dist/holmes/admission/core/event-judgement.d.ts +37 -0
- package/dist/holmes/admission/core/event-judgement.js +251 -0
- package/dist/holmes/admission/core/path-rules.d.ts +35 -0
- package/dist/holmes/admission/core/path-rules.js +88 -0
- package/dist/holmes/admission/core/pin.d.ts +7 -0
- package/dist/holmes/admission/core/pin.js +29 -0
- package/dist/holmes/admission/core/ports.d.ts +48 -0
- package/dist/holmes/admission/core/ports.js +11 -0
- package/dist/holmes/admission/core/range-resolver.d.ts +32 -0
- package/dist/holmes/admission/core/range-resolver.js +51 -0
- package/dist/holmes/admission/core/self-containment.d.ts +1 -0
- package/dist/holmes/admission/core/self-containment.js +125 -0
- package/dist/holmes/admission/core/signature-source.d.ts +9 -0
- package/dist/holmes/admission/core/signature-source.js +4 -0
- package/dist/holmes/admission/core/transition-planner.d.ts +15 -0
- package/dist/holmes/admission/core/transition-planner.js +14 -0
- package/dist/holmes/admission/core/verdict.d.ts +38 -0
- package/dist/holmes/admission/core/verdict.js +17 -0
- package/dist/holmes/admission/core/wiring.d.ts +44 -0
- package/dist/holmes/admission/core/wiring.js +618 -0
- package/dist/holmes/admission/forge/git-object-port.d.ts +4 -0
- package/dist/holmes/admission/forge/git-object-port.js +132 -0
- package/dist/holmes/assoc/assoc-arm.d.ts +1 -1
- package/dist/holmes/assoc/assoc-arm.js +1 -1
- package/dist/holmes/cli/agents.d.ts +8 -0
- package/dist/holmes/cli/agents.js +9 -5
- package/dist/holmes/cli/approve-cli.d.ts +2 -0
- package/dist/holmes/cli/approve-cli.js +392 -0
- package/dist/holmes/cli/approve-ref.d.ts +13 -7
- package/dist/holmes/cli/approve-ref.js +30 -10
- package/dist/holmes/cli/approve-status.d.ts +26 -2
- package/dist/holmes/cli/approve-status.js +98 -18
- package/dist/holmes/cli/approve-watch.d.ts +5 -0
- package/dist/holmes/cli/approve-watch.js +10 -5
- package/dist/holmes/cli/approve.d.ts +50 -13
- package/dist/holmes/cli/approve.js +260 -67
- package/dist/holmes/cli/attest.js +2 -1
- package/dist/holmes/cli/autonomy.d.ts +4 -1
- package/dist/holmes/cli/autonomy.js +17 -10
- package/dist/holmes/cli/codex-oracle.d.ts +11 -0
- package/dist/holmes/cli/codex-oracle.js +5 -1
- package/dist/holmes/cli/codex-toml.d.ts +10 -0
- package/dist/holmes/cli/codex-toml.js +36 -2
- package/dist/holmes/cli/doctor-boundary.d.ts +76 -0
- package/dist/holmes/cli/doctor-boundary.js +308 -0
- package/dist/holmes/cli/doctor-locks.d.ts +15 -0
- package/dist/holmes/cli/doctor-locks.js +119 -0
- package/dist/holmes/cli/doctor.d.ts +2 -0
- package/dist/holmes/cli/doctor.js +45 -5
- package/dist/holmes/cli/flags.d.ts +23 -0
- package/dist/holmes/cli/flags.js +89 -0
- package/dist/holmes/cli/index.d.ts +5 -1
- package/dist/holmes/cli/index.js +206 -424
- package/dist/holmes/cli/init.js +33 -0
- package/dist/holmes/cli/lock-recover.d.ts +5 -0
- package/dist/holmes/cli/lock-recover.js +126 -0
- package/dist/holmes/cli/mcp-processes.d.ts +32 -0
- package/dist/holmes/cli/mcp-processes.js +132 -0
- package/dist/holmes/cli/release-docs.js +1 -1
- package/dist/holmes/cli/run-exec.d.ts +141 -0
- package/dist/holmes/cli/run-exec.js +1435 -0
- package/dist/holmes/cli/run-provision.d.ts +8 -0
- package/dist/holmes/cli/run-provision.js +325 -0
- package/dist/holmes/cli/run-wiring.d.ts +69 -0
- package/dist/holmes/cli/run-wiring.js +270 -0
- package/dist/holmes/cli/run.d.ts +26 -0
- package/dist/holmes/cli/run.js +364 -83
- package/dist/holmes/cli/runtime-binding-approval.js +32 -19
- package/dist/holmes/cli/screen-safe.d.ts +3 -92
- package/dist/holmes/cli/screen-safe.js +18 -756
- package/dist/holmes/config/config.d.ts +2 -0
- package/dist/holmes/config/config.js +5 -2
- package/dist/holmes/cpg/foundation/language-matrix.js +2 -2
- package/dist/holmes/cpg/import-resolver.js +1 -1
- package/dist/holmes/governance/approval-decisions.d.ts +47 -0
- package/dist/holmes/governance/approval-decisions.js +29 -0
- package/dist/holmes/governance/approval-grants.d.ts +220 -1
- package/dist/holmes/governance/approval-grants.js +612 -33
- package/dist/holmes/governance/approval-queue.d.ts +31 -0
- package/dist/holmes/governance/approval-queue.js +122 -11
- package/dist/holmes/governance/approval-spend.d.ts +95 -0
- package/dist/holmes/governance/approval-spend.js +191 -0
- package/dist/holmes/governance/autonomous-shell.d.ts +61 -0
- package/dist/holmes/governance/autonomous-shell.js +332 -0
- package/dist/holmes/governance/autonomy.d.ts +5 -0
- package/dist/holmes/governance/autonomy.js +16 -11
- package/dist/holmes/governance/constitution.d.ts +5 -0
- package/dist/holmes/governance/constitution.js +32 -12
- package/dist/holmes/governance/full-autonomy.d.ts +10 -0
- package/dist/holmes/governance/full-autonomy.js +103 -7
- package/dist/holmes/governance/harness-catalog.d.ts +103 -0
- package/dist/holmes/governance/harness-catalog.js +348 -0
- package/dist/holmes/governance/human-channel.d.ts +38 -0
- package/dist/holmes/governance/human-channel.js +49 -0
- package/dist/holmes/governance/install-manifest.d.ts +22 -0
- package/dist/holmes/governance/install-manifest.js +160 -0
- package/dist/holmes/governance/ledger-rechain.js +2 -0
- package/dist/holmes/governance/ledger-store.conformance.d.ts +7 -1
- package/dist/holmes/governance/ledger-store.conformance.js +66 -0
- package/dist/holmes/governance/ledger-store.d.ts +88 -11
- package/dist/holmes/governance/ledger-store.js +186 -8
- package/dist/holmes/governance/provenance-chain.d.ts +16 -4
- package/dist/holmes/governance/provenance-chain.js +19 -4
- package/dist/holmes/governance/provenance-ledger.d.ts +6 -3
- package/dist/holmes/governance/provenance-ledger.js +53 -18
- package/dist/holmes/governance/push-gate-runner.js +11 -7
- package/dist/holmes/governance/recorded-pairs.d.ts +96 -0
- package/dist/holmes/governance/recorded-pairs.js +522 -0
- package/dist/holmes/governance/replica-id.d.ts +1 -1
- package/dist/holmes/governance/replica-id.js +1 -1
- package/dist/holmes/governance/spec-seam.d.ts +59 -0
- package/dist/holmes/governance/spec-seam.js +587 -0
- package/dist/holmes/governance/spend-kinds.d.ts +16 -0
- package/dist/holmes/governance/spend-kinds.js +18 -0
- package/dist/holmes/governance/tool-actions.js +2 -0
- package/dist/holmes/guardrail/decision-ledger.d.ts +2 -1
- package/dist/holmes/guardrail/decision-ledger.js +2 -1
- package/dist/holmes/guardrail/impact-gate.d.ts +1 -0
- package/dist/holmes/guardrail/impact-gate.js +1 -1
- package/dist/holmes/guardrail/line-continuation.d.ts +8 -0
- package/dist/holmes/guardrail/line-continuation.js +39 -0
- package/dist/holmes/guardrail/operator-person.d.ts +28 -4
- package/dist/holmes/guardrail/operator-person.js +57 -11
- package/dist/holmes/guardrail/refusal-codes.d.ts +8 -3
- package/dist/holmes/guardrail/refusal-codes.js +70 -10
- package/dist/holmes/guardrail/risk-classifier.d.ts +15 -9
- package/dist/holmes/guardrail/risk-classifier.js +245 -15
- package/dist/holmes/guardrail/risk-gate.d.ts +2 -8
- package/dist/holmes/guardrail/risk-gate.js +7 -34
- package/dist/holmes/guardrail/risk-types.d.ts +10 -0
- package/dist/holmes/guardrail/run-plan-scope.js +3 -1
- package/dist/holmes/guardrail/run-refusals.d.ts +6 -1
- package/dist/holmes/guardrail/run-refusals.js +36 -14
- package/dist/holmes/guardrail/run-stages.d.ts +10 -0
- package/dist/holmes/guardrail/run-stages.js +46 -6
- package/dist/holmes/guardrail/scope-judgment.js +1 -1
- package/dist/holmes/guardrail/shell-words.js +24 -3
- package/dist/holmes/guardrail/unresolved-write.d.ts +40 -0
- package/dist/holmes/guardrail/unresolved-write.js +556 -0
- package/dist/holmes/guardrail/write-target.d.ts +3 -0
- package/dist/holmes/guardrail/write-target.js +26 -5
- package/dist/holmes/hooks/pre-tool-use.d.ts +105 -1
- package/dist/holmes/hooks/pre-tool-use.js +1167 -168
- package/dist/holmes/hooks/rtm-refresh-child.d.ts +1 -1
- package/dist/holmes/hooks/rtm-refresh-child.js +1 -1
- package/dist/holmes/hooks/session-start.d.ts +5 -0
- package/dist/holmes/hooks/session-start.js +29 -1
- package/dist/holmes/hooks/stop.d.ts +23 -0
- package/dist/holmes/hooks/stop.js +88 -33
- package/dist/holmes/mcp/approval-adapters.js +3 -1
- package/dist/holmes/mcp/approval-commit.js +3 -2
- package/dist/holmes/mcp/approval-policy.d.ts +2 -1
- package/dist/holmes/mcp/approval-policy.js +3 -1
- package/dist/holmes/mcp/handlers/adoption.d.ts +1 -1
- package/dist/holmes/mcp/handlers/approval-ask.d.ts +14 -0
- package/dist/holmes/mcp/handlers/approval-ask.js +31 -6
- package/dist/holmes/mcp/handlers/entity-integration.d.ts +3 -3
- package/dist/holmes/mcp/handlers/entity-integration.js +29 -11
- package/dist/holmes/mcp/handlers/entity-renumber.d.ts +4 -4
- package/dist/holmes/mcp/handlers/entity-renumber.js +29 -11
- package/dist/holmes/mcp/handlers/entity-store.d.ts +2 -2
- package/dist/holmes/mcp/handlers/entity-store.js +133 -59
- package/dist/holmes/mcp/handlers/operator-inspection.d.ts +9 -5
- package/dist/holmes/mcp/handlers/operator-inspection.js +79 -16
- package/dist/holmes/mcp/handlers/phase-queries.d.ts +1 -1
- package/dist/holmes/mcp/handlers/requirement-triage.d.ts +4 -4
- package/dist/holmes/mcp/handlers/review-evidence.d.ts +2 -2
- package/dist/holmes/mcp/handlers/review-evidence.js +35 -11
- package/dist/holmes/mcp/handlers/review-queries.d.ts +5 -0
- package/dist/holmes/mcp/handlers/review-queries.js +8 -1
- package/dist/holmes/mcp/handlers/review-verdict.d.ts +3 -0
- package/dist/holmes/mcp/handlers/review-verdict.js +10 -3
- package/dist/holmes/mcp/handlers/risk-assessment.d.ts +7 -2
- package/dist/holmes/mcp/handlers/risk-assessment.js +34 -12
- package/dist/holmes/mcp/handlers/runtime-binding-tool.d.ts +2 -2
- package/dist/holmes/mcp/handlers/slice-orchestration.d.ts +6 -1
- package/dist/holmes/mcp/handlers/slice-orchestration.js +14 -1
- package/dist/holmes/mcp/handlers/spec-approval.d.ts +15 -3
- package/dist/holmes/mcp/handlers/spec-approval.js +32 -5
- package/dist/holmes/mcp/handlers/spec-authoring.d.ts +2 -2
- package/dist/holmes/mcp/handlers/spec-authoring.js +19 -2
- package/dist/holmes/mcp/handlers/spec-lifecycle.d.ts +11 -38
- package/dist/holmes/mcp/handlers/spec-lifecycle.js +441 -94
- package/dist/holmes/mcp/handlers/spec-queries.d.ts +2 -2
- package/dist/holmes/mcp/handlers/taint-screening.d.ts +1 -1
- package/dist/holmes/mcp/handlers/taint-screening.js +2 -2
- package/dist/holmes/mcp/handlers/test-execution.d.ts +1 -1
- package/dist/holmes/mcp/handlers/workspace-preflight.d.ts +5 -0
- package/dist/holmes/mcp/handlers/workspace-preflight.js +10 -2
- package/dist/holmes/mcp/handlers/workspace-queries.d.ts +2 -2
- package/dist/holmes/mcp/handlers.d.ts +99 -79
- package/dist/holmes/mcp/handlers.js +93 -25
- package/dist/holmes/mcp/harness-attestation.d.ts +78 -5
- package/dist/holmes/mcp/harness-attestation.js +325 -53
- package/dist/holmes/mcp/maintenance-analyze.d.ts +1 -1
- package/dist/holmes/mcp/maintenance-analyze.js +9 -9
- package/dist/holmes/mcp/maintenance-evidence.js +31 -2
- package/dist/holmes/mcp/requirement-triage-evidence.js +22 -13
- package/dist/holmes/mcp/server-staleness.d.ts +43 -0
- package/dist/holmes/mcp/server-staleness.js +158 -0
- package/dist/holmes/mcp/server.js +34 -9
- package/dist/holmes/mcp/spec-id-guard.js +1 -1
- package/dist/holmes/mcp/tool-schemas.d.ts +13 -0
- package/dist/holmes/mcp/tool-schemas.js +42 -2
- package/dist/holmes/project/act-root.d.ts +19 -0
- package/dist/holmes/project/act-root.js +100 -0
- package/dist/holmes/project/baseline.js +4 -3
- package/dist/holmes/project/bounded-group.d.ts +47 -0
- package/dist/holmes/project/bounded-group.js +140 -0
- package/dist/holmes/project/bounded-io.d.ts +50 -2
- package/dist/holmes/project/bounded-io.js +138 -6
- package/dist/holmes/project/change-source.js +2 -2
- package/dist/holmes/project/instance-id.d.ts +10 -0
- package/dist/holmes/project/instance-id.js +233 -0
- package/dist/holmes/project/machine-identity.d.ts +25 -0
- package/dist/holmes/project/machine-identity.js +133 -0
- package/dist/holmes/project/owned-lock.d.ts +84 -0
- package/dist/holmes/project/owned-lock.js +263 -0
- package/dist/holmes/project/plain-lock-fs.d.ts +2 -0
- package/dist/holmes/project/plain-lock-fs.js +126 -0
- package/dist/holmes/project/request-lock.d.ts +85 -0
- package/dist/holmes/project/request-lock.js +459 -0
- package/dist/holmes/project/root.d.ts +12 -4
- package/dist/holmes/project/root.js +26 -7
- package/dist/holmes/project/run-records.d.ts +19 -0
- package/dist/holmes/project/run-records.js +94 -12
- package/dist/holmes/project/screen-text.d.ts +94 -0
- package/dist/holmes/project/screen-text.js +763 -0
- package/dist/holmes/project/spend-lock.d.ts +82 -0
- package/dist/holmes/project/spend-lock.js +413 -0
- package/dist/holmes/project/workspace-preflight.d.ts +5 -0
- package/dist/holmes/project/workspace-preflight.js +24 -1
- package/dist/holmes/refresh/freshness-coordinator.d.ts +1 -1
- package/dist/holmes/refresh/freshness-coordinator.js +1 -1
- package/dist/holmes/review/condition-hunk-replay.js +4 -2
- package/dist/holmes/review/confidence-calibration.d.ts +1 -1
- package/dist/holmes/review/confidence-calibration.js +1 -1
- package/dist/holmes/review/content-verify.js +1 -1
- package/dist/holmes/review/hop-ablation.d.ts +4 -4
- package/dist/holmes/review/hop-ablation.js +5 -5
- package/dist/holmes/review/point-in-time-replay.js +12 -3
- package/dist/holmes/review/rank-diagnosis.d.ts +2 -2
- package/dist/holmes/review/rank-diagnosis.js +1 -1
- package/dist/holmes/review/replay-corpus.d.ts +10 -4
- package/dist/holmes/review/replay-corpus.js +25 -9
- package/dist/holmes/review/requirement-triage.js +2 -2
- package/dist/holmes/review/semantic-arm.d.ts +3 -3
- package/dist/holmes/review/semantic-arm.js +3 -3
- package/dist/holmes/review/test-outcomes.js +3 -1
- package/dist/holmes/review/test-runner.d.ts +11 -0
- package/dist/holmes/review/test-runner.js +31 -10
- package/dist/holmes/review/test-selection-breadth.js +2 -2
- package/dist/holmes/review/verdicts.d.ts +109 -7
- package/dist/holmes/review/verdicts.js +653 -34
- package/dist/holmes/rtm/anchor-census.d.ts +9 -0
- package/dist/holmes/rtm/anchor-census.js +151 -0
- package/dist/holmes/rtm/anchor-ids.d.ts +25 -1
- package/dist/holmes/rtm/anchor-ids.js +45 -2
- package/dist/holmes/rtm/comment-ranges.d.ts +2 -0
- package/dist/holmes/rtm/comment-ranges.js +104 -0
- package/dist/holmes/rtm/counted-tests.d.ts +1 -0
- package/dist/holmes/rtm/counted-tests.js +63 -0
- package/dist/holmes/rtm/impact-advisory.d.ts +1 -1
- package/dist/holmes/rtm/known-defects.js +1 -1
- package/dist/holmes/rtm/localize.js +1 -1
- package/dist/holmes/rtm/taint-benchmark.d.ts +1 -1
- package/dist/holmes/rtm/taint-vocabulary.d.ts +1 -1
- package/dist/holmes/rtm/test-scope.d.ts +31 -0
- package/dist/holmes/rtm/test-scope.js +166 -5
- package/dist/holmes/rtm/trace-gaps.js +1 -1
- package/dist/holmes/runtime/dispatch.d.ts +10 -0
- package/dist/holmes/runtime/dispatch.js +12 -1
- package/dist/holmes/semantic/cloud-usage.d.ts +1 -1
- package/dist/holmes/semantic/cloud-usage.js +1 -1
- package/dist/holmes/semantic/unreadable-paths.d.ts +1 -1
- package/dist/holmes/semantic/unreadable-paths.js +1 -1
- package/dist/holmes/spec/approval-blockers.js +1 -1
- package/dist/holmes/spec/entity-store.d.ts +6 -1
- package/dist/holmes/spec/entity-store.js +16 -2
- package/dist/holmes/spec/entity-transaction.d.ts +7 -2
- package/dist/holmes/spec/entity-transaction.js +87 -170
- package/dist/holmes/spec/spec-store.d.ts +12 -6
- package/dist/holmes/spec/spec-store.js +4 -2
- package/dist/holmes/spec/spec-types.js +1 -1
- package/dist/holmes/spec/succession-guard.d.ts +56 -0
- package/dist/holmes/spec/succession-guard.js +187 -0
- package/dist/holmes/spec/succession.d.ts +70 -0
- package/dist/holmes/spec/succession.js +171 -0
- package/dist/holmes/spec/transition-policy.d.ts +2 -2
- package/docs/install-guide.md +9 -3
- package/docs/language-support.md +78 -0
- package/package.json +4 -3
- package/playbooks/author-slice/PLAYBOOK.md +1 -1
- package/playbooks/promote-slice/PLAYBOOK.md +5 -1
- package/playbooks/publish/PLAYBOOK.md +45 -33
- package/dist/holmes/review/manual-baseline.d.ts +0 -209
- package/dist/holmes/review/manual-baseline.js +0 -2847
package/README.md
CHANGED
|
@@ -5,12 +5,14 @@
|
|
|
5
5
|
[](https://github.com/holmes-kit/holmes-kit/blob/main/LICENSE)
|
|
6
6
|
|
|
7
7
|
> **"No Spec, No Code"** — Deterministic Agentic Software Engineering (ASE) harness with causal traceability.
|
|
8
|
+
>
|
|
9
|
+
> Its hook prevents accidents. Its resistance to forgery has not been verified: it is not a security boundary against the same user's agent shell.
|
|
8
10
|
|
|
9
11
|
<!-- holmes-kit:attest:begin -->
|
|
10
12
|

|
|
11
13
|
|
|
12
|
-
**
|
|
13
|
-
Measured at `
|
|
14
|
+
**536/536** source files (100%) trace to an approved spec · **1170/1266** approved A-SPECs (92.4%) are anchored from code.
|
|
15
|
+
Measured at `b487a60cb479` (specs `sha256:4432137ee912`) — reproduce with `holmes-kit attest --exclude docs/goals/probes/`.
|
|
14
16
|
<!-- holmes-kit:attest:end -->
|
|
15
17
|
|
|
16
18
|
---
|
|
@@ -22,17 +24,31 @@ Measured at `622ce26a4958` (specs `sha256:35b66c9f8ccd`) — reproduce with `hol
|
|
|
22
24
|
---
|
|
23
25
|
|
|
24
26
|
### 🛡️ Currently Supported Features (Production Features)
|
|
25
|
-
- **
|
|
26
|
-
- **
|
|
27
|
-
-
|
|
27
|
+
- **The gate says what it judges, and run start judges what wiring launches** *(new in 0.40.0)*:
|
|
28
|
+
- **A shell command that builds a path into `.ax` while it runs** is judged by the same not-a-read rule as one that names a protected path. The refusal says how the command was read and what to do first. This rule prevents accidents; its resistance to forgery has not been verified. Replaying 1,000 commands agents really wrote against 0.39's rules on the real hook, two samples gave 1 and 4 newly refused (0.1% and 0.4%). That corpus ran on the Claude Code input shape only.
|
|
29
|
+
- **`run start`** passes `mcp` and `gate` only for what launches holmes-kit's own entries, not for wiring that merely names it (breaking). `--provision` now covers a Codex worktree's MCP table; Antigravity run start is refused until its loading of a linked worktree's `.agents` is measured (breaking).
|
|
30
|
+
- **The operator judgement knows cursor-agent and opencode**, from their published package and source, and a user or project file may add to that catalog. Attestation of the in-session approval form is stricter, and is not strong proof against an agent of the same user.
|
|
31
|
+
- **`approve` decisions take an id, or a prefix of eight or more characters that names one request** (breaking): a list number is refused. The approval queue otherwise keeps its 0.39 behaviour; its redesign is 0.41's.
|
|
32
|
+
- The CHANGELOG's Known limitations name the rest. The hook is not a security boundary against the same user's agent shell.
|
|
33
|
+
- **An orchestrator's runs carry their own wiring and review policy** *(new in 0.39.0)*:
|
|
34
|
+
- **`run start --provision`** makes a Claude Code worktree governed. It writes the worktree's `.mcp.json` and `.claude/settings.local.json`, and only where git ignores them. They are pinned to the CLI's own build, no secret is copied, and nothing is left behind when the worktree is removed. In 0.39.0 Codex and Antigravity runs are refused by name; 0.40.0 adds Codex (above).
|
|
35
|
+
- **`--review-rounds <1-20>`** stops a run as `review.unresolved` once its failing independent reviews reach the cap, and names the unresolved findings. **`--strict-review`** also blocks on open important findings, at transitions and at Stop.
|
|
36
|
+
- **`approval_withdraw`** lets a session withdraw a request its own MCP server filed. Another session's request is refused.
|
|
37
|
+
- **A stale MCP server says so.** A running server reports `serverStale` on every tool result once the install it loaded has changed. `workspace_preflight` checks its build, and `doctor` and the session banner name every holmes-kit server that started before the last upgrade.
|
|
38
|
+
- **Full autonomy mode — judgments inside the scope end at once, apart from spec staging** *(new in 0.38.0)*:
|
|
39
|
+
- **Issuing.** `holmes-kit autonomy full --scope <dir>` issues a user-level profile. The person issues it once, in the session's approval form; holmes-kit never issues it for an agent.
|
|
40
|
+
- **Not a security boundary against the same user's agent shell.** The hook's goal is to prevent accidents; resistance to forgery has not been verified and is not claimed. A grant the agent itself produced is not told apart from an operator's; the gate refuses only the shell commands whose path into `.ax` it can see in the command text. The root fix, grant files kept where the agent cannot write, is planned as a follow-up in the next version (0.41). See the CHANGELOG's Known limitations.
|
|
41
|
+
- **Inside the scope**, a judgment ends at once, except that spec staging in a form the gate recognises still asks for an approval (A-SPEC-792.31):
|
|
28
42
|
- A seal the grader hands to a person seals as `full-autonomy:`. An un-admitted REQ or an undeclared or unknown grade is refused, and the refusal names its fix.
|
|
29
43
|
- A workspace-local destructive git act, or an `rm -rf` inside the scope, passes after a restorable recovery point is written under `refs/holmes/full/`.
|
|
30
|
-
-
|
|
44
|
+
- Every other act the gate already refuses is refused with a route and never queued: secrets, config, approval or ledger writes (in the forms the gate's text judgement recognises), and a recursive delete outside the scope. Outside spec staging, a headless benchmark run does not wait on a person.
|
|
45
|
+
- **BREAKING: push and publish follow the flags** *(new in 0.40.0)*. A `git push` or `npm publish` the gate reads in the command's clauses is refused without `--allow-push` or `--allow-publish`, and a grant does not lift it. A help or dry-run form passes, except that a force push with such a flag is still refused while the push flag is off. The gate reads a limited set of command forms; the CHANGELOG's Known limitations name the classes it does not read. With or without the flag, in a repository holding a spec change that no approval staged, the spec-change check refuses a push first, a command that only names a push included; a publish has no such check. Issuing a profile again replaces every flag: one issued with `--no-architecture` returns to approving architecture documents unless the flag is named again.
|
|
46
|
+
- **Not judged.** A plain write outside the scope gets no decision, so REQ-792's criterion that such an act is refused is not met in 0.40.0.
|
|
31
47
|
- **Revoking.** `--revoke` ends the profile.
|
|
32
|
-
- **
|
|
48
|
+
- **The agent does not type approval commands.** The agent's refusal tells it to call `approval_ask` with the id. The operator's own screens (the non-TTY hint and the refusal-log footer) still print an `approve --grant <id>` line for a person to paste.
|
|
33
49
|
- **Shell grants** last until they are used.
|
|
34
|
-
- **Approvals happen in the session, not in a separate terminal** *(new in 0.37.0 —
|
|
35
|
-
- **An orchestrator can run governed agents, and reviews become gates** *(new in 0.36.0)*: `holmes-kit run start --worktree <dir> --engine claude|codex|agy [--scope <A-SPEC>]…` opens a run that pins the CLI, MCP and hook builds, prints the headless command and a stop key, and ends only with that key (`run status`, `run transition`, `run stop`). Inside a run
|
|
50
|
+
- **Approvals happen in the session, not in a separate terminal** *(new in 0.37.0 — gate fix, upgrade recommended; the hook prevents accidents and is not a security boundary)*: a refusal now ends with `Agent: call approval_ask with id "req-…"`. The MCP tool `approval_ask` shows that request in the harness's approval form, and the person's answer is recorded exactly as `holmes-kit approve` records it. That covers shell, config and code-write approvals (on Claude Code today; Codex and Antigravity are a named gap until measured) and a request a run awaits. `review_verdict` records an independent review verdict the same way. The form waits for the person (no 240-second limit). `approve --grant`, `--watch` and `autonomy on` refuse from a process they judge to be an agent's, the session's `!` included, within the limits the CHANGELOG names: through 0.36.1 an agent could approve its own refused command by running the command its refusal printed. A grant the agent itself produced is not told apart from an operator's either.
|
|
51
|
+
- **An orchestrator can run governed agents, and reviews become gates** *(new in 0.36.0)*: `holmes-kit run start --worktree <dir> --engine claude|codex|agy [--scope <A-SPEC>]…` opens a run that pins the CLI, MCP and hook builds, prints the headless command and a stop key, and ends only with that key (`run status`, `run transition`, `run stop`). Inside a run a judgement that cannot be made refuses, within what the gate reads from a command's text: agent launches it recognises are refused, refusals are logged with a repeat stop, an approval pauses the run until the operator decides it, a declared stage machine (analysis → design → implement → review → test → done) denies the writes it recognises per stage, and Stop and push wait for an independent passing review. `holmes-kit review record|status|gate|mrp` records verdicts bound to a commit range, refuses self-review (an agent-harness ancestor process included), and assembles the merge-ready package. Every deny ends with a `[holmes-refusal]` line carrying a stable code. A project can cap its semantic tier (`semantic.maxTier`) and its automatic approval (`autonomy.ceiling`) in `ax.config.json`, and only an approval can raise either. doctor counts cloud embedding requests. `approve --withdraw` lets a run close its own request. Interactive sessions keep 0.35.25 verdicts, except for what this release adds to the gate's reading: path-less spec staging, computed shell writes, executable files and side paths under a role policy, and Claude Code's PowerShell tool on Windows. Interactive agent launches may carry the autonomy options measured to keep the child's Holmes gate. This is an interim release of the role/phase goal: the acceptance scenario with a reference orchestrator has not been run yet.
|
|
36
52
|
|
|
37
53
|
- **Agents clean up their own temporary work** *(new in 0.35.25)*: `holmes-kit scratch --new <label>` makes a directory under a per-user Holmes scratch root (`os.tmpdir()/holmes-scratch-<uid>`, mode 0700), and on macOS and Linux the gate lets an agent in Claude Code, Codex or Antigravity remove it with one plain `rm -rf <absolute path>` without an operator act; the root itself, tracked source, every other path and any compound command keep their verdict. Where another holmes-kit install sits in an ancestor `node_modules` of the workspace or the home directory (npm, Windows shims and pnpm alike), approval hints name the running install's own path so that copy cannot answer them (a PowerShell form on Windows), and doctor's `npx resolution` row names it.
|
|
38
54
|
- **You can tell whether a harness's gate actually ran here** *(new in 0.35.24)*: the PreToolUse and Stop hooks of Claude Code, Codex and Antigravity leave a git-ignored per-harness record (`.ax/state/hook-heartbeat/`, at most one write a minute, never part of a decision). `workspace_preflight` with `harness` passes `runtime-enforcement` only after that harness's PreToolUse gate was observed within 24 h and since its wiring last changed; doctor shows one `hook observed (<harness>)` row each; `runtime-binding status` reports `activation` for this selection's gate and names every other observation and an outdated deployed dispatcher. `runtime_binding` answers an unbound workspace with its routing instead of "not registered", init states a Codex verdict for registry-owned Codex files, and doctor FAILs a running Stop hook under 75 s. Measured need: a Codex session in a release-routed workspace concluded it was ungoverned.
|
|
@@ -42,28 +58,28 @@ Measured at `622ce26a4958` (specs `sha256:35b66c9f8ccd`) — reproduce with `hol
|
|
|
42
58
|
- **The analysis names the unchanged files a change has broken** *(new in 0.35.16)*: with `changedFiles` given, `maintenance_analyze` reports under `impacts.removedNameUsers` every unchanged file that imports a changed file and still uses a top-level name that file no longer defines (removed or renamed), and the files still importing a deleted TypeScript/JavaScript file. Deterministic and read-only; TypeScript/JavaScript and Python. Measured on public repositories: every file named was one the commit did change (22 of 22, 21 of 21). It fires rarely — 2–7% of the files an incomplete change set was missing. Member names and changed signatures are not read.
|
|
43
59
|
- **The analysis names the file a change still has to create** *(new in 0.35.15)*: with `changedFiles` given, `maintenance_analyze` reports under `impacts.missingNewFiles` every relative import a changed TypeScript/JavaScript file newly introduces that resolves to nothing — the importing file, the specifier and the candidate paths. Deterministic and read-only. On two unseen windows of a public TypeScript monorepo every naming was a file the change did create (precision 1.000), covering 78–86% of the not-yet-existing files an incomplete change set was missing. Only uncommitted changes in a git repository; other languages, bare package names and path aliases are not read.
|
|
44
60
|
- **ES-module TypeScript projects get their import graph** *(new in 0.35.14 — fix)*: a specifier written `./x.js` for a `x.ts` source (the ESM convention) now resolves, where it used to emit no edge at all — on a public TypeScript monorepo the graph went from 3 import edges to 4,628 of 6,854 import relations. Extensionless projects are unchanged. The cycle ratchet sees the same edges. Workspace package names are still unresolved, and the graded impact list does not yet use import edges.
|
|
45
|
-
- **The impact list also knows where work is concentrating, and a release
|
|
61
|
+
- **The impact list also knows where work is concentrating, and a release is refused when its badge has not moved since the last tag** *(new in 0.35.13)*: for a named change, `impacts.rankedImpact` is fused once more with each file's recency-weighted change frequency (same single `git log`; rows may carry `changeFrequency`). On 703 replayed changes neither corpus had been measured on before, recall among the ten rose 0.485 → 0.545 and 0.378 → 0.540 on a second, Python repository (both above the minimum detectable effect) and 0.521 → 0.551 / 0.419 → 0.477 here; precision rose detectably on all four windows. Stated plainly: against the modelled human engineer this project aims at (`docs/NORTH-STAR.md` — recall 0.67–0.78, precision ≈ 0.9) recall is still below the band and precision about a sixth. Separately, `npm publish` now refuses when the README shows the attest badge and `.ax/badges/traced.svg` was not re-measured since the previous release.
|
|
46
62
|
- **What else moves when you change this file — ranked by history too** *(new in 0.35.12)*: when `maintenance_analyze` is given `changedFiles`, its graded impact list (`impacts.rankedImpact`) fuses the call-graph ranking with recency-weighted co-change from git history (files committed together with the changed ones, recent commits counting more). On replayed changes of a second, Python repository a file that really changed with the named one is among the ten shown with recall 0.44 instead of 0.34 (beyond the minimum detectable difference, and replicated on further changes); on this repository the difference is positive and not detectable. Walking the call graph deeper was measured at the same time and not adopted: it reaches more and ranks worse.
|
|
47
63
|
- **The graph states what the code does, and intake answers in one call** *(new in 0.35.11)*: three corrections to what the traceability graph and `requirement_triage` say, each measured before it was built. `requirement_triage` ranked every requirement lineage on the first 64 distinct words of its text; it now reads the whole text (right lineage in the top five: 0.28 → 0.66 on this repository, 0.76 → 0.85 on a second one, both beyond the minimum detectable difference). A call with `persist: true` waits up to 20 seconds for the refresh it requested instead of returning `ambiguous` and asking to be repeated (`HOLMES_TRIAGE_WAIT_MS` sets the bound, 0 turns it off). `maintenance_analyze` lists `relevantTests` in relevance order — tests named after the changed file first — so the ten a bounded response shows are no longer the alphabetically first ten (a test the change also touched is among them with recall 0.48 instead of 0.21 here). TypeScript `calls` edges are bound by the compiler's symbol resolution — 21% of the name-bound edges linked a standard-library call such as `xs.map()` to an unrelated symbol — using only the files the scan already read plus TypeScript's bundled library; and an `@implements` anchor written in or directly above a function links the spec to that function instead of to every function of the file. **What is not claimed:** on replayed changes neither graph correction moved what `maintenance_analyze` returns beyond the minimum detectable difference; they change what the graph states, and the CHANGELOG records one measured cost.
|
|
48
|
-
- **The protected store is recognised
|
|
64
|
+
- **The protected store's spelling is recognised in a shell command's text** *(new in 0.35.2 — gate fix, upgrade recommended; the hook prevents accidents and is not a security boundary)*: through 0.35.1 a path into `.ax/specs`, `.ax/ledger`, `.ax/approvals` or `.ax/state` written directly after a shell expansion, a variable, or a character the shell removes at run time was not seen as protected, so a removal, move or overwrite of governance state could pass the gate. The store spelling now counts wherever it appears in a command, and an output redirect to a computed target is not a read. Reads still pass. A directory that merely ends in `.ax` and has a child named like the store's is judged as the store. Limit: a path assembled so the spelling never appears in the command text is outside this rule.
|
|
49
65
|
- **The session-start banner in Codex** *(new in 0.35.8)*: with a runtime registry, `runtime-binding setup --activate-hooks codex` (or the `runtime_binding` tool) adds a SessionStart entry to the workspace's `.codex/hooks.json`, so a Codex session starts by being told which Holmes build governs it and whether autonomous approval is on — as Claude Code sessions are. It runs after you trust it in Codex's `/hooks`. Antigravity passes no hook output to the model, so nothing is wired there.
|
|
50
66
|
- **The Stop hook leaves other repositories alone** *(new in 0.35.7 — upgrade recommended for Codex users)*: Codex wires the Holmes Stop hook at user level, so it is called in every repository on the machine. Through 0.35.6 it blocked the end of a turn in a repository that is not a Holmes project (`[ART-1] … no @implements anchor`). It now answers nothing where no project can be found; inside a project nothing changes.
|
|
51
67
|
- **Re-apply a registered runtime binding without leaving the session** *(new in 0.35.6)*: the MCP tool `runtime_binding` previews and applies the plan `runtime-binding setup` would make for the registered workspace, including `activate_hooks`. It never chooses a build — it uses the package the operator registry already names — and it writes only when you answer approve in the approval dialog, which shows the plan digest and the files. No answer, a denial, a client without the dialog, or autonomous approval write nothing and leave the usual queue request. Native hook trust in Codex is still given in Codex's `/hooks`.
|
|
52
|
-
- **`doctor` shows when a checkout's hooks are not the ones its sessions run** *(new in 0.35.5)*: when you develop Holmes-Kit itself with sessions routed to a released install, the `development hooks` row compares the compiled files and has both hook programs judge the same payloads, so a hook change that is not live yet is visible instead of assumed. In the same release, `runtime-binding setup` refuses a plan that would write the Codex gate where Codex has it switched off *(
|
|
53
|
-
- **No in-session shortcut around a person while autonomy is on** *(new in 0.35.4 —
|
|
54
|
-
- **An unanswered approval is held, never approved** *(new in 0.35.3 —
|
|
68
|
+
- **`doctor` shows when a checkout's hooks are not the ones its sessions run** *(new in 0.35.5)*: when you develop Holmes-Kit itself with sessions routed to a released install, the `development hooks` row compares the compiled files and has both hook programs judge the same payloads, so a hook change that is not live yet is visible instead of assumed. In the same release, `runtime-binding setup` refuses a plan that would write the Codex gate where Codex has it switched off *(gate fix; the hook prevents accidents and is not a security boundary — if you ran setup with 0.35.2–0.35.4, check `doctor` for `FAIL codex user hooks`)*.
|
|
69
|
+
- **No in-session shortcut around a person while autonomy is on** *(new in 0.35.4 — gate fix, upgrade recommended; the hook prevents accidents and is not a security boundary)*: on a client without the MCP form dialog, the `approval_commit` continuation is no longer offered or accepted while autonomous approval is on — the request goes to the approval queue. Its only human check is the host's own tool confirmation, which an allow rule or auto mode removes. With autonomy off it works as before; seals made through it are recorded as `host-gated:<harness>`.
|
|
70
|
+
- **An unanswered approval is held, never approved** *(new in 0.35.3 — gate fix, upgrade recommended; the hook prevents accidents and is not a security boundary)*: with autonomous approval on, an in-session approval dialog that ran out of time used to be recorded as an approval (actor `autonomous-timeout:<harness>`) — for exactly the seals and critical-finding resolutions autonomy reserves for a person. An unanswered dialog now returns the request to the approval queue in every mode. To audit earlier sessions, search the provenance ledger for `autonomous-timeout`.
|
|
55
71
|
- **Approvals that fit how people work** *(new in 0.35.2)*: an approval for a request that carries the approved content's digest (a spec seal) no longer expires after 30 minutes — it stays valid until used, revoked, or the content changes (`--ttl` still bounds it; requests without a digest keep the default). With autonomous approval on, a gate change declared `gate-behavior: tightens — …` or `gate-behavior: wording — …` is sealed without the operator; any other gate change still asks, and a seal handed to the operator says which rule handed it over. On a machine with a runtime registry the in-session approval dialog is reachable again, and `init`/`upgrade` no longer replace wiring the registry owns.
|
|
56
72
|
- **Separate development and consumer runtimes** *(new in 0.35.0)*: `runtime-binding setup` explicitly registers a checkout and its built package in an operator-owned registry. Normal Claude, Codex and Antigravity launches select that development package for the registered workspace; other workspaces select the configured release. Missing or conflicting bindings refuse with diagnosis instead of silently switching builds. Setup previews exact changes and requires authority for a changed installation; a validated unchanged plan needs no new grant. Normal migration preserves disabled hooks and native trust. `--activate-hooks` explicitly restores selected Holmes entries, while native trust and global disable switches still require native review. See [development runtime setup and recovery](docs/install-guide.md#development-and-consumer-runtime-binding) for the workflow and current approval limitation. Configuration readiness does not prove live three-harness enforcement.
|
|
57
73
|
- **Bounded routed-hook recovery** *(new in 0.35.0)*: routed hooks share an 18-second input/selection/execution budget and allow up to 8 seconds for owned-process cleanup. Failure reports the selected runtime and diagnosis commands, retains unresolved findings, and directs an approved repair followed by retry of the original operation. Cleanup uncertainty is reported; persistent MCP sessions have no hook lifetime deadline. Literal recovery prompts and recognized installer previews are distinguished from actual shell writes without permitting command substitutions or protected output targets.
|
|
58
74
|
- **Maintenance evidence survives the RED commit, and test evidence records what ran** *(new in 0.35.0)*: persisted `maintenance_analyze` evidence includes the request and explicit `changedFiles`, allowing the pre-edit advisory to cover named new files and analyses up to 20 ancestor commits back when every intervening change is covered. A passing `test_run` records the tree captured before execution, so edits made during a run remain unverified changes. The static test counter handles literals and same-file aliases, and recognizes suite skips only in code. The shared shell gate accepts read-only loops, prose literals, and commit messages mentioning `.ax`, and classifies file redirects using `>&` and `>|` as protected writes where applicable.
|
|
59
|
-
- 📖 **Reading `.ax` from the shell is a read, and a docs fix does not re-run the whole release suite** *(new in 0.34.0)*: the gate splits shell commands at operators outside quotes and substitutions, judges every command substitution it would run, and knows literal `cd`, `pwd`, `sleep`, `seq`, `pgrep`, clock-reading `date`, `git -C` and `while`/`until` loops — so `grep "a\|b" .ax/…`, `f=$(find .ax/specs …)` or `until grep -q … .ax/…; do sleep 20; done` no longer file an approval request, while
|
|
75
|
+
- 📖 **Reading `.ax` from the shell is a read, and a docs fix does not re-run the whole release suite** *(new in 0.34.0)*: the gate splits shell commands at operators outside quotes and substitutions, judges every command substitution it would run, and knows literal `cd`, `pwd`, `sleep`, `seq`, `pgrep`, clock-reading `date`, `git -C` and `while`/`until` loops — so `grep "a\|b" .ax/…`, `f=$(find .ax/specs …)` or `until grep -q … .ax/…; do sleep 20; done` no longer file an approval request, while the write forms the gate recognises are still refused (and `echo "$(sh -c …)"` now is). `sed -i` is judged by the files it edits, not by the words in its script. After a full release lane, `node scripts/verify-release.js --inherit-release-test-lane` lets a commit that changes only `README.md` or unshipped `docs/` files publish on the full lane's receipt by running just the docs tests; the publish check recomputes that diff with git. `requirement_triage` counts a lineage with sub-slices as approved, and an autoreload MCP launcher exits when its client goes away.
|
|
60
76
|
- 🗜️ **Large answers are compressed, not cut, and new requirements are not blocked by a guess** *(new in 0.33.0)*: `spec_list`, `review_status` and `reverse_scan` answer by default with a compressed view — duplicates removed, digests dropped, what needs action first, anything left out counted with a note — and `detail: "full"` (or paging, or `spec_list({ ids })` for one spec) gives the complete answer. `requirement_triage` confirms a lineage only when both of its channels agree and the lineage mentions every code identifier the request names, so a requirement next to a finished one, or on an install without a semantic layer, can still be admitted. `maintenance_analyze` judges a Korean or Japanese request against unreadable files by its words and, on the cloud tier, by meaning; the pre-edit gate finds the analysis the session persisted; `spec_approve` names a spec's blockers instead of queueing an approval nobody could use; and `holmes-kit autonomy status`/`off` read the project default in `.mcp.json`, so `off` never claims OFF while autonomous approval is still on.
|
|
61
77
|
- 🔎 **The analysis tools decide on evidence about the request, and say what they could not decide** *(new in 0.32.0)*: measured on two repositories by point-in-time replay, `maintenance_analyze` had answered `ambiguous` for every request because a shell script anywhere in the tree counted against it — the classification now counts an unreadable language only when the change touches it, while the test scope stays as conservative as before (relaxing it too let narrowed scopes miss the commit's own tests). `confidence` carries `confidenceCalibrated: false`; persisted evidence records why a scope was `full` and `maintenance_calibration` reports how often each cause occurred; candidate specs come in relevance order. `requirement_triage` answers in summaries by default (`detail: "full"` for document text), counts semantic coverage over documents that can have a vector, and gives `existing-change`/`fulfilled` only when its lexical and semantic channels agree on the first-ranked lineage — a lineage the request cites is listed first but a citation is not evidence — otherwise `ambiguous`, which leaves a new requirement possible.
|
|
62
78
|
- 🚦 **The gate only ever denies** *(changed in 0.31.0)*: an action Holmes does not deny is left to your harness's own permission flow — Claude Code and Codex get no permission decision, Antigravity gets `ask` (or `allow` for a read inside the workspace that git does not ignore). Earlier versions answered `allow`, which Claude Code treats as "bypassing permission prompt", so anything the shell model missed ran unconfirmed. In Claude Code's default mode you now see its confirmations again, as without Holmes.
|
|
63
79
|
- 🪝 **The Codex gate loads again on codex-cli 0.155** *(new in 0.31.0)*: plugin hooks were removed upstream, so `init --agent codex` wires the Holmes PreToolUse and Stop kernels into the user-level `$CODEX_HOME/hooks.json`, keeps every hook it does not own, and `--remove` takes away only its own groups. Codex runs a user hook only after you trust it once with `/hooks`; Holmes never forges that trust, and `doctor` says so instead of claiming enforcement.
|
|
64
|
-
- 🧭 **The shell gate judges by identity, from where the command really runs** *(new in 0.31.0)*: wiring files
|
|
80
|
+
- 🧭 **The shell gate judges by identity, from where the command really runs** *(new in 0.31.0)*: wiring files and the `.ax` store are judged as shell WORDS in the command's text, resolved against each segment's real base — a `cd` moves the base only when it is certain to have run, an uncertain or expanded one (`cd .a?`, a link made in the same command, `cd "$X"`) leaves it unknown and the command is judged at every base it could have produced, and the base starts at the harness's own working directory (the payload `cwd`, a Codex `workdir`), not the project root. An evaluation runs under a deadline that refuses when it passes. The Codex oracle asks the installed Codex whether your config loads — locally, over copies, with plugins and every proxy closed, `sqlite_home`/`analytics`/`otel` isolated from the user copy alone, and a verdict it could not obtain labelled `approximate`. Source walkers skip nested git working trees only when git says the tree is not the project's, read regular files only, and ask git once per scan; the gate-path readers that release measured read linearly in their input.
|
|
65
81
|
- 🪟 **Approval stays inside the agent session** *(new in 0.29.0)*: Claude Code, Codex, and Antigravity use the same capability-negotiated route. Holmes opens a direct MCP form only when that live client advertises `elicitation.form`; otherwise it exposes one sensitive, challenge-bound `approval_commit` continuation in the same agent session *(not while autonomous approval is on, since 0.35.4 — the request is queued instead)*. The host may render its native tool confirmation, but its arrival is recorded as `host-gated`, never claimed as proof that a human answered. The server issues an opaque, memory-only intent bound to the action kind, target, subject digest, workspace and MCP run; only one matching retry can consume it. No `config.toml` value or persisted `HOLMES_APPROVAL` is authority. The `holmes-kit approve` TUI is recovery-only when a session cannot present approval. Under autonomous mode, eligible low-risk work stays automatic and an ordinary unclassified HITL request queues without interrupting the agent; high-risk or irreversible work is shown in the session and waits for an answer. Timeout, cancel, deny, malformed and unavailable outcomes never approve *(timeout: since 0.35.3)*.
|
|
66
|
-
- 🧾 **A new prompt is checked against governed intent before it becomes a new spec** *(new in 0.29.0)*: `requirement_triage` reads the approved REQ/H-SPEC/A-SPEC/T-SPEC lineage, a receipt-bound current RTM graph, source and requirement-document semantic coverage, code anchors, and exact-HEAD execution evidence before recommending `fulfilled`, `existing-change`, `new`, or `ambiguous`. BM25 is always present; a verified local BGE-M3 cache and explicit Gemini opt-in add candidates and also enter the ranking score, so when lexical evidence is weak or tied a semantic match can decide which lineage leads — every such answer shows its semantic coverage, and a run that used no semantic score says `lexicalOnly: true`. A cold, stale, unreadable, failed, partial, or absent lane remains visible as ambiguity; a workspace with no semantic tier, or with transfer switched off by `HOLMES_NO_SEMANTIC_WARM`, runs **lexical-only** — it can still author a new REQ, and the answer and its evidence say `lexicalOnly: true` (set it in the environment of both your harness — its hooks spawn the background refresh — and the Holmes MCP server; a refresh recorded as suppressed also keeps triage from embedding. The switch stops automatic transfer: the background refresh embeds neither source nor requirement documents, and `requirement_triage` does not embed the prompt; tools you invoke explicitly under an opted-in cloud tier — `maintenance_analyze`, `issue_localize`, `rtm_reindex` — still embed their query or index as before). The detached refresh worker warms both versioned semantic populations under existing cloud-consent rules; a persisted v2 artifact binds prompt, workspace, HEAD, and receipt generation. New REQ creation — through `spec_create` or `spec_slice_init` — verifies that evidence at one shared MCP boundary,
|
|
82
|
+
- 🧾 **A new prompt is checked against governed intent before it becomes a new spec** *(new in 0.29.0)*: `requirement_triage` reads the approved REQ/H-SPEC/A-SPEC/T-SPEC lineage, a receipt-bound current RTM graph, source and requirement-document semantic coverage, code anchors, and exact-HEAD execution evidence before recommending `fulfilled`, `existing-change`, `new`, or `ambiguous`. BM25 is always present; a verified local BGE-M3 cache and explicit Gemini opt-in add candidates and also enter the ranking score, so when lexical evidence is weak or tied a semantic match can decide which lineage leads — every such answer shows its semantic coverage, and a run that used no semantic score says `lexicalOnly: true`. A cold, stale, unreadable, failed, partial, or absent lane remains visible as ambiguity; a workspace with no semantic tier, or with transfer switched off by `HOLMES_NO_SEMANTIC_WARM`, runs **lexical-only** — it can still author a new REQ, and the answer and its evidence say `lexicalOnly: true` (set it in the environment of both your harness — its hooks spawn the background refresh — and the Holmes MCP server; a refresh recorded as suppressed also keeps triage from embedding. The switch stops automatic transfer: the background refresh embeds neither source nor requirement documents, and `requirement_triage` does not embed the prompt; tools you invoke explicitly under an opted-in cloud tier — `maintenance_analyze`, `issue_localize`, `rtm_reindex` — still embed their query or index as before). The detached refresh worker warms both versioned semantic populations under existing cloud-consent rules; a persisted v2 artifact binds prompt, workspace, HEAD, and receipt generation. New REQ creation — through `spec_create` or `spec_slice_init` — verifies that evidence at one shared MCP boundary, whichever harness calls it. A file an agent's own shell writes does not pass through that boundary.
|
|
67
83
|
- 🧭 **One governed operating contract survives every harness** *(new in 0.28.0)*: the common managed block in `AGENTS.md` carries the same No Spec, No Code rules to Claude Code, Codex CLI, and Antigravity while leaving the repository's own rules outside the block intact. `holmes-kit guidance check` names a stale or locally conflicted managed block, `guidance refresh` first plans the change and then replaces only the Holmes-owned region, and `doctor` runs the same check. An installer or upgrader cannot silently discard local guidance.
|
|
68
84
|
- 🧷 **A worktree can prove which workspace the MCP server serves before an edit** *(new in 0.28.0)*: `workspace_preflight` returns the bound root/store identity and reports a foreign caller as a mismatch without registering, rebinding, or writing anything. `holmes-kit doctor --agent claude|codex|antigravity` checks each harness's local wiring prerequisites and states that preparation is not evidence of live hook enforcement. This is paired with a packaged Superpowers compatibility playbook that preserves Holmes specifications, RED/GREEN evidence, review closure, and finish/reconciliation requirements through the corresponding Superpowers workflow. Fixture and subprocess coverage preserve neighboring configuration and foreign-root isolation; live linked-worktree and paid-harness acceptance remain explicitly unverified until observed.
|
|
69
85
|
- 📏 **Say how much of the repository is governed — as a number, not a label** *(new in 0.27.0)*: `holmes-kit attest` reports how many scanned source files are anchored to an **approved** spec, beside how many approved A-SPECs are anchored from code, and says where that is true (commit, plus a digest of the approved specs) so anyone can reproduce it. No new judgement: the scanner's files, the anchors, the existing link census. A per-file "generated under holmes-kit" header was declined — it is a claim that survives an ungoverned edit, and line 1 already carries the anchor a gate verifies. `--exclude a,b` names vendored trees at a path boundary and is echoed in every output; what cannot be measured is `n/a`, never `0%`; `100` appears only when every file is traced. `--badge` writes a self-contained local SVG, and `--readme` rewrites **only** the region between the `holmes-kit:attest` markers — a README without them is never touched, and a half marker is refused. A statement, not a gate: the numbers never change the exit code.
|
|
@@ -73,7 +89,7 @@ Measured at `622ce26a4958` (specs `sha256:35b66c9f8ccd`) — reproduce with `hol
|
|
|
73
89
|
- 🧬 **Declare your architecture, in every language the graph can follow** *(new in 0.26.0)*: a C-SPEC's `## Forbidden Edges` takes a third rule kind beside `import` and `call` — `- inherits src/app -x-> ConcreteBase`, an exact match enforced at the pre-edit gate. Nothing is inferred: the rule reads the graph's `inherits` edges and never asks which class is "abstract", which is what makes it hold in Go, where interface satisfaction cannot be inferred at all. A project that already breaks the rule it wants adopts it with a **baseline that expires** — `- allow until 2026-09-27 : inherits src/legacy/a.ts -> LegacyBase`, exact on kind, file and target, never a prefix. Past its date the allowance still holds, because an expiry that blocked would turn the rule into a barrier to adoption; it is **reported** instead, carrying `(reconfirmed n since <date>)` so a twelfth renewal cannot hide.
|
|
74
90
|
- 🏛️ **The architecture verdict reaches the person closing the turn** *(new in 0.26.0)*: the scan-wide judgement existed and nothing in the product called it — measured, zero consumers outside the tests — so an expired baseline was neither blocked nor seen, and a time-boxed allowance could not be told from a permanent pardon. The Stop hook now prints `ARCH` lines on the non-blocking `tracked` channel: violations no baseline covers, expired baselines with their renewal count, and **which rule kind could not be judged in which extension** (`inherits rules NOT judged in: .js, .py, .tsx`) — asked per kind, over the files a rule of that kind actually judges, because a pooled answer called a language *judged* for a rule it could not see. No rule declared, nothing said and nothing paid: the judgement shares the one scan the cycle ratchet already makes (measured here: scan 6.6 s, judgement 0.14 s).
|
|
75
91
|
- ♻️ **The cycle ratchet judges every language it can resolve** *(new in 0.26.0)*: the Stop hook had re-implemented import resolution beside the graph builder's — relative specifiers only, four extensions. Measured on fixtures shaped the way each language requires: 16 import edges, 2 survived; 9 planted cycles, 1 found. It cost nothing in an all-TypeScript tree (919 edges either way), which is how it survived to 0.25, and everything in a Java, Go, Python or Rust consumer. There is now **one** resolver, consumed by both; a language whose specifiers do not resolve stays `unavailable` rather than reading as clean, and a wide Go package cycle is capped per cycle with the dropped members counted.
|
|
76
|
-
- 🔑 **The id a refusal prints can be granted** *(new in 0.26.0)*: `approve --grant <id>` resolved references against the decision inbox alone, and a shell hard-HITL refusal lives in the per-machine refusal log — so the very id the refusal printed failed before the fallback that handles it could run, and the owner had nothing to approve. Id and prefix references now resolve across both stores. A **number**
|
|
92
|
+
- 🔑 **The id a refusal prints can be granted** *(new in 0.26.0)*: `approve --grant <id>` resolved references against the decision inbox alone, and a shell hard-HITL refusal lives in the per-machine refusal log — so the very id the refusal printed failed before the fallback that handles it could run, and the owner had nothing to approve. Id and prefix references now resolve across both stores. A list **number** is no longer accepted for a decision (0.40.0: it names whatever row holds it when the command runs), a prefix that collides across the stores is refused by name, an unreadable log removes candidates rather than granting, and the inbox list is unchanged.
|
|
77
93
|
- 📬 **A reporter hears that their defect was fixed** *(new in 0.26.0)*: a defect filed through `holmes-kit report` is matched — locally, once — against the list of resolved reports that ships in the package, and the session start says so. Nothing is sent anywhere.
|
|
78
94
|
- 🔦 **A semantic layer that is inert says so** *(new in 0.25.0)*: the tier line said what was CONFIGURED, never whether one lookup would succeed. Measured on this repository: the resolved tier was `cloud` and **0 of 602 scanned files** had a cached document vector under it, so every lookup returned nothing — reranking reordered nothing, alternates emitted nothing, and the output was byte-identical to a layer that examined everything and agreed. A naive check would have counted the 532 vectors sitting in the cache and called it healthy; they keyed on symbol lists that no longer existed. `doctor` now reports coverage against the files scanned NOW, through the runtime's own accessor, in four states — the two that cannot be judged say so rather than passing quietly.
|
|
79
95
|
- 🔁 **Vectors refresh on the channel that keeps the graph fresh** *(new in 0.25.0)*: the graph self-heals through the Stop hook's detached child; the vectors did not, because warming was reachable only from an explicit `rtm_reindex`. The cache key hashes the file's path plus its symbol names, so every edit that renames a symbol invalidates that file's vector — twelve days of work had taken coverage to zero. The refresh now warms too, and the Stop hook reports the verdict the child recorded rather than scanning (tree-sitter wasm must not ride into a gate process); **a missing verdict reads as "not run", never as a pass**. Warming under the cloud tier is egress, so it is automatic AND observed, with `HOLMES_NO_SEMANTIC_WARM` to switch the transfer off — an owner who switches it off is shown a switch, not a fault. The verdict records the commit it was taken at, so work merged from another machine reports **needs re-measuring** instead of yesterday's numbers as today's truth.
|
|
@@ -96,7 +112,7 @@ Measured at `622ce26a4958` (specs `sha256:35b66c9f8ccd`) — reproduce with `hol
|
|
|
96
112
|
- 🔎 **The RTM stops claiming coverage it cannot see** *(0.21.0)*: `codeLinkedPct`, `unlinkedCount` and `unlinkedByReason` join the old `coveragePct`, which read 100 while 11.4% of approved specs carried no `implements` edge — plus a Files-to-Touch fulfilment advisory and `rtm_impact` **trace gaps** (a spec that declares a changed production file yet anchors only tests).
|
|
97
113
|
- 🩹 **`@known-defect(reason, expires=YYYY-MM-DD)` and article ART-9** *(0.21.0)*: a test that pins a known defect as its expected value carries a machine-readable marker — listed as debt while live, blocking only once it has **expired** or cannot be read. A bypass is sometimes right; the marker is there so the next person can see it.
|
|
98
114
|
- 🧑🤝🧑 **Concurrent multi-agent workspace** *(0.20.0)*: several agents, machines and clones converge on one spec store through Git — replica-stamped provenance, UUID-keyed entities that renumber without losing identity or approval closure, `entity_integrate` with per-side conflict evidence, and single-use approvals whose double-spend freezes every authority-spending act until `ledger_reconcile`. Reproduced end to end outside this repository on macOS and Linux.
|
|
99
|
-
- 🗂️ **Approval decisions you can actually see** *(0.20.0)*: `approve --status` shows who asked (run · replica · workspace), the risk grade, the subject digest and exactly what a grant would open. A grant is bound to the workspace it was minted in and to the
|
|
115
|
+
- 🗂️ **Approval decisions you can actually see** *(0.20.0)*: `approve --status` shows who asked (run · replica · workspace), the risk grade, the subject digest and exactly what a grant would open. A grant is bound to the workspace it was minted in and to the subject digest shown when it was granted — a copied one is `foreign-workspace`, changed content is `stale-subject` — and `--revoke` withdraws it. A grant file proves no person made it: the agent's own shell can write one (Known limitations).
|
|
100
116
|
- 🔁 **Import cycles are governed** *(0.19.0)*: guidance reaches the agent before it designs, a `graphPreview.cycles` advisory names the cycles your declared files are already in (each edge classified `type-erasable` / `lazy-require` / `eager-value`), and a Stop-hook ratchet in `track` catches new ones — the escape is a **named exception**, never a threshold, so a project carrying legacy cycles can still adopt the harness. This repository went three cycles → zero.
|
|
101
117
|
- 📐 **Size and fan-in, shown but never judged** *(0.19.0)*: lines, symbols, longest function, fan-in and fan-out per declared file. Numbers only — a test pins the **absence** of a severity field, because one would grow into the gate the evidence does not support.
|
|
102
118
|
- 🎯 **Candidates you could actually act on** *(0.19.0)*: history-derived candidates must be able to be source (**63.3%** of emission slots were going to files that cannot be the answer), vendored trees are demoted, and def-use ranking orders symbols inside a file the search already found.
|
|
@@ -109,11 +125,11 @@ Measured at `622ce26a4958` (specs `sha256:35b66c9f8ccd`) — reproduce with `hol
|
|
|
109
125
|
**Foundations** — in place since the early releases, still load-bearing.
|
|
110
126
|
|
|
111
127
|
- 📋 **Requirements & specification governance**: strict **"No Spec, No Code"** across a 4-tier chain (`REQ ➔ H-SPEC ➔ A-SPEC ➔ T-SPEC`) with `// @implements A-SPEC-XXX` code anchors — comma-lists and every anchor in a file participate in the gate.
|
|
112
|
-
- 🔴 **Inbuilt TDD — RED-first,
|
|
113
|
-
- 🧱 **Deterministic gate
|
|
114
|
-
- 🤖 **Autonomous approval — three layers
|
|
128
|
+
- 🔴 **Inbuilt TDD — RED-first, recorded and judged** *(0.9.0)*: constitution article **ART-8** reads a recorded `red-assertion → green` sequence in the ledger, and a `red-error` (a test that could not run) is not a valid RED — so "the covering test failed *correctly*" is judged from the record, not on trust. It ships observe-first (`redFirstEvidence: track`): it reports, and blocks only under `strict`. Where superpowers *asks* for RED-first, holmes-kit *records* whether it happened.
|
|
129
|
+
- 🧱 **Deterministic gate** *(0.8.0, 0.13.0)*: shell writes are judged at the segment's **effective working directory**, the governing anchor is the whole set rather than the first match, a project is governed when **any** spec exists, and `cp`/`mv` are classified by **destination**.
|
|
130
|
+
- 🤖 **Autonomous approval — three layers** *(0.8.0, reworked 0.13.0; session UX 0.29.0)*: a project default (`init --autonomy`) and an expiring per-session envelope let the agent seal **low-risk** specs itself under an `autonomous:<client>` actor. Ordinary unclassified HITL work queues without a form; governance-critical, high-risk or irreversible work asks for an in-session confirmation (an approval the same user's agent shell can forge: Known limitations); a form that is not answered returns to the approval queue *(since 0.35.3 — it was recorded as an approval before)*. No holmes-kit tool grants autonomy to the agent (its own shell writing approval files is the Known limitation above: not a security boundary), the posture is surfaced at every session start, and off is byte-identical to a human-gated project.
|
|
115
131
|
- 🧭 **Compatibility and evolution gates** *(0.14.0, 0.15.0)*: a new A-SPEC seals only with `harness_impact:` and `os_impact:` declared and machine-cross-checked against Files-to-Touch; separately, a changed in-scope source that **newly introduces an external dependency** raises a spec-reappraisal — a warning when manual, a queued item under autonomy, never a blocked turn.
|
|
116
|
-
- 🚢 **Release autonomy + docs-currency gate** *(0.13.0, machine-checked in 0.23.2)*: `npm publish`
|
|
132
|
+
- 🚢 **Release autonomy + docs-currency gate** *(0.13.0, machine-checked in 0.23.2)*: `npm publish` runs `verify-release` through `prepublishOnly`, which refuses a dirty tree, a missing or old release test-lane receipt and a badge that has not moved, and checks the docs — a stale doc is a false claim. Without a full profile the hook gives `npm publish` no decision (measured on a scratch project); under one, it follows `--allow-publish`. The risk rules for a release are in the publish playbook and are a procedure: nothing runs the classifier for you.
|
|
117
133
|
- 🧠 **3-tier semantic layer** *(local preparation default in 0.29.0)*: BGE-M3 is prepared and verified locally during a normal npm installation (zero repository-text egress); `HOLMES_SKIP_MODEL_INSTALL=1` is the explicit opt-out. `cloud` remains the opt-in `gemini-embedding-001` tier. Measured on 305 traceability cases: recall 0.486 → 0.667 → **0.887**; on lexical-zero requests 0% → 52% → **92%**. Surfaced additively, never as a hard filter.
|
|
118
134
|
- 🎯 **Graded impact surface** *(0.3.0)*: `rankedImpact` (personalized PageRank over the spec/code graph) beat its pre-registered naive baseline on **both** recall and precision across 3 corpora (×1.6–×17) — measured before claimed.
|
|
119
135
|
- 🐞 **Causal defect localization & CPG** *(equalized in 0.5–0.7)*: AST code property graph (CFG/DDG/CDG) and dataflow taint reachability across 7 languages — **42 language×layer cells graded on measured evidence** (11 corpora, 39,344 functions, zero invariant violations; C++ conditional on 67.9% parse coverage, disclosed in the matrix).
|
|
@@ -122,10 +138,10 @@ Measured at `622ce26a4958` (specs `sha256:35b66c9f8ccd`) — reproduce with `hol
|
|
|
122
138
|
- 🔔 **Approval UX** *(0.3.1; inbox split 0.15.0; in-session recovery 0.29.0)*: the agent-session UI is primary; the tracked queue is the fallback when the client cannot present it. A form timeout is distinguished from cancel/unavailable, and in every mode it returns the request to the queue. The queue holds **decision-seeking requests only** — plain gate refusals live in a local per-machine log (raw commands never leave the machine), after 1,404 single-shot refusals were measured burying a 2-item inbox.
|
|
123
139
|
- ⬆️ **Zero-config upgrades & session banner** *(0.8.0–0.12.2)*: `holmes-kit upgrade` re-pins **every** recorded workspace in one command (`--dry-run`/`--yes`), and every session start states the version, the governance rule and any newer published version — from every harness's MCP startup, not just Claude's. The write stays your explicit choice, never a silent auto-install.
|
|
124
140
|
- 🧰 **Governance UX tools** *(0.10.0)*: `spec_unseal` (return a sealed spec to editable `draft` in one act, out-of-band approval required), `approval_status` and `ledger_timeline` for read-only observability, and a structured `conflict` on optimistic-concurrency refusal.
|
|
125
|
-
- 🚦 **Push & server-side re-validation** *(hardened in 0.8.0)*: a local `pre-push` evidence gate (test-run ledger head == push HEAD, green, executed > 0) plus a server-side workflow that re-runs `npm ci → build → full suite → tarball install probe
|
|
126
|
-
- 🧪 **Self-healing & diagnostic doctor**: integrity checks
|
|
141
|
+
- 🚦 **Push & server-side re-validation** *(hardened in 0.8.0)*: a local `pre-push` evidence gate (test-run ledger head == push HEAD, green, executed > 0) plus a server-side workflow that re-runs `npm ci → build → full suite → tarball install probe`. Where that workflow runs, a `--no-verify` push or a hook-less clone shows as a failed run; it detects, it does not prevent, and write access can change or cancel it.
|
|
142
|
+
- 🧪 **Self-healing & diagnostic doctor**: integrity checks that name the fix for each failing one (`doctor`), repair of the recovery skills (`holmes-kit skills refresh`) and of a blocked spec (`spec_remediate`), plus a live report of holmes-kit's own advertised MCP schema token cost.
|
|
127
143
|
- 🔢 **Sensible spec numbering** *(0.12.1)*: a brand-new project's first slice is **REQ-100**; existing projects keep `max(existing)+1` exactly, and 4-digit ids (including `ADR-1000+`) work cleanly.
|
|
128
|
-
- 🌐 **English CLI & hook surface** *(0.13.0)*: the operator-facing CLI, `doctor` output, hook `deny` reasons and interactive prompts are English, guarded by a hangul-absence test over the **rendered runtime output** rather than a source scan.
|
|
144
|
+
- 🌐 **English CLI & hook surface** *(0.13.0)*: the operator-facing CLI, `doctor` output, hook `deny` reasons and interactive prompts are English, guarded by a hangul-absence test over the **rendered runtime output** rather than a source scan. Not yet English: a few strings outside that test (a truncation marker, one `init --dry-run` hint) and the comments in the files `init` writes for roles and `.gitattributes`; planned for 0.41.
|
|
129
145
|
- 🤖 **CLI-first AI harness matrix**: native process hook gating for Claude Code, Antigravity CLI (AGY), Codex CLI, and the Google Antigravity SDK.
|
|
130
146
|
|
|
131
147
|
---
|
|
@@ -141,16 +157,16 @@ Holmes-Kit strives to expand into a unified enterprise SDLC harness bridging ext
|
|
|
141
157
|
|
|
142
158
|
## 🤖 Supported AI Coding Tools & Environments (CLI-First Focus)
|
|
143
159
|
|
|
144
|
-
Holmes-Kit prioritizes **CLI-based AI Coding Agents
|
|
160
|
+
Holmes-Kit prioritizes **CLI-based AI Coding Agents**, whose hooks run as OS processes before a tool acts:
|
|
145
161
|
|
|
146
162
|
| AI Coding Agent / Framework | Harness Tier | Integration & Enforcement Mechanisms |
|
|
147
163
|
| :--- | :--- | :--- |
|
|
148
164
|
| 🤖 **Claude Code CLI** | 🥇 Tier 1 (Native) | OS PreToolUse & Stop hooks (`.claude/settings.local.json`), MCP server (`.mcp.json`) |
|
|
149
165
|
| 🚀 **Antigravity CLI (AGY)** | 🥇 Tier 1 (Native) | AGY Hooks (`hooks.json`), MCP config (`.agents/mcp_config.json`), Governance Skills |
|
|
150
166
|
| 💻 **Codex CLI / Agentic Shell** | 🥇 Tier 1 (Native) | Codex MCP integration (user-level `$CODEX_HOME/config.toml`, normally `~/.codex/config.toml`, shared by every workspace), plugin-packaged gate hooks at the marketplace path Codex reads (`.claude-plugin/marketplace.json`). Hard-gate enforcement was verified on codex-cli 0.152.x; codex-cli 0.155.x removed plugin hooks (`plugin_hooks: removed`), so `init --agent codex` also wires the pre-tool and Stop gates into the user-level `$CODEX_HOME/hooks.json`, preserving your own hooks (REQ-727). **Codex runs that hook only after you trust it once: open `codex` and run `/hooks`.** Holmes never writes that trust, and `doctor` WARNs because it cannot verify it offline (live evidence: `docs/goals/EVIDENCE-live-sessions-2026-09-23.md`). |
|
|
151
|
-
| 🧩 **Google Antigravity SDK** | 🥇 Tier 1 (Native) | Autonomous Agent SDK bindings and
|
|
167
|
+
| 🧩 **Google Antigravity SDK** | 🥇 Tier 1 (Native) | Autonomous Agent SDK bindings and a hash-chained provenance ledger (tamper evidence, not prevention) |
|
|
152
168
|
|
|
153
|
-
> **Note**: Holmes-Kit focuses
|
|
169
|
+
> **Note**: Holmes-Kit focuses on CLI-based autonomous agents because they let an OS hook refuse (`deny`) an act before a file changes. The hook prevents accidents; it is not a security boundary (see the CHANGELOG's Known limitations).
|
|
154
170
|
|
|
155
171
|
---
|
|
156
172
|
|
|
@@ -174,7 +190,7 @@ Add `-DryRun` to see what it would do without installing. Exit codes: `0` ok / a
|
|
|
174
190
|
| Which situation are you in? | Privileges | Command |
|
|
175
191
|
|---|---|---|
|
|
176
192
|
| **Using it in one project** (most people) | none | `npm install --save-dev @holmes-lab/holmes-kit` |
|
|
177
|
-
| **Zero-install one-shot** (
|
|
193
|
+
| **Zero-install one-shot** (to look at it, not to keep) | none | `npx -y @holmes-lab/holmes-kit init` — npx fetches and runs; read "How the MCP server is wired" below before keeping this wiring |
|
|
178
194
|
| Company-managed PC / restricted account | none | same — no system directory is touched |
|
|
179
195
|
| CI / container | none | same, plus `--prefer-online` right after a release |
|
|
180
196
|
| CLI across many projects (`-g`) | depends | run `npm config get prefix` first — see below |
|
|
@@ -218,7 +234,8 @@ npx holmes-kit init # drop the npx prefix if you installed with -g
|
|
|
218
234
|
[ ] 💻 Codex CLI (~/.codex/config.toml)
|
|
219
235
|
```
|
|
220
236
|
*It then asks — defaulting to **No** — whether to grant **autonomous spec approval** (low-risk specs
|
|
221
|
-
self-seal; governance-critical, high-risk and irreversible
|
|
237
|
+
self-seal; governance-critical, high-risk and irreversible ones ask for an approval — which, as the
|
|
238
|
+
Known limitations say, the same user's agent shell can forge). Skip the prompt with
|
|
222
239
|
`--autonomy` / `--no-autonomy`, or turn it on later per-session with `holmes-kit autonomy on`.*
|
|
223
240
|
|
|
224
241
|
### 3. Verify Health
|
|
@@ -290,7 +307,8 @@ the consent act: with a key present, repository-derived text is sent to Google's
|
|
|
290
307
|
|
|
291
308
|
> 🔒 **Never** commit a key, pass it as a CLI argument, or put it in a file inside the project
|
|
292
309
|
> tree. Holmes-Kit's credential chain has **no project-tree source by design**, and agents are
|
|
293
|
-
> gated from setting keys on their own — consent
|
|
310
|
+
> gated from setting keys on their own — consent is meant to stay a human act (the hook is no security boundary
|
|
311
|
+
> against the same user's agent shell — Known limitations).
|
|
294
312
|
|
|
295
313
|
---
|
|
296
314
|
|
|
@@ -308,7 +326,7 @@ flowchart LR
|
|
|
308
326
|
1. **Spec First**: The agent authors requirements and architecture specs via `spec_create`.
|
|
309
327
|
2. **Test First**: The agent writes tests and approves `T-SPEC` before writing implementation code.
|
|
310
328
|
3. **Implement**: Code files anchor to their architecture spec with `// @implements A-SPEC-NNN`.
|
|
311
|
-
4. **Deterministic Guard**: If the agent attempts to write code without approved specs, **Holmes-Kit hooks block the action and provide exact next steps**.
|
|
329
|
+
4. **Deterministic Guard**: If the agent attempts to write code without approved specs in a form the gate recognises, **Holmes-Kit hooks block the action and provide exact next steps**.
|
|
312
330
|
|
|
313
331
|
---
|
|
314
332
|
|
|
@@ -325,18 +343,18 @@ flowchart LR
|
|
|
325
343
|
| `holmes-kit doctor --target <root> --registry <bindings.json>` | Diagnose the same operator registry used by custom routing installations |
|
|
326
344
|
| `holmes-kit autonomy status` | Show the current autonomous-approval posture (project default + session envelope) |
|
|
327
345
|
| `holmes-kit autonomy on --for 2h` | Self-drive low-risk specs for this session only (expiring; needs a TTY or `HOLMES_APPROVAL`) |
|
|
328
|
-
| `holmes-kit autonomy full --scope <dir>` | Full autonomy inside `<dir>` (decided once in the session approval form):
|
|
346
|
+
| `holmes-kit autonomy full --scope <dir>` | Full autonomy inside `<dir>` (decided once in the session approval form): a judgment there ends at once, apart from spec staging; `--allow-push`, `--allow-publish` (without them the gate refuses the pushes and publishes it reads), `--no-architecture`; `--revoke` ends it |
|
|
329
347
|
| `holmes-kit autonomy off` | End session autonomy immediately; if the project default in `.mcp.json` still keeps autonomy on, it says so and exits 1 instead of claiming OFF |
|
|
330
348
|
| `holmes-kit semantic-setup` | Download and verify the local `bge-m3` model (retry/recovery; shared across projects) |
|
|
331
349
|
| `holmes-kit semantic-check` | Verify local inference **offline**, without downloading anything |
|
|
332
350
|
| `holmes-kit semantic-key set` | Store the cloud-tier key outside the tree (stdin only, never argv) |
|
|
333
351
|
| `holmes-kit approve --status` | The whole approval picture: workspace, delegation, per-request risk/run/subject/grant preview, recent outcomes |
|
|
334
352
|
| `holmes-kit approve --watch` | Resident decision surface: decide with one key as requests arrive (prints the status picture before each new item) |
|
|
335
|
-
| `holmes-kit approve --grant <
|
|
336
|
-
| `holmes-kit approve --deny <
|
|
353
|
+
| `holmes-kit approve --grant <id>` | Mint the narrow, workspace- and subject-bound grant for one request (`--ttl`, `--rationale`); `<id>` is the id under the request or a prefix of eight or more characters no other request shares — a list number is refused; check the subject digest the decision line names, since a re-filing can carry another subject under the same id |
|
|
354
|
+
| `holmes-kit approve --deny <id> --reason <text>` | Record a denial the agent sees on its next attempt |
|
|
337
355
|
| `holmes-kit approve --revoke <id> --reason <text>` | Withdraw a live grant; the request must be decided again |
|
|
338
356
|
| `holmes-kit doctor` | Comprehensive health check of specs, hooks, MCP, and anchors |
|
|
339
|
-
| `holmes-kit
|
|
357
|
+
| `holmes-kit skills refresh` | Reinstall the recovery skills holmes-kit owns; for any other failing check, `doctor` names the fix |
|
|
340
358
|
| `holmes-kit ci` | Run non-interactive headless governance gate for GitHub Actions / GitLab CI |
|
|
341
359
|
| `holmes-kit ci --json` | Run CI gate and emit machine-readable JSON results |
|
|
342
360
|
|
|
@@ -373,7 +391,7 @@ Holmes-Kit embeds native AST & Code Property Graph (D-CPG) analyzers to track ca
|
|
|
373
391
|
| Language | relations | ast | cfg | ddg | cdg | taint | Corpus evidence |
|
|
374
392
|
| :--- | :---: | :---: | :---: | :---: | :---: | :---: | :--- |
|
|
375
393
|
| **TypeScript / JavaScript** | ● | ● | ● | ● | ● | ● | 10,929 functions (this repository), zero invariant violations |
|
|
376
|
-
| **Python** | ● | ● | ● | ● | ● | ● | 1,209 functions (
|
|
394
|
+
| **Python** | ● | ● | ● | ● | ● | ● | 1,209 functions (a private consumer workspace), zero invariant violations |
|
|
377
395
|
| **C#** | ● | ● | ● | ● | ● | ● | 9,184 functions (Newtonsoft.Json + RestSharp), zero invariant violations — 4.4% of files refuse at L1 (preprocessor across syntax) |
|
|
378
396
|
| **Java** | ● | ● | ● | ● | ● | ● | 8,376 functions (gson + junit4), zero invariant violations |
|
|
379
397
|
| **Go** | ● | ● | ● | ● | ● | ● | 2,637 functions (gin + cobra), zero invariant violations |
|
|
@@ -390,11 +408,11 @@ Full per-cell bases (and every stated limit) live in [docs/language-support.md](
|
|
|
390
408
|
| **macOS** | Apple Silicon (arm64) / Intel (x64) | ✅ Tier 1 | macOS 12+ (Full hook enforcement) |
|
|
391
409
|
| **Linux** | x86_64 / arm64 | ✅ Tier 1 | Ubuntu, Debian, Fedora, Arch, RHEL. **Field-validated 2026-09-14** (Ubuntu 24.04 aarch64, OrbStack): tarball install, `init --agent all`, doctor, pytest RED→GREEN, Git integration, renumber, derived-state recovery and the approval round-trip, all from the external matrix probe |
|
|
392
410
|
| **Windows (WSL2)** | x86_64 | ✅ Tier 1 | WSL2 Ubuntu/Debian recommended |
|
|
393
|
-
| **Windows Native** | x86_64 | ✅ Tier 1 | Windows 10/11 (Node.js 20+; prebuilt natives, no build tools needed in the common case). **Field-validated 2026-09-14/15** (Windows 11, Node 24, npm 12, pytest 9): tarball install, `init --agent all`, doctor, pytest RED→GREEN, adoption, Git integration, renumber, derived-state recovery and the approval round-trip — the external matrix passes from the long-name path; 0.20.1 fixes the defects it found (8.3 short paths, the merge tool's global config, transient `EPERM`, npx cache corruption). Under **npm 12** declare `allowScripts` for `better-sqlite3` and `sharp` in the consuming project (doctor prints the exact entry). |
|
|
411
|
+
| **Windows Native** | x86_64 | ✅ Tier 1 | Windows 10/11 (Node.js 20+; prebuilt natives, no build tools needed in the common case). **Field-validated 2026-09-14/15** (Windows 11, Node 24, npm 12, pytest 9): tarball install, `init --agent all`, doctor, pytest RED→GREEN, adoption, Git integration, renumber, derived-state recovery and the approval round-trip — the external matrix passes from the long-name path; 0.20.1 fixes the defects it found (8.3 short paths, the merge tool's global config, transient `EPERM`, npx cache corruption). Under **npm 12** declare `allowScripts` for `better-sqlite3` and `sharp` in the consuming project (doctor prints the exact entry). The 0.40.0 gate rules as a whole have not been measured on Windows. |
|
|
394
412
|
|
|
395
413
|
> **Runtime Requirement**: Node.js `>= 20.0.0` (LTS recommended)
|
|
396
414
|
>
|
|
397
|
-
> **How a tier is decided**: by the verification that actually executes, not by declaration. A platform is Tier 1 only while its gate verdicts are exercised by the suite; if that stops being true it is demoted and the demotion is recorded. See ADR-015 (platform tier is decided by executed verification — internal decision record).
|
|
415
|
+
> **How a tier is decided**: by the verification that actually executes, not by declaration. A platform is Tier 1 only while its gate verdicts are exercised by the suite; if that stops being true it is demoted and the demotion is recorded. The Windows row's field validation predates 0.40.0, and no Windows CI runs the suite for this release. See ADR-015 (platform tier is decided by executed verification — internal decision record).
|
|
398
416
|
|
|
399
417
|
---
|
|
400
418
|
|
package/dist/.build-id
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
bf78b204-mw2004s8
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* The admission policy (A-SPEC-792.37 §2, draft 13): one changed protected path, one axis → its contributions. The
|
|
3
|
+
* state-pair table's first matching row decides at the table level; key rules, self-containment findings and the
|
|
4
|
+
* configuration add their own levels; the stricter wins when the event assembles them. `extraSignatureKinds` raises an
|
|
5
|
+
* admitted path to `needs-signature` and lowers nothing. No signature is recognised in 0.40.0.
|
|
6
|
+
*/
|
|
7
|
+
import { TreeEntry, Axis } from './ports';
|
|
8
|
+
import { Contribution } from './verdict';
|
|
9
|
+
import { BoundedObjectReader } from './bounded-reader';
|
|
10
|
+
import { AdmissionConfig } from './config-loader';
|
|
11
|
+
import { Kind } from './path-rules';
|
|
12
|
+
export interface Change {
|
|
13
|
+
path: string;
|
|
14
|
+
kind: Kind;
|
|
15
|
+
base?: TreeEntry;
|
|
16
|
+
head?: TreeEntry;
|
|
17
|
+
}
|
|
18
|
+
/** What the policy reads about the event's head and configuration. */
|
|
19
|
+
export interface PolicyContext {
|
|
20
|
+
reader: BoundedObjectReader;
|
|
21
|
+
axis: Axis;
|
|
22
|
+
/** The configuration at this pair's `configAt`: loaded, absent (no file), refused (invalid), or none (a creation). */
|
|
23
|
+
config: {
|
|
24
|
+
config: AdmissionConfig;
|
|
25
|
+
} | {
|
|
26
|
+
absent: string;
|
|
27
|
+
} | {
|
|
28
|
+
refused: string;
|
|
29
|
+
} | {
|
|
30
|
+
none: true;
|
|
31
|
+
};
|
|
32
|
+
headIndex: Map<string, string[]>;
|
|
33
|
+
readHead: (p: string) => Buffer;
|
|
34
|
+
collisions: Set<string>;
|
|
35
|
+
}
|
|
36
|
+
/** Every contribution of one change on one axis. */
|
|
37
|
+
export declare function judgeChange(c: Change, ctx: PolicyContext): Contribution[];
|
|
@@ -0,0 +1,147 @@
|
|
|
1
|
+
"use strict";
|
|
2
|
+
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
|
+
exports.judgeChange = judgeChange;
|
|
4
|
+
const config_loader_1 = require("./config-loader");
|
|
5
|
+
const path_rules_1 = require("./path-rules");
|
|
6
|
+
const change_classifier_1 = require("./change-classifier");
|
|
7
|
+
const self_containment_1 = require("./self-containment");
|
|
8
|
+
const spec_parser_1 = require("../../spec/spec-parser");
|
|
9
|
+
const QUEUE_REMEDY = 'other ledgers and the queue: no re-ordering tool in 0.40.0 — the alarm stays for that push';
|
|
10
|
+
const LEDGER_REMEDY = 'provenance ledgers: `holmes-kit ledger rechain`';
|
|
11
|
+
const isNormalBlob = (e) => !e || (e.type === 'blob' && e.mode === '100644');
|
|
12
|
+
const DRAFTISH = new Set(['draft', 'review']);
|
|
13
|
+
function stateOf(reader, e, kind, path) {
|
|
14
|
+
if (!e)
|
|
15
|
+
return { state: 'absent' };
|
|
16
|
+
const bytes = reader.doc(e.oid);
|
|
17
|
+
if (bytes === null)
|
|
18
|
+
return 'size';
|
|
19
|
+
if (kind === 'spec')
|
|
20
|
+
return (0, change_classifier_1.docState)(bytes);
|
|
21
|
+
if ((0, path_rules_1.isDetectorWorkflow)(path)) {
|
|
22
|
+
const r = (0, change_classifier_1.preChecks)(bytes, 'workflow');
|
|
23
|
+
return r ? { state: 'unparseable', reason: r } : { state: 'draft' };
|
|
24
|
+
}
|
|
25
|
+
const r = (0, change_classifier_1.preChecks)(bytes, 'frontmatter');
|
|
26
|
+
if (r)
|
|
27
|
+
return { state: 'unparseable', reason: r };
|
|
28
|
+
try {
|
|
29
|
+
(0, spec_parser_1.parseSpec)(bytes.toString('utf8'));
|
|
30
|
+
}
|
|
31
|
+
catch (err) {
|
|
32
|
+
return { state: 'unparseable', reason: `does not parse (${String(err.message).split('\n')[0]})` };
|
|
33
|
+
}
|
|
34
|
+
return { state: 'draft' }; // a decision has no state rows; it is row 16
|
|
35
|
+
}
|
|
36
|
+
/** The table row that decides, as one contribution (first match wins). */
|
|
37
|
+
function tableRow(c, ctx) {
|
|
38
|
+
const t = (row, verdict, reason) => ({ level: 'table', axis: ctx.axis, row, verdict, reason });
|
|
39
|
+
const { base: b, head: h, kind, path } = c;
|
|
40
|
+
// row 1: a mode other than 100644, a symlink or a submodule; an ancestor that is not a tree
|
|
41
|
+
if (kind === 'ancestor' || !isNormalBlob(b) || !isNormalBlob(h))
|
|
42
|
+
return t(1, 'refused', `${path}: a mode other than 100644, a symlink, a submodule, or an ancestor that is not a tree`);
|
|
43
|
+
// row 2: any → unparseable (documents with a state: specs, decisions, the detector workflows)
|
|
44
|
+
let before, after;
|
|
45
|
+
if (kind === 'spec' || kind === 'decision' || (0, path_rules_1.isDetectorWorkflow)(path)) {
|
|
46
|
+
before = stateOf(ctx.reader, b, kind, path);
|
|
47
|
+
after = stateOf(ctx.reader, h, kind, path);
|
|
48
|
+
if (before === 'size' || after === 'size')
|
|
49
|
+
return t(2, 'incomplete', 'size: a parsed document over 1 MiB');
|
|
50
|
+
if (h && after.state === 'unparseable')
|
|
51
|
+
return t(2, 'refused', `unparseable: ${after.reason ?? ''}`);
|
|
52
|
+
}
|
|
53
|
+
if (kind === 'definition')
|
|
54
|
+
return t(3, 'needs-signature', 'a change to the detection definition');
|
|
55
|
+
if (kind === 'ledger' || kind === 'queue') {
|
|
56
|
+
if (kind === 'ledger' && !b) {
|
|
57
|
+
const replica = (0, path_rules_1.replicaOf)(path);
|
|
58
|
+
if (replica === null)
|
|
59
|
+
return t(4, 'refused', 'a new legacy ledger');
|
|
60
|
+
const allowed = 'config' in ctx.config && ctx.config.config.replicaAllow.includes(replica);
|
|
61
|
+
if (!allowed)
|
|
62
|
+
return t(4, 'needs-signature', `a new replica ledger (${replica}) not on replicaAllow`);
|
|
63
|
+
}
|
|
64
|
+
if (!h)
|
|
65
|
+
return t(6, 'refused', 'a ledger or the queue deleted');
|
|
66
|
+
const a = ctx.reader.append(b ? b.oid : null, h.oid);
|
|
67
|
+
if (a.ok)
|
|
68
|
+
return t(5, 'admit', 'append only');
|
|
69
|
+
const remedy = kind === 'queue' || !/^\.ax\/ledger\/provenance[.]/i.test(path) ? QUEUE_REMEDY : LEDGER_REMEDY;
|
|
70
|
+
return t(6, 'refused', `${a.union ? 'union merge inserted lines mid-file' : 'not append-only'} — ${remedy}`);
|
|
71
|
+
}
|
|
72
|
+
if (kind === 'audit')
|
|
73
|
+
return t(7, 'admit', 'audit');
|
|
74
|
+
if (kind === 'spec' && before && after && before !== 'size' && after !== 'size') {
|
|
75
|
+
const S = before.state, T = after.state;
|
|
76
|
+
const spec = after.spec;
|
|
77
|
+
const fm = (spec?.frontmatter ?? {});
|
|
78
|
+
const sealCheck = () => {
|
|
79
|
+
if (!spec)
|
|
80
|
+
return 'no document';
|
|
81
|
+
if (fm.approved_digest !== (0, change_classifier_1.specDigest)(spec))
|
|
82
|
+
return 'approved_digest is not the canonical digest';
|
|
83
|
+
return (0, change_classifier_1.parentBreach)(spec, ctx.headIndex, ctx.readHead, (id) => (0, change_classifier_1.onCycle)(id, ctx.headIndex, ctx.readHead));
|
|
84
|
+
};
|
|
85
|
+
if (S === 'unparseable' && T !== 'absent') {
|
|
86
|
+
const breach = T === 'approved' ? sealCheck() : null;
|
|
87
|
+
return breach ? t(8, 'refused', breach) : t(8, 'needs-signature', 'unparseable → parseable');
|
|
88
|
+
}
|
|
89
|
+
if ((S === 'absent' || DRAFTISH.has(S)) && DRAFTISH.has(T) && fm.approved_digest === undefined && fm.parent_digests === undefined)
|
|
90
|
+
return t(9, 'admit', 'draft, no seal');
|
|
91
|
+
if (DRAFTISH.has(S) && T === 'absent')
|
|
92
|
+
return t(10, 'admit', 'a draft deleted');
|
|
93
|
+
if ((S === 'absent' || DRAFTISH.has(S)) && T === 'approved') {
|
|
94
|
+
const breach = sealCheck();
|
|
95
|
+
return breach ? t(11, 'refused', breach) : t(11, 'needs-signature', 'sealed');
|
|
96
|
+
}
|
|
97
|
+
if (S === 'approved' && T === 'approved') {
|
|
98
|
+
const breach = spec ? (0, change_classifier_1.parentBreach)(spec, ctx.headIndex, ctx.readHead, (id) => (0, change_classifier_1.onCycle)(id, ctx.headIndex, ctx.readHead)) : null;
|
|
99
|
+
return breach ? t(12, 'refused', breach) : t(12, 'needs-signature', 'an approved spec changed');
|
|
100
|
+
}
|
|
101
|
+
if (S === 'approved' && DRAFTISH.has(T))
|
|
102
|
+
return t(13, 'needs-signature', 'an un-seal');
|
|
103
|
+
if ((S === 'approved' && T === 'outdated') || ((S === 'approved' || S === 'outdated') && T === 'absent'))
|
|
104
|
+
return t(14, 'needs-signature', 'retired or deleted');
|
|
105
|
+
if (S === 'outdated')
|
|
106
|
+
return t(15, 'needs-signature', 'outdated → another state');
|
|
107
|
+
}
|
|
108
|
+
return t(16, 'needs-signature', 'a protected path');
|
|
109
|
+
}
|
|
110
|
+
/** Every contribution of one change on one axis. */
|
|
111
|
+
function judgeChange(c, ctx) {
|
|
112
|
+
const out = [];
|
|
113
|
+
const cfg = ctx.config;
|
|
114
|
+
const isConfigAddition = (0, path_rules_1.fold)(c.path) === path_rules_1.CONFIG_PATH && !c.base && !!c.head;
|
|
115
|
+
if ('none' in cfg)
|
|
116
|
+
out.push({ level: 'path', axis: ctx.axis, verdict: 'refused', reason: 'branch creation: judged with no configuration' });
|
|
117
|
+
else if ('absent' in cfg && !isConfigAddition)
|
|
118
|
+
out.push({ level: 'path', axis: ctx.axis, verdict: 'refused', reason: cfg.absent });
|
|
119
|
+
else if ('refused' in cfg)
|
|
120
|
+
out.push({ level: 'path', axis: ctx.axis, verdict: 'refused', reason: cfg.refused });
|
|
121
|
+
if (ctx.collisions.has(c.path))
|
|
122
|
+
out.push({ level: 'key', axis: ctx.axis, verdict: 'refused', reason: 'a case or NFC collision' });
|
|
123
|
+
if (c.kind === 'spec' && c.head) {
|
|
124
|
+
const bytes = ctx.reader.doc(c.head.oid);
|
|
125
|
+
const st = bytes ? (0, change_classifier_1.docState)(bytes) : null;
|
|
126
|
+
if (st?.spec) {
|
|
127
|
+
const b = (0, change_classifier_1.keyRuleBreach)(c.path, st.spec, ctx.headIndex);
|
|
128
|
+
if (b)
|
|
129
|
+
out.push({ level: 'key', axis: ctx.axis, verdict: 'refused', reason: b });
|
|
130
|
+
}
|
|
131
|
+
}
|
|
132
|
+
if ((0, path_rules_1.isDetectorWorkflow)(c.path) && c.head) {
|
|
133
|
+
const bytes = ctx.reader.doc(c.head.oid);
|
|
134
|
+
// a document the pre-checks refuse is row 2's, not a workflow whose keys are judged (the closed key set would name
|
|
135
|
+
// every key of a YAML that is no workflow at all)
|
|
136
|
+
for (const f of bytes && (0, change_classifier_1.preChecks)(bytes, 'workflow') === null ? (0, self_containment_1.selfContainmentFindings)(bytes) : [])
|
|
137
|
+
out.push({ level: 'finding', axis: ctx.axis, verdict: 'refused', reason: f });
|
|
138
|
+
}
|
|
139
|
+
const row = tableRow(c, ctx);
|
|
140
|
+
out.push(row);
|
|
141
|
+
if (c.kind === 'definition' && row.row !== 3)
|
|
142
|
+
out.push({ level: 'table', axis: ctx.axis, row: 3, verdict: 'needs-signature', reason: 'a change to the detection definition' });
|
|
143
|
+
if (row.verdict === 'admit' && 'config' in cfg && cfg.config.extraSignatureKinds.some((k) => (0, config_loader_1.matchesKind)(k, c.path))) {
|
|
144
|
+
out.push({ level: 'table', axis: ctx.axis, verdict: 'needs-signature', reason: 'extraSignatureKinds' });
|
|
145
|
+
}
|
|
146
|
+
return out;
|
|
147
|
+
}
|