@1aboveio/skills 0.19.2 → 0.20.1

package/skills/engineering/resolve-issues/references/terminal-evidence-journal.md

@@ -1,40 +0,0 @@
-# Terminal provider evidence journal
-
-Use the journal when a provider has already issued terminal delivery facts but an ordinary `run-state.mjs` transition is blocked by resolver dependency coherence. The journal preserves the observation until the installation can be repaired. It does not repair the installation and does not authorize delivery.
-
-Package-version identity, npm coherence, public repair commands, and the trusted repair contract belong to #996. This recovery path neither redefines nor bypasses them. Resolve-release's terminal evidence bundles remain separate; this journal applies only to resolve-issues delivery recovery.
-
-## Append
-
-Create an observation JSON associated with the current run's unit and component. For a member unit carrying `deliveryRef`, the journal binds the provider subject to that referenced canonical `components[].delivery` record: its component ID, PR, and `authorizedHeadSha`. The member `unitId` remains in the association; its distinct unit PR and `pushedSha` are not the combined delivery identity. Legacy unit-owned delivery continues to bind the unit PR and head. The observation must include:
-
-- provider id and observation time;
-- merged PR state, exact PR head, merge commit, and merge time;
-- non-ambiguous check conclusions on that exact head;
-- the freshly observed target ref/head and merge ancestry;
-- the provider-issued queue execution artifact when the authorized required-check plan has queue-head checks.
-
-Then append it without changing the run manifest:
-
-```sh
-node <resolve-issues>/scripts/terminal-evidence-journal.mjs append \
-  --manifest <run-manifest.json> \
-  --input <terminal-observation.json>
-```
-
-The default journal is `${RESOLVER_TERMINAL_EVIDENCE_DIR:-${XDG_STATE_HOME:-~/.local/state}/resolver-terminal-evidence}`. Each entry is written once as `<sha256>.json`, created exclusively, made read-only, and validated against its canonical content address when read. An evidence-identical retry is a no-op. A different byte sequence at the same address is reported as tampering/collision.
-
-Appending evidence never writes the run manifest, changes disposition, records authorization, or marks a unit complete. It remains valid to append while Workflow coherence is red because this standalone module imports no shared skill runtime.
-
-## Reconcile
-
-After the actual resolver dependency closure is coherent again, run:
-
-```sh
-node <resolve-issues>/scripts/run-state.mjs reconcile-terminal-evidence \
-  <run-slug> <absolute-journal-entry-path>
-```
-
-This is a coherence-gated manifest transition. It validates the journal schema and digest, resolves the current unit/component association, rebinds PR and exact-head identity through canonical component delivery whenever the unit carries `deliveryRef`, re-reads that PR and its checks from the provider, reacquires queue execution evidence when the current plan requires it, fetches `origin/<targetBranch>`, and proves merge-commit ancestry. Only then does it apply the existing delivery outcome transition and append `terminalEvidenceImports[]` in one atomic manifest write.
-
-Stale heads, moved identities, duplicate checks/imports, terminal-state contradictions, unavailable or changed queue evidence, failed/skipped checks, and absent fresh ancestry are rejected. The journal remains evidence after rejection; it never becomes authorization by its own existence.