triad-plus 1.2.0 → 1.4.0

package/schemas/runtime-capabilities.schema.json

@@ -6,7 +6,7 @@
   "required": ["schema_version", "detected_at", "host", "host_runtime", "verifier_runtime", "lifecycle_async", "verification"],
   "properties": {
     "schema_version": { "const": 1 },
-    "host": { "enum": ["codex", "opencode", "claude-code", "antigravity"] },
+    "host": { "enum": ["codex", "opencode", "claude-code", "antigravity", "hermes", "copilot"] },
     "host_runtime": { "type": "object", "required": ["binary", "version", "available"] },
     "verifier_runtime": { "type": "object", "required": ["binary", "version", "available"] },
     "lifecycle_async": { "type": "object", "required": ["kind", "minimum_version", "available", "configured", "reason"] },

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

@@ -26,7 +26,9 @@ conditions, runnable quality gates, practical-test need, and integration need.
 6. Create `.loop/runtime/assignments/` and record the active adapter metadata in
    `.loop/runtime/capabilities.json` by running
    `.triad-runtime/triad-runtime-capabilities.mjs --adapter
-   .triad-runtime/adapter.json`.
+   .triad-runtime/adapter.json --requested-mode <project.control_plane.dispatch_mode>`.
+   Use `auto` when the project does not declare a mode. For Codex, `auto` is
+   explicit dispatch; `async_hook` is an experimental opt-in only.
 7. Show the full card division before delivery work. Continue unless the owner
    changes it or an escalation condition exists.
 

package/skills/triad-loop-bootstrap/assets/loop-template/feature-card.template.md

@@ -24,6 +24,12 @@
 - Allowed dependencies: `<names or none>`
 - Test fixtures/examples: `<paths>`
 
+## Repository skill binding
+
+- Repository policy/router: `<path to the repository router SKILL.md or not applicable>`
+- Required skills: `<router, routed skills, and completion skill>`
+- Assignment evidence: `<relative SKILL.md paths and SHA-256 values>`
+
 ## Integration, practical test, and risk
 
 - Local-worktree setup: `<not applicable or command>`

package/skills/triad-loop-bootstrap/assets/loop-template/handoff-report.template.md

@@ -50,6 +50,14 @@ State: `not_applicable | ready_to_start | active | closed | start_failed`
 - Start: `<only on owner request>`
 - Stop: `<only on owner completion>`
 - Closure evidence: `<timestamp, process result, port-release check>`
+- Remote access contract: `<none | declared remote URL and access mode>`.
+  `localhost` is local-only and must not be presented as a remote endpoint.
+
+## Delivery closure record
+
+- Run record updated: `<path and final decision>`
+- Final branch/commit map recorded: `<yes/no; reference>`
+- Final delivery message issued: `<yes/no; timestamp or reference>`
 
 ## Practical test and follow-up
 

package/skills/triad-loop-bootstrap/assets/loop-template/run-state.yaml

@@ -2,6 +2,14 @@ version: 2
 updated_at: null
 project_decision: not_started
 
+delivery:
+  status: not_delivered # not_delivered | delivered | delivery_blocked | delivered_without_demo
+  handoff: null
+  branches: []
+  evaluator_report: null
+  delivered_at: null
+  owner_message: null
+
 feature_plan:
   path: feature-plan.md
   status: declared

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

@@ -16,6 +16,16 @@
   "expected_prd_sha256": "REPLACE_ME_SHA256",
   "expected_card_sha256": "REPLACE_ME_SHA256",
   "expected_gates_sha256": "REPLACE_ME_SHA256",
+  "required_repository_skills": [
+    {
+      "path": ".agents/skills/router/SKILL.md",
+      "sha256": "REPLACE_ME_SHA256"
+    },
+    {
+      "path": ".agents/skills/agent-completion/SKILL.md",
+      "sha256": "REPLACE_ME_SHA256"
+    }
+  ],
   "verification_run_id": "REPLACE_ME_UUID",
   "evidence_directory": ".loop/evidence/REPLACE_ME_FEATURE_ID/attempt-001"
 }

package/skills/triad-loop-bootstrap/assets/project.yaml

@@ -37,7 +37,17 @@ project:
       enabled: false
       start_policy: only_on_owner_request
       stop_policy: only_on_owner_completion
+      # Declare a service only when the owner needs a practical demo. A remote
+      # URL is optional and must never be inferred from a localhost URL.
       services: []
+      # Example service shape:
+      # - id: component-demo
+      #   worktree: worktrees/product-repository
+      #   start_command: npm run dev -- --host 0.0.0.0
+      #   stop_command: <owner-completion procedure>
+      #   local_url: http://127.0.0.1:6006
+      #   remote_access: tailscale # none | tailscale | proxy | public
+      #   remote_url: http://host.example:6006
 
 integration:
   enabled: false

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

@@ -10,6 +10,18 @@ project manifest, repository instructions, allowed surface, prior findings, and
 gates. Verify the declared worktree and branch before editing. Do not change
 scope, policy, assignments, queue, state, or evidence records.
 
+At the beginning of every activation, read `.triad-plus/team.json` when it
+exists. Your first report to the Orchestrator must identify you as its configured
+`roles.developer.displayName` and the Triad+ Developer, then name the assigned
+card. This is an attributed role-activation record, not an approval or a state
+transition.
+
+When the assignment declares `required_repository_skills`, read every bound
+file from the declared worktree before editing. Include their relative paths and
+SHA-256 values in the report as a **repository-skill attestation**. If a bound
+skill is missing or its hash differs, stop and report the mismatch; do not
+replace it with external context or a similarly named skill.
+
 Implement the smallest complete change and focused tests. Run useful local
 checks and measure declared criteria. Report changed files, tests, exact command
 results, metrics, worktree/branch, risks, and blockers to the Orchestrator.

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

@@ -11,6 +11,26 @@ artifact/observation instructions, and current verifier evidence. Do not request
 Developer reasoning, conversation history, prior Reviewer discussion, or attempt
 history unless the owner explicitly requires it.
 
+The approved evaluation packet is the complete evaluation boundary. Do not
+inspect queue state, delivery state, coordinator state, run-state files,
+handoff files, or other control records unless their contents are explicitly
+included in the approved evaluation packet. Evaluate only the supplied goal,
+quality/acceptance target, final candidate or observable artifact, and
+environment-derived verification evidence. Never use an out-of-packet control
+record to justify a verdict.
+
+At the beginning of every activation, read `.triad-plus/team.json` when it
+exists. Your first report must identify you as its configured
+`roles.evaluator.displayName` and Evaluator+, then name the completed result
+being assessed. This is an attributed post-run activation record; it does not
+reopen or modify Triad.
+
+When verifier evidence declares `repository_skills`, independently read the
+listed bound files from the final worktree and include their paths and SHA-256
+values in the evaluation report. A missing or mismatched binding makes the
+evaluation `INDETERMINATE`; it never starts repair or changes the closed Triad
+result.
+
 Return a report conforming to `schemas/evaluator-plus-result.schema.json` and
 store it separately under `artifacts/evaluator-plus/<evaluation-id>.json`:
 
@@ -20,5 +40,5 @@ store it separately under `artifacts/evaluator-plus/<evaluation-id>.json`:
 
 Include concise rationale, direct evidence references, and confidence. Do not
 edit source, change the Triad queue/state, commit, push, approve delivery, or
-request automatic repair. A `FAIL` leaves the Triad run approved and closed; it
-may inform a new owner-requested run.
+request automatic repair, and never reopen the Triad run. A `FAIL` leaves the
+Triad run approved and closed; it may inform a new owner-requested run.

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

@@ -18,18 +18,28 @@ intermediary or another Triad role to the owner. You may report delegated roles'
 outputs, but never claim their identity. Technical role IDs and authority remain
 unchanged.
 
-After loading this configuration, the first owner-facing message of every Triad+
-run must begin with a concise introduction: "I am <displayName>, the Triad+
-Orchestrator for this run." Localize it to the configured interaction language,
-then state in one sentence whether the run is new or resumed and what input was
-received. Do this before delegating, discussing artifacts, or asking questions.
+If the current Triad+ invocation has not yet introduced the Orchestrator, its
+first owner-facing message is a presentation, not a generic acknowledgement or
+bootstrap report. Before any other owner-facing content, begin with a
+first-person sentence that includes `<displayName>` and "Triad+ Orchestrator",
+localized to the configured interaction language; then state whether the run is
+new or resumed and what input was received. If the entry point already made that
+presentation for this invocation, do not repeat it.
 
 ## Run one card
 
 1. Verify the PRD hash, declared worktree/branch, repository instructions,
-   runnable gates, and capability snapshot.
+   runnable gates, and capability snapshot. The snapshot must reflect
+   `project.control_plane.dispatch_mode` as `requested_mode` (default `auto`).
+   When repository instructions define
+   a skill router, read it, select the router, routed skills, and completion
+   skill required by the card, and bind their worktree-relative paths plus
+   SHA-256 values in `required_repository_skills` on the Developer assignment.
+   Do not assign the card if this binding cannot be made.
 2. Choose one dependency-approved `ready` card, mark it `in_progress`, append an
-   attempt, and create an active assignment before delegating.
+   attempt, and create an active assignment before delegating. Before each
+   delegation, publish an owner-facing activation notice that attributes the
+   configured display name, technical role, and card/attempt to that role.
 3. Give the Developer the card, relevant PRD excerpt, allowed surface, gates,
    risks, and prior findings. Treat its command results and report as
    **agent-reported claims**, never as control-plane gate truth.
@@ -38,17 +48,37 @@ received. Do this before delegating, discussing artifacts, or asking questions.
    the verifier explicitly. Accept only current evidence whose assignment ID,
    feature, attempt, PRD/card/gate hashes, expected branch, and candidate
    fingerprint match the active candidate.
+   A Developer report is never a human-input wait condition: immediately wait
+   for the configured hook evidence or invoke the verifier, then immediately
+   dispatch the Reviewer on a verifier pass. Do not ask the owner to continue
+   between Developer completion, verification, and review.
 5. A passing verifier result is **environment-derived evidence**. Move only then
    to `in_review`. Missing, stale, failed, timed-out, invalid-context, or
    invalidated evidence never advances the card.
 6. Give the Reviewer the card, diff, developer report, verifier evidence, prior
    attempts, and risks. Record its recommendation:
-   - `approved`: verify scope/evidence, commit the card locally, then select the
-     next ready card;
+   - `approved`: verify scope/evidence, commit the card locally, promote every
+     dependency-satisfied draft card to `ready`, then immediately select and
+     assign the next ready card;
    - `rework`: preserve findings and return the card to `in_progress` for a new
      attempt and new verification;
    - `blocked`: record the exact external condition or owner decision required.
 7. Stop automatic retry at the declared limit and escalate the decision needed.
+   Do not ask the owner to continue, pause between cards, or finish the run
+   while a dependency-satisfied card remains `ready`; stop only for a declared
+   escalation, a blocked card, or when every required card is terminal.
+
+## Unattended continuation rule
+
+The normal chain is unattended: Developer completion → verification → Reviewer
+→ rework or approval → next dependency-satisfied card. Do not stop for an
+acknowledgement, progress update, or agent-reported claim. The only valid human
+wait conditions are an escalation named by the policy, a `blocked` verdict, an
+unrecoverable runtime error, or an explicit owner pause.
+
+An owner-facing activation or progress update is informational output, never an
+implicit pause. After sending it, continue the recorded next action without
+waiting for a reply unless one of the valid human wait conditions applies.
 
 ## Authority and delivery
 
@@ -61,8 +91,30 @@ review, and restoration of normal roles.
 After all required cards and project gates pass, commit each approved card if
 needed and normally push declared branches. Never force-push, create/update a
 pull request, publish, release, or start/stop a demo without owner direction.
-Write a final handoff with cards, commits, pushes, verifier evidence, reviewer
-decisions, risks, exceptions, and practical-test instructions.
+
+## Delivery closure gate
+
+`approved` is not an owner delivery. Do not declare a project delivered, closed,
+or ready for owner testing until this gate has completed:
+
+1. Record the final commit and normal-push evidence for every declared branch.
+2. If configured, complete the isolated Evaluator+ dispatch and record its
+   report. Its verdict still cannot reopen Triad.
+3. Write the final handoff from the handoff template with cards, commits,
+   pushes, verifier evidence, reviewer decisions, risks, exceptions, and
+   practical-test instructions.
+4. Update the control-workspace run record with the delivery decision, handoff
+   reference, final branch/commit map, and optional Evaluator+ reference.
+5. Give the owner one final delivery message that links the handoff, names the
+   practical test, and states the demo status.
+
+For every configured demo service, copy its declared command, local URL, remote
+URL, and remote-access mode into the handoff. Never present `localhost` as a
+remote endpoint. If the service is loopback-only or has no configured remote
+URL, explicitly say that remote testing is unavailable. On an owner request to
+start a demo, validate the declared local URL and, when a remote URL is
+configured, validate that endpoint before reporting it. Keep the service running
+until the owner explicitly ends the demo.
 
 Evaluator+ is outside the Triad production run. After final Triad approval,
 read `roles.evaluator.enabled` from `.triad-plus/team.json`: when it is `true`,
@@ -72,3 +124,5 @@ false or omitted, finish without evaluation. Record the report separately;
 `PASS`, `FAIL`, and `INDETERMINATE` cannot reopen, rework, assign Developer work,
 or change the already closed Triad run. A per-run `--evaluator` or
 `--no-evaluator` request may override the configuration when the host exposes it.
+Before dispatching it, publish the corresponding attributed Evaluator+
+activation notice.

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

@@ -11,6 +11,19 @@ instructions, actual diff/worktree, and verifier evidence. You may know prior
 attempts and correction history; independence means assess the artifact and
 evidence yourself, not blindness.
 
+At the beginning of every activation, read `.triad-plus/team.json` when it
+exists. Your first report to the Orchestrator must identify you as its configured
+`roles.reviewer.displayName` and the Triad+ Reviewer, then name the feature and
+attempt under review. This is an attributed role-activation record, not an
+approval or a state transition.
+
+When the assignment declares `required_repository_skills`, independently read
+the same bound files from the declared worktree and compare their paths and
+SHA-256 values with the Developer attestation and verifier evidence. A missing,
+mismatched, or unreported required repository skill is a `blocked` result until
+the Orchestrator creates a valid assignment; external context never substitutes
+for the repository skill policy.
+
 Confirm scope, dependencies, candidate fingerprint, assignment ID, feature,
 attempt, expected branch, and PRD/card/gate hashes. Reject stale, missing,
 invalidated, or failed verifier evidence. Independently rerun enough required