triad-plus 1.12.1 → 1.12.2

package/CHANGELOG.md

@@ -1,6 +1,14 @@
 # Changelog
 
-## Unreleased
+## 1.12.2 — 2026-09-26
+
+- Fix compatibility for historical assignments with `scope_contract: null` and
+  omit unconfigured scope contracts from new bootstrap templates while keeping
+  valid scope enforcement fail-closed.
+- Clarify the exact explicit verifier identity/run-id invocation contract and
+  the omission rule for unconfigured repository-skill bindings.
+- Clarify the bounded Card and delivery handoff report-context contract without
+  changing Reviewer independence or deterministic verification semantics.
 
 ## 1.12.1 — 2026-09-26
 

package/docs/human-readable-reports.md

@@ -39,6 +39,25 @@ committed fingerprint separately. A blocked or not-delivered terminal Card must
 include a truthful reason and never claims delivery. Writes are atomic and
 re-running the command with the same context is idempotent.
 
+### Card context checklist
+
+The derived card context should carry only canonical control-plane fields:
+
+- `card.id` (and its title, goal/outcome, repository, and card path);
+- terminal `status`, `attempts`, and verification runs;
+- at least one passing verification run with its evidence path and candidate
+  fingerprint;
+- independent `review.decision: approved` and its evidence/fingerprint;
+- `final.branch`, `final.commit`, `final.repository`, `final.base_commit`, and
+  `final.candidate_fingerprint`;
+- assignment/packet/verification provenance and bounded evidence references.
+
+For an approved card, `final.candidate_fingerprint` is the pre-commit
+fingerprint recorded by the passing verifier. The renderer computes and records
+`final.committed_candidate_fingerprint` from the committed delta; do not replace
+the verified fingerprint with a newly calculated value in the input context.
+The source card and canonical evidence remain read-only.
+
 ## Materialize the final handoff
 
 ```bash
@@ -53,3 +72,22 @@ The handoff opens with the executive summary and Card results, then preserves
 links to the technical evidence, branch/commit map, quality-contract closure,
 Evaluator+ result, delivery gates, demo details, risks, and practical test.
 It is a view for people, not an alternative delivery state machine.
+
+### Handoff context checklist
+
+The derived handoff context must include a non-empty `cards` list and a
+`decision` plus `executive_summary`. Each card entry carries `id`, `title`,
+`status`, `summary`, `report_path`, and, when available, `commit`,
+`candidate_fingerprint`, `verification`, `review`, `evaluator_report`, and
+`evidence_refs`. The remaining canonical handoff fields are:
+
+`code_areas`, `residual`, `verification`, `review`, `branch_commits`,
+`practical_test`, `evaluator`, `delivery`, `quality_contract`,
+`delivery_criteria`, `demo`, `evidence_refs`, `exceptions`, `prd_baseline`,
+`approved_cards`, `push_evidence`, `gate_metrics`,
+`local_worktree_integration`, `delivery_closure_record`, `final_message`,
+`risks`, and `generated_from`.
+
+Populate fields from canonical run, card, verifier, Reviewer, Evaluator+, and
+delivery records. Do not pass Developer reasoning, queue-control narrative, or
+unbounded source documents merely to satisfy the renderer.

package/docs/verification.md

@@ -17,6 +17,36 @@ An agent-reported claim is not the same as verification evidence. A Developer ca
 report the commands it ran; `triad-verify` independently observes declared
 required `control-plane` gates and writes atomic evidence.
 
+## Explicit verifier dispatch contract
+
+When the configured route is `explicit_dispatch`, invoke the installed verifier
+with the active assignment's exact Developer identity. The trigger is supplied
+as JSON on stdin; it is not inferred from the shell process or from the card:
+
+```bash
+agent_id="<assignment.agent_id>"
+run_id="<assignment.verification_run_id>"
+printf '{"event":"manual_explicit_dispatch","agent_id":"%s","agent_type":"triad_developer","run_id":"%s"}' "$agent_id" "$run_id" |
+  node .triad-runtime/triad-verify.mjs \
+    --project /absolute/path/to/control-workspace \
+    --assignment /absolute/path/to/control-workspace/.loop/runtime/assignments/<assignment-file>.json \
+    --run-id "$run_id"
+```
+
+`agent_id` must match the active assignment exactly and `agent_type` must be
+`triad_developer`. The `run_id` on stdin and `--run-id` must match the active
+assignment when one is bound. A missing or mismatched trigger is
+`invalid_context`; no gate runs and no retry/remediation budget is consumed.
+
+When the repository has no router or required repository skills, omit the
+`required_repository_skills` property from the assignment. Do not represent an
+unconfigured binding as a present empty array: a present array is a declared
+binding and must contain at least one validated skill. This documents existing
+runtime behavior; it does not add a new verifier mode or transition.
+
+`triad-verify.mjs` does not expose a help screen. Use the assignment, project
+configuration, and this explicit recipe rather than invoking it with `--help`.
+
 ## Immutable Quality Contract
 
 Projects may opt into `project.quality_contract` with a project-relative JSON

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "triad-plus",
-  "version": "1.12.1",
+  "version": "1.12.2",
   "description": "A lightweight, evidence-backed engineering loop for coding agents.",
   "license": "Apache-2.0",
   "type": "module",

package/runtime/triad-verify.mjs

@@ -115,7 +115,10 @@ function withinRoot(root, candidate, label) {
 
 async function scopePreflight(projectRoot, worktree, assignment) {
   const specification = assignment.scope_contract;
-  if (specification === undefined) {
+  // v1.12.1's assignment template materialized an unconfigured scope as
+  // `null`. Treat that historical sentinel exactly like an omitted contract,
+  // while continuing to fail closed for every malformed non-null value.
+  if (specification === undefined || specification === null) {
     const candidate = await collectCandidateChanges(worktree);
     return {
       configured: false,

package/skills/triad-loop-bootstrap/assets/loop-template/runtime/assignments/assignment.template.json

@@ -20,7 +20,6 @@
   "quality_baseline_path": null,
   "expected_quality_baseline_fingerprint": null,
   "required_gate_ids": [],
-  "scope_contract": null,
   "required_repository_skills": [
     {
       "path": ".agents/skills/router/SKILL.md",

package/skills/triad-loop-orchestrator/SKILL.md

@@ -153,7 +153,24 @@ fail-closed escalation; do not dispatch a Developer or consume retry budget.
    for a missing detail or contradiction, not systematic startup context.
 4. After completion, move to `verifying`. Follow the recorded dispatch route:
    wait for a valid hook-produced file when one is configured, otherwise invoke
-   the verifier explicitly. Accept only current evidence whose assignment ID,
+   the verifier with the exact active Developer identity. For explicit dispatch,
+   pipe the trigger JSON and bind the same run ID on stdin and argv:
+
+   ```bash
+   agent_id="<assignment.agent_id>"
+   run_id="<assignment.verification_run_id>"
+   printf '{"event":"manual_explicit_dispatch","agent_id":"%s","agent_type":"triad_developer","run_id":"%s"}' "$agent_id" "$run_id" |
+     node .triad-runtime/triad-verify.mjs \
+       --project /absolute/path/to/control-workspace \
+       --assignment /absolute/path/to/control-workspace/.loop/runtime/assignments/<assignment-file>.json \
+       --run-id "$run_id"
+   ```
+
+   Do not substitute a generic `manual` trigger or a different agent identity.
+   When no repository skills are configured, omit
+   `required_repository_skills` from the assignment; a present empty array is
+   a declared binding and fails closed. These are existing runtime semantics,
+   not a new verification behavior. Accept only current evidence whose assignment ID,
    feature, attempt, PRD/card/gate hashes, expected branch, and candidate
    fingerprint match the active candidate. When an opt-in scope contract is
    configured, `triad-verify` first compares the complete candidate delta from