gentle-pi 2.2.0 → 2.4.0

package/scripts/verify-package-files.mjs

@@ -30,6 +30,7 @@ const requiredPaths = [
   "assets/agents/sdd-init.md",
   "assets/agents/sdd-onboard.md",
   "assets/agents/sdd-proposal.md",
+  "assets/agents/sdd-research.md",
   "assets/agents/sdd-spec.md",
   "assets/agents/sdd-status.md",
   "assets/agents/sdd-sync.md",
@@ -52,7 +53,6 @@ const requiredPaths = [
   "extensions/sdd-init.ts",
   "extensions/skill-registry.ts",
   "lib/gentle-ai-binary.ts",
-  "lib/git-commit-transaction.ts",
   "lib/native-review-cli.ts",
   "lib/provider-contract-bundle.ts",
   "lib/review-host-relay.ts",
@@ -60,17 +60,13 @@ const requiredPaths = [
   "lib/review-relay-contract.ts",
   "lib/sdd-preflight.ts",
 	"runtime/gentle-ai-binary.mjs",
-	"runtime/git-commit-transaction.mjs",
 	"runtime/native-review-cli.mjs",
 	"runtime/review-integration-v2.mjs",
 	"runtime/review-relay-contract.mjs",
-	"scripts/build-git-commit-transaction-runner.mjs",
   "scripts/check-provider-contract.mjs",
   "scripts/gentle-ai-installer.mjs",
   "scripts/install-gentle-ai.mjs",
   "scripts/mirror-provider-contract.mjs",
-  "scripts/run-git-commit-transaction.mjs",
-	"scripts/test-packed-runner.mjs",
   "tests/fixtures/native-review-cli/v2.1.3/start.json",
   "tests/fixtures/provider-contract-bundle/v1.1.0/README.md",
   "tests/fixtures/provider-contract-bundle/v1.1.0/manifest.json",
@@ -84,16 +80,17 @@ const requiredPaths = [
   // exact bytes are pinned by the lock-driven scripts/check-provider-contract.mjs
   // drift check, which runs in the same pnpm test flow.
   "contracts/review-provider-contract-mirror/provider-contract.lock.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/README.md",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/manifest.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/schemas/lens.schema.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/schemas/refuter.schema.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/schemas/targeted-validator.schema.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/vectors/lens.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/vectors/refuter.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/bundle/vectors/targeted-validator.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/generated/provider-capabilities.baseline.json",
-  "contracts/review-provider-contract-mirror/v1.1.0/generated/provider-roles.baseline.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/README.md",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/manifest.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/orchestration/pi.md",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/schemas/lens.schema.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/schemas/refuter.schema.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/schemas/targeted-validator.schema.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/vectors/lens.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/vectors/refuter.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/bundle/vectors/targeted-validator.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/generated/provider-capabilities.baseline.json",
+  "contracts/review-provider-contract-mirror/v1.2.0/generated/provider-roles.baseline.json",
   "prompts/skill-creation.md",
   "skills/_shared/review-ledger-contract.md",
   "skills/branch-pr/SKILL.md",
@@ -162,6 +159,7 @@ const contractHashes = {
   "contracts/review-integration/v1/schemas/status-v2.schema.json": "dd9914b647a1d9edc4ecdcbed4f0c800b39ec290912d5c2a4cc6ba3098d5f21e",
   "contracts/review-integration/v1/schemas/status.schema.json": "250d2c646b8822b38eaefafd2bfdefa1134cc23a00e553a7201f33257573149a",
   "contracts/review-integration/v1/schemas/targeted-validation-request.schema.json": "52b91154693b4dd66983fc91ecf7197503555f2c9e85cac626cffd3035c53d65",
+  "contracts/review-integration/v1/schemas/transition-execution.schema.json": "ddee03bd0c1b6e70f21c399bae7fe528aa4ad46cebb5a48ec72b6e6b3694aa2d",
   "contracts/review-integration/v1/schemas/verification-evidence.schema.json": "fd15890bf2ef1db95d771ee7f468e9e64014351d7940f65604eb24f41e68a22f",
   "contracts/review-integration/v2/fixtures/capabilities.fixture.json": "17c150d851c15b3f0c20d18c2e2741eb2232ffa24f35aa71d6d30e90a85e42b7",
   "contracts/review-integration/v2/fixtures/consent.fixture.json": "203cc96d5c29ba0f27b5c4db04c2e88566e0a923d3a0cdb317f78d9065349075",
@@ -172,11 +170,13 @@ const contractHashes = {
   "contracts/review-integration/v2/schemas/capabilities.schema.json": "7ab061ed27bd3b929d6033cc20f56097e851f4454ca14a815255748b50191248",
   "contracts/review-integration/v2/schemas/consent.schema.json": "b2b4465338497f11927de91cb2e5da12b6cb4a1039afe05aebe1abbf53b21858",
   "contracts/review-integration/v2/schemas/failure.schema.json": "a56a2f715c3138d6f2cee37257cd6e758a15d4e0b1215745951d85831d148967",
+  "contracts/review-integration/v2/schemas/last-event-closure.schema.json": "612531204afa5941e4927c38e868c720a4519fe4b9a5a4ffd29f021dc053001d",
+  "contracts/review-integration/v2/schemas/opencode-provider-role.schema.json": "c6b9f216f89c044f8e844b55e7200114850cfbc16642bca0677f30a399d8aa9b",
   "contracts/review-integration/v2/schemas/operation.schema.json": "1c0128a0576064d4338ee0a1945e9d0d0569c1a7a2140217b2539af5d1a9ed1e",
   "contracts/review-integration/v2/schemas/repair.schema.json": "98a85fd45a8ae7f6211ffeeb3f9c478fa1dd1c17f385751f15f2111e6c3ab167",
   "contracts/review-integration/v2/schemas/start.schema.json": "2991e3fcca672d9257d61b6a336fb34e58b15a8e03f8a09a7adf892cae6a8085",
   "contracts/review-integration/v2/schemas/status.schema.json": "c4dcc736cfc6300560a3c4262d2d982368529d5c49d58d499552a3b0beef9212",
-  "docs/review-integration.md": "189f9b128cafaf225d2b6be53111f893ca46eb687fb9e5e051a84727b6a34bbc",
+  "docs/review-integration.md": "95a3df92785bc4d9f3b99e702aaf817ae0440bd16c83218d2c3f2aca67c280fb",
 };
 
 requiredPaths.push(...Object.keys(contractHashes));
@@ -247,7 +247,7 @@ export function gentleAiVersionPinMismatches({ installerVersion, releaseBaseUrl,
 // so this script never needs the generator to export anything it doesn't
 // already export for its own `--write`/`--check` CLI use.
 export function extractGeneratedRuntimeSources(packageRoot) {
-  const generatorPath = join(packageRoot, "scripts/build-git-commit-transaction-runner.mjs");
+  const generatorPath = join(packageRoot, "scripts/build-runtime-modules.mjs");
   const generatorSource = readFileSync(generatorPath, "utf8");
   const sourcesMatch = generatorSource.match(/const sources = \[([\s\S]*?)\];/);
   if (!sourcesMatch) {
@@ -316,7 +316,7 @@ async function main() {
   const generatedRuntimeSources = extractGeneratedRuntimeSources(root);
   const { drifted } = reconcileGeneratedRuntimeSources(root, generatedRuntimeSources, requiredPaths);
   if (drifted.length > 0) {
-    console.error("gentle-pi generated commit transaction runtime sources, runtime/*.mjs, and requiredPaths have drifted apart:");
+    console.error("gentle-pi generated runtime sources, runtime/*.mjs, and requiredPaths have drifted apart:");
     for (const entry of drifted) {
       const where = [];
       if (!entry.inSources) where.push("missing from generator sources");
@@ -334,7 +334,7 @@ async function main() {
   });
 
   if (driftedContracts.length > 0) {
-    console.error("gentle-pi packaged review-integration/v1 and review-integration/v2 contract bytes drifted from the byte-identical Gentle AI v2.4.0 contract:");
+    console.error("gentle-pi packaged review-integration/v1 and review-integration/v2 contract bytes drifted from the pinned v2.6.0 runtime's vendored Gentle AI contract artifacts:");
     for (const drift of driftedContracts) console.error(`- ${drift.relativePath}: expected ${drift.expected}, got ${drift.actual}`);
     process.exit(1);
   }
@@ -351,17 +351,17 @@ async function main() {
   if (unpinnedDigests.length > 0) {
     console.error("gentle-pi Gentle AI release digests are not pinned SHA-256 values:");
     for (const entry of unpinnedDigests) console.error(`- ${entry}`);
-    console.error("Refusing to pack/publish until scripts/gentle-ai-installer.mjs pins the published checksums.txt archive digests and extracted binary digests.");
+    console.error("Refusing to pack/publish until scripts/gentle-ai-installer.mjs pins the published release digests (checksums.txt archives for a stable, SHA256SUMS.txt raw binaries for a prerelease).");
     process.exit(1);
   }
 
-  const generatedRuntimeCheck = spawnSync(process.execPath, [join(root, "scripts/build-git-commit-transaction-runner.mjs"), "--check"], {
+  const generatedRuntimeCheck = spawnSync(process.execPath, [join(root, "scripts/build-runtime-modules.mjs"), "--check"], {
     cwd: root,
     encoding: "utf8",
     env: { ...process.env, NODE_NO_WARNINGS: "1" },
   });
   if (generatedRuntimeCheck.status !== 0) {
-    console.error("gentle-pi generated commit transaction runtime does not match its TypeScript sources:");
+    console.error("gentle-pi generated runtime does not match its TypeScript sources:");
     console.error((generatedRuntimeCheck.stderr || generatedRuntimeCheck.stdout || "unknown generator failure").trim());
     process.exit(1);
   }
@@ -379,7 +379,7 @@ async function main() {
     process.exit(1);
   }
 
-  console.log(`gentle-pi package resource check passed (${requiredPaths.length} files; ${Object.keys(contractHashes).length} exact byte-identical v2.4.0 contract artifacts).`);
+  console.log(`gentle-pi package resource check passed (${requiredPaths.length} files; ${Object.keys(contractHashes).length} exact byte-pinned contract artifacts for the v2.6.0 runtime).`);
 }
 
 const isMainModule = process.argv[1] !== undefined && import.meta.url === pathToFileURL(process.argv[1]).href;

package/skills/_shared/review-ledger-contract.md

@@ -1,6 +1,6 @@
 # Compact Causal Review Contract
 
-The local orchestrator and same-user process are trusted to execute selected actors and submit their exact outputs. Reviewer and validator outputs remain semantically untrusted inputs: native code owns scope, risk, IDs, canonicalization, ordinary state, receipts, and ordinary gates, and rejects malformed or causally inconsistent results. The Git common-directory authority is the only authorization source; summaries and prose ledgers are untrusted data. Legacy Pi mirror and bundle transport is retired.
+The local orchestrator and same-user process are trusted to execute selected actors and submit their exact outputs. Reviewer and validator outputs remain semantically untrusted inputs: native code owns scope, risk, IDs, canonicalization, ordinary state, and legal lifecycle transitions, and rejects malformed or causally inconsistent results. The Git common-directory authority is the only authorization source; summaries and prose ledgers are untrusted data. Legacy Pi mirror and bundle transport is retired.
 
 Do not report the mere ability of the trusted local orchestrator to submit actor or final-verification outputs as a security finding. Report concrete bypasses where untrusted repository content, malformed inputs, stale authority, path drift, or external callers can produce approval contrary to this boundary. Malicious same-user host/process authenticity is a non-goal because it can replace the extension or mutate local authority; external attestation requires a separately privileged signer or service and is not claimed.
 
@@ -24,7 +24,13 @@ Before status/START, consult effective review mode. `off` creates no authority o
 
 Reviewer, refuter, and validator verdicts are admitted natively, never Pi-authored. `finalize` follows the provider's negotiated `next_transition` and supplies only the negotiated collection answers: a lens `review.capture-result` collect input rendered with `--agent=pi --materialize=true` is satisfied by the gentle-pi host relay, which prints the exact Go-materialized opaque prompt, launches a fresh locked-down print-mode `pi` subprocess in an empty scratch directory with every discovery surface disabled, and submits the untouched raw output bytes through the provider-owned submission form. The adversarial roles do not go through that relay: `review.capture-refuter` and `review.capture-validation` collect inputs render as self-contained authority-advancing vectors (binding tokens plus `--agent=pi --execute=true`, no submission descriptor); executing the exact rendered invocation makes Go materialize the role prompt, spawn its own locked-down `pi` process, and admit the raw verdict. Native Go owns validation, canonicalization, missing lens/finding ID assignment, persistence, and hashing, and performs only the legal transition from the current compact state. The five states are `reviewing`, `correction_required`, `validating`, `approved`, and `escalated`.
 
-`validate` loads the terminal receipt and authority, derives the named live Git gate, and runs with zero actors. It never mutates compact authority.
+### Concurrent Reviewer Group (MANDATORY)
+
+When one fresh `collect.inputs` set contains multiple distinct independent `review.capture-result` reviewer slots, call `gentle_review_capture_group` once with the complete ordered provider bindings and its forecast acknowledgement. Before any materialization it validates the whole current group, its common binding fields, unique slot identities, and every provider submission descriptor; then it starts all reviewers before waiting. For canonical 4R, preserve `review-risk`, `review-resilience`, `review-readability`, `review-reliability` order.
+
+Each grouped launch runs only its own provider-issued `review.capture-result` binding, and admission remains in provider order. A typed terminal or nonterminal closure returns directly; a later stop after earlier admission reports bounded partial progress and never claims no mutation. If every submission returns without closure, reconcile fresh bound STATUS and return its declared action rather than inferring group success. On `correction_required`, continue only through exact bound STATUS and the provider-issued `review.capture-correction-plan` binding.
+
+`validate` is informational and runs with zero actors. It never mutates compact authority or controls delivery.
 
 ## Causal findings
 
@@ -41,7 +47,7 @@ Only severe `introduced`, `behavior-activated`, or `worsened` findings with vali
 
 Refuter rows may cite independent concrete proof and do not need to repeat reviewer `proof_refs`. `pre-existing` and `base-only` findings become non-blocking follow-ups. `unknown`, insufficient evidence, malformed severe claims, empty/malformed proof, missing/duplicate/extra refuter rows, and inconclusive severe outcomes escalate. `WARNING` and `SUGGESTION` remain informational.
 
-Actor output cannot authorize transitions, corrections, receipts, gates, or delivery.
+Actor output cannot authorize transitions, corrections, or delivery.
 
 ## Correction
 
@@ -59,21 +65,15 @@ Final verification evidence is supplied and hashed only during finalization. Fai
 
 The negotiated native provider owns compact-v2 storage and its private paths. Pi consumes only typed START, FINALIZE, target status, validation, recovery, reconciliation, and SDD-binding results. Content-derived revisions, compare-and-swap replacement, exact retry idempotency, stale/semantic retry rejection, semantic validation, terminal immutability, atomic publication, and receipt readback remain provider guarantees.
 
-Existing graph-v1 ordinary lineages remain readable and gate-validatable but reject new mutation. Legacy graph bundle export/import is retired. Judgment Day remains mutable on graph-v1. Pre-graph numbered authority remains destructive-reset-only, while native target status owns mixed-authority ambiguity and the required maintainer action.
-
-Permanent Pi-owned consumer infrastructure is limited to canonical identity primitives, repository/common-directory binding, immutable candidate views, and the publication-gate command projection. These modules are not authority mirrors.
-
-## Lifecycle gates
-
-Pre-commit, pre-push, pre-PR, and release validate an approved receipt against one exact typed command target with zero actors. Native validation uses `gentle-ai.review-integration/v2`, loads authority and receipt, derives live target/publication evidence, then immediately reloads authority and re-derives target/publication evidence before allow. Authorized direct commit uses the durable hook/native-validation transaction and unresolved recovery blocks publication. The Pi-owned `review-publication-gate` module isolates command projection and publication revalidation from graph-v1 authority storage without changing these guarantees.
+Existing graph-v1 ordinary lineages remain readable for compatibility but reject new mutation. Legacy graph bundle export/import is retired. Judgment Day remains mutable on graph-v1. Pre-graph numbered authority remains destructive-reset-only, while native target status owns mixed-authority ambiguity and the required maintainer action.
 
-PR #1216 introduced the v2.1.1 `<remote>/<branch>` selector contract that v2.1.2 inherits unchanged.
+Permanent Pi-owned consumer infrastructure is limited to canonical identity primitives, repository/common-directory binding, and immutable candidate views. These modules are not authority mirrors.
 
-Pi additionally registers one one-shot authorization for the exact subsequent command. Successful `/gentle:review-mode disable` clears pending lifecycle authorization; each lifecycle command rechecks mode, so out-of-band disable discards stale authorization and proceeds organically, never as approval. Full target/publication derivation runs after controller-time native allow, before bash-time native validation, and again after that validation before command allow. `gh pr create` binds repository precedence (`--repo`, `GH_REPO`, local inference), the effective source/value, and the exact advertised remote head commit equal to reviewed local `HEAD`; pre-PR keeps fetch-side repository/base/head semantics. Existing native push destinations bind the command remote, destination ref, old/new objects, exact destination selector, and advertised old commit in one rederived fingerprint only when effective push and fetch URL/identity match. Split fetch/push pre-push is an upstream v2.1.1 contract limitation: `<remote>/<branch>` resolves through fetch-side remote-tracking state even when Pi probes `pushurl`, so Pi fails closed before native validation with `native-split-fetch-push-unsupported-until-upstream-supports-explicit-push-base`. Native first-push authorization remains unsupported until a separate follow-up adds a persisted explicit advertised-base source, so a missing destination fails closed instead of inferring an upstream, default branch, or nearest ancestor. Publication probes are shell-free, bounded, and cancellation-aware, and the complete bash-time publication/native revalidation has one aggregate bounded deadline combined with Pi's cancellation signal when available. Repository identity, first-push destination, push destination, exact PR base/head, release evidence, protected-main release fast path, and fail-closed dangerous-command interception remain mandatory. Base advancement is unsupported without a receipt-bound signed CI trust root and therefore fails closed.
+## Delivery boundary
 
-Release from protected `main` may bypass receipt validation only when the tag targets the current immutable `origin/main` SHA, required CI for that exact SHA is independently proven successful, the remote head is rechecked before tag push, and no fresh risk evidence exists. Major and post-incident releases require explicit extraordinary review.
+Commit, push, pull-request creation, and release creation are not RDD gates. Review outcomes and receipt state are informational and never authorize, consume, rewrite, or block a Bash delivery command; ordinary repository policy owns delivery. Pi does not inspect RDD mode or native authority for those commands.
 
-Review transactions, validation, and SDD never commit, push, create a PR, release, or publish.
+Dangerous-command confirmation/safety and destructive-review-maintenance consent remain independent. Review transactions, validation, and SDD never perform delivery commands themselves.
 
 ## Judgment Day
 

package/skills/chained-pr/SKILL.md

@@ -14,6 +14,8 @@ Load this skill when a planned PR may exceed **400 changed lines**, SDD forecast
 ## Hard Rules
 
 - Split PRs over **400 changed lines** unless a maintainer explicitly accepts `size:exception`.
+- The budget constrains how work is **sliced**, never the code itself. Never delete comments, blank lines, docs, or tests, and never compress or restyle code, to fit under the budget.
+- Slicing is bounded: make **one** honest slicing pass. If no cohesive split brings every slice within budget, stop iterating, keep the best cohesive split, and report the final line count with a `size:exception` recommendation.
 - Keep each PR reviewable in about **≤60 minutes**.
 - Use one deliverable work unit per PR; keep tests/docs with the unit they verify.
 - State start, end, prior dependencies, follow-up work, and out-of-scope items in every chained PR.
@@ -30,6 +32,7 @@ Load this skill when a planned PR may exceed **400 changed lines**, SDD forecast
 | PR >400, each slice can land independently | Use Stacked PRs to main. |
 | PR >400, feature must integrate before main | Use Feature Branch Chain with tracker. |
 | Generated/vendor/migration diff cannot split cleanly | Ask maintainer for `size:exception`. |
+| No cohesive split fits the budget after one slicing pass | Stop; deliver the best split, report the overage and why it cannot shrink further, and recommend `size:exception`. |
 | SDD provides `delivery_strategy` | Follow it before apply/PR creation. |
 
 ## Execution Steps

package/skills/cognitive-doc-design/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: cognitive-doc-design
+name: gentle-ai-cognitive-doc-design
 description: "Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs."
 license: Apache-2.0
 metadata:

package/skills/comment-writer/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: comment-writer
+name: gentle-ai-comment-writer
 description: "Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments."
 license: Apache-2.0
 metadata:

package/skills/gentle-ai/SKILL.md

@@ -17,11 +17,9 @@ When asked who or what you are, answer as el Gentleman: a Pi-specific coding-age
 - Use OpenSpec-style artifacts for proposal, specs, design, tasks, apply progress, verify report, and archive notes.
 - If tests exist, follow strict TDD: RED, GREEN, TRIANGULATE, REFACTOR, and record evidence.
 - Keep one parent session responsible for orchestration; child subagents should receive concrete phase work and must not spawn more subagents.
-- Parent-only delegation triggers apply after complexity appears: 4+ files for understanding, 2+ non-trivial files to write, commit/PR after code changes, tooling/worktree incidents, or long sessions with accumulating complexity.
-- As parent, prefer `scout`/`context-builder` for context-heavy exploration and one forked `worker` for implementation. Review lenses run only when selected by ordinary transaction start; do not call a generic `reviewer` or add lifecycle review actors.
+- Parent-only delegation triggers apply after complexity appears: 4+ files for understanding, 2+ non-trivial files to write, tooling/worktree incidents, or long sessions with accumulating complexity.
 - Keep writes single-threaded unless the user explicitly approves isolated parallel worktrees.
 - Forecast review workload before large changes; ask before producing oversized or multi-area diffs.
-- Start review routing only inside a bound ordinary transaction; lifecycle commands use approved receipts and exact typed targets instead of ambient-diff advice.
 - Keep dangerous-command safety independent and authoritative.
 - Never claim persistent memory is available because of el Gentleman itself; memory is provided by separate packages/tools when active.
 - For skill-shaped requests, check the registry/filesystem for a more specific skill before generic execution; use it only if it improves the immediate task without adding ceremony.
@@ -46,87 +44,22 @@ clarify → explore → proposal → spec → design → tasks → apply → ver
 For bounded implementation with subagents:
 
 ```text
-clarify → scout/context-builder when context-heavy → one worker → selected review lens(es) → worker fixes → verify
+clarify → scout/context-builder when context-heavy → one worker → verify
 ```
 
 Hard delegation triggers:
 
 - **4-file rule**: reading 4+ files to understand means delegate exploration.
-- **Multi-file write rule**: touching 2+ non-trivial files means use one worker; any review remains inside the bound transaction budget.
-- **Lifecycle gate rule**: commit/push/PR/release validates an approved receipt and exact typed target with zero actors; missing or changed authority fails closed.
-- **Incident rule**: after wrong cwd, accidental worktree/repo mutation, merge recovery, confusing test command, or environment workaround, diagnose separately without reopening a closed lineage or resetting its budget.
+- **Multi-file write rule**: touching 2+ non-trivial files means use one worker.
+- **Incident rule**: after wrong cwd, accidental worktree/repo mutation, merge recovery, confusing test command, or environment workaround, diagnose separately.
 - **Long-session rule**: after roughly 20 tool calls, 5 exploratory reads, or 2 non-mechanical edits with no delegation and accumulating complexity, pause and choose a non-review subagent or justify not doing so.
 
 ## Review Lens Selection
 
-Never request a subagent named `reviewer`; it is an intent, not an installed agent. Select concrete review agents by risk profile:
+`review-risk`, `review-reliability`, `review-resilience`, and `review-readability` are Gentle AI review-lens vocabulary. This injected skill does not select, invoke, sequence, or retry those lenses; any applicable runtime uses only its dynamically supplied instructions.
 
-| Context | Review lens |
-| --- | --- |
-| Clear naming, structure, maintainability, small refactors | `review-readability` |
-| Behavior, state, tests, determinism, regressions | `review-reliability` |
-| Shell/process integration, partial failures, recovery, degraded dependencies | `review-resilience` |
-| Security, permissions, data exposure/loss, architecture, dependencies | `review-risk` |
-| Large PR, hot path, or >400 changed lines | Full 4R: `review-risk`, `review-resilience`, `review-readability`, `review-reliability` |
+## Gentle AI RDD Ownership
 
-For a standard change, choose exactly one dominant-risk lens using the fixed precedence encoded by the controller. Only high-risk changes—security/auth/update/payments, data loss/exposure, permissions, shell/process integration, or more than 400 authored changed lines—run the canonical full 4R set.
-
-## Bounded Review Transaction Contract
-
-Call `gentle_review` INSPECT before START. The package-local Gentle AI v2.4.0 executable negotiates `gentle-ai.review-integration/v2`; INSPECT is target-scoped status, not a Pi-built authority inventory. New ordinary review uses native compact-v2 `start -> finalize -> validate`. START receives a JSON-serialized ordinary input; an optional repository-local `policyPath` and an explicit `baseRef` paired with `committedOnly: true` are the only selectors. Native code derives Git scope, untracked paths, lineage, risk tier/reasons, lenses, authored lines, and correction budget. `judgment-day` remains explicit and separate.
-
-If INSPECT or START reports `blocked-legacy` or `blocked-mixed`, explain that legacy authority cannot be migrated and request explicit user authorization for the exact destructive-reset challenge. RESET and RECOVER each require fresh operation-bound confirmation through the interactive Pi UI and fail closed headlessly. The UI cannot cryptographically attest the human's identity; its residual trust is the operator controlling that Pi session, while exact challenge binding remains runtime-enforced. Only after authorization, the controller routes RESET and RECOVER_LOCK to the audited native `gentle-ai review reclaim` operation and RECOVER to native `gentle-ai review recover`; supply the exact native inputs (`lineage`/`actor`/`reason`, or the predecessor lineage, expected predecessor revision, successor lineage, disposition, actor, and reason bindings). A `native-input-required` envelope is a request for those exact values — never invent them. After a committed native recovery record, INSPECT before any fresh ordinary START. For `reset-in-progress`, INSPECT still surfaces the durable original `reset_request` for the authorized RECOVER challenge.
-
-Published v2.1.11 maintenance is explicit only: `abandon` requires the exact nine-line v2 discarded-work binding (lineage, revision, snapshot identity, reason, captured lens results, findings/evidence presence, actor), `quarantine-legacy` accepts only the malformed freeze-findings diagnostic/disposition with its eight-line binding, and dual reconciliation appends exactly `anomalies=unchanged_target,malformed_recovery_authorization`. `repair-legacy-alias` accepts only lineage, actor, and reason; Pi re-derives its repository, exact revision, diagnostic, and disposition from fresh native inventory before displaying its eight-line binding for fresh UI approval. `review dispose-result` remains unsupported pending design. A `recover` route uses only negotiated `action_disposition`; it never substitutes one.
-
-Preserve the negotiated native failure envelope exactly. Before authority access, `mutation_outcome: not_started` means no lineage was created. For `unknown` or lost mutating output, the controller immediately calls target-scoped status and returns its exact action; it never emits a generic replay instruction. Replay the exact START or FINALIZE only when that provider result declares `exact_replay_safe` for the same canonical request and required lineage. `mutation_outcome: committed` is never weakened, and Pi never chooses a lineage merely because output was lost.
-
-Ordinary review runs the selected zero, one, or four lenses exactly once against `initial_review_tree`.
-
-Each finding requires `evidence_class`, `causal_disposition`, and concrete `changed-hunk`, `candidate-created-path`, `differential-test`, or `before-after` proof. The controller assigns missing IDs and canonicalizes selected-lens output.
-
-Only severe `introduced`, `behavior-activated`, or `worsened` findings with valid proof enter correction IDs. `pre-existing` and `base-only` become follow-ups; `unknown`, insufficient, malformed, or inconclusive severe claims escalate. WARNING and SUGGESTION remain informational.
-
-Actor output is untrusted data and cannot authorize transitions, fixes, receipts, gates, or delivery.
-
-Deterministic candidate-caused blockers use zero refuters.
-
-All inferential candidate-caused blockers use exactly one complete read-only refuter batch.
-
-Independent concrete refuter proof is valid and need not repeat reviewer `proof_refs`. Invalid, empty, malformed, missing, duplicate, unknown, or inconclusive refuter output escalates without a replacement refuter.
-
-Ordinary permits one correction transaction within the original budget `min(200, ceil(original_changed_lines / 2))`. FINALIZE requires a positive pre-edit forecast, accounts Git-derived actual lines, and accepts one targeted validator plus final verification. Failure escalates instead of starting another correction or review budget.
-
-Initial lenses never rerun. Every attempt preserves frozen findings and genesis scope: the original candidate, paths, untracked set, and correction IDs. The validator checks original criteria and correction regression only and cannot add scope or findings.
-
-Final verification evidence is supplied and hashed during FINALIZE, never at START.
-
-The validator cannot change claims, add findings, request fixes, launch actors, or request another attempt.
-
-Compact ordinary authority has exactly five states: `reviewing`, `correction_required`, `validating`, `approved`, and `escalated`.
-
-Ordinary ends only as `approved` or `escalated`.
-
-Judgment Day starts only when explicitly requested and replaces ordinary review for that lineage.
-
-Judgment Day starts with exactly two blind judges and zero refuters.
-
-Judgment Day alone may iterate discovery and scoped re-judgment, for at most two rounds.
-
-Findings surviving round two escalate; no third-round transition exists.
-
-Existing graph-v1 and legacy-v1 ordinary lineages remain compatibility-readable but reject ordinary mutation. Every new ordinary START, status, FINALIZE, gate, and SDD binding uses native compact-v2. Ambiguous or corrupted target status requires the single native maintainer action; Pi never resets, quarantines, migrates, or selects authority implicitly. Judgment Day remains explicit and separate.
-
-PR #1216 introduced the v2.1.1 `<remote>/<branch>` selector contract that v2.1.2 inherits unchanged.
-
-Native gates are read-only and always pass `--contract gentle-ai.review-integration/v2`. Pi registers one exact one-shot command authorization and rederives before and after bash-time native validation. Authorized direct `git commit` is rewritten through the package-owned durable transaction: run the effective pre-commit hook once, derive the post-hook index tree, validate that exact tree natively, preserve remaining hooks through proxies, commit without rerunning pre-commit, then prove `HEAD^{tree}`. An unresolved transaction blocks push, PR, and release; recovery never resets Git content automatically. Native pre-PR binds GitHub CLI repository precedence plus the exact advertised remote head equal to reviewed local `HEAD`. Publication probes remain shell-free, bounded, cancellation-aware, and fail closed on unsupported topology.
-Release from protected `main` may bypass receipt validation only when the tag targets the current immutable `origin/main` SHA, required CI for that exact SHA is successful, the remote head is rechecked before tag push, and no fresh risk evidence exists; otherwise release fails closed through native receipt validation.
-Major and post-incident releases require explicit extraordinary review even when fast-path checks pass.
+Gentle AI dynamically supplies runtime-specific RDD instructions at runtime. Treat them as the sole lifecycle authority. This skill never defines a review route, command sequence, state machine, approval or gate policy, recovery path, or fallback; when no native instruction is available, follow ordinary repository policy without inventing one.
 
 Dangerous-command safety remains independent and authoritative.
-
-SDD completion adds no review or Judgment Day pass.
-
-Review operations, validation, and SDD perform no push, PR creation, release, or publication. Only the separate durable commit runner may create one local commit after exact native authorization and HEAD proof.
-
-The package ensures SDD agents and chains are available as global Pi runtime assets. Adversarial review roles (refuter, targeted validator) are never Pi-authored: the provider renders self-contained capture vectors and Go runs its own locked-down `pi` process on them. Project/user agent definitions are overrides and may shadow package assets; never rewrite or claim their effective permissions. Use `/gentle:install-sdd --force` only for recovery or intentional global refresh.

package/skills/issue-creation/SKILL.md

@@ -4,18 +4,14 @@ description: "Create and triage GitHub issues from repository evidence. Trigger:
 license: Apache-2.0
 metadata:
   author: gentleman-programming
-  version: "1.2"
+  version: "1.3"
 ---
 
 # Issue Creation
 
-## When To Use
-
-Use this skill when creating, drafting, triaging, or approving an issue in the current GitHub repository.
-
 ## Core Rule
 
-Discover the repository's actual contribution workflow before proposing or publishing an issue. Templates, labels, approval gates, and Discussions support are repository policy, not universal GitHub behavior.
+Discover the target repository's contribution workflow before proposing or publishing. YAML Issue Forms are the format authority for the default automated path: materialize reviewed answers into a private `BODY_FILE` and publish with `--body-file`.
 
 ## Safe Discovery
 
@@ -27,123 +23,87 @@ REPO="$(gh repo view --json nameWithOwner -q .nameWithOwner)"
 REPO_URL="$(gh repo view --json url -q .url)"
 HOST="${REPO_URL#*://}"
 HOST="${HOST%%/*}"
+TARGET="$HOST/$REPO"
 gh repo view --json nameWithOwner,url,hasDiscussionsEnabled,hasIssuesEnabled,isBlankIssuesEnabled
-git ls-files CONTRIBUTING.md CONTRIBUTING.* .github/CONTRIBUTING.md .github/ISSUE_TEMPLATE
+git ls-files README.md CONTRIBUTING.md CONTRIBUTING.* .github/CONTRIBUTING.md .github/ISSUE_TEMPLATE .github/ISSUE_TEMPLATE/config.yml
 gh api --hostname "$HOST" --paginate "repos/$REPO/labels?per_page=100" --jq '.[].name'
 ```
 
-Also inspect:
-
-- repository instructions such as `CONTRIBUTING.md` and `README.md`;
-- files under `.github/ISSUE_TEMPLATE`;
-- `.github/ISSUE_TEMPLATE/config.yml` when present;
-- issue forms, required fields, and labels declared by each template;
-- existing open and closed issues for duplicates and established wording.
+Inspect `README.md`, contribution instructions, `.github/ISSUE_TEMPLATE/config.yml` contact links, forms, labels, and open and closed issues. For questions/support, follow repository-prescribed Discussions/contact routing when available; otherwise ask or stop. Complete target verification for `REPO`, `HOST`, and `TARGET`. Fail closed before mutation when authentication, target verification, issue availability, policy, form selection, or required metadata is missing or ambiguous. A blank fallback is allowed only when `isBlankIssuesEnabled` is explicitly true.
 
-Stop and ask for repository context if authentication, repository resolution, verification that REPO and HOST are non-empty, required metadata is unavailable, hasIssuesEnabled is false, or policy discovery fails. Never continue from failed discovery into issue publication.
-
-A no-template fallback is allowed only when isBlankIssuesEnabled is explicitly true. Otherwise follow discovered contact links or stop and ask; never publish.
-
-After discovery and review, build optional label arguments using only labels that exist and repository policy permits the actor to apply:
+Build `LABEL_ARGS` only from reviewed labels that exist and policy permits the actor to apply:
 
 ```bash
 LABEL_ARGS=()
-# Repeat for each reviewed, permitted discovered label.
-LABEL_ARGS+=(--label "$LABEL")
+LABEL_ARGS+=(--label "$LABEL") # Repeat only for each permitted discovered label.
 ```
 
-An empty array applies no label; do not invent labels.
-
-## Workflow
+## Duplicate And Form Decision
 
-1. Describe the problem or request in one sentence and derive a short search query.
-2. Search open and closed issues:
+1. Describe the report in one sentence, derive `QUERY`, then complete one duplicate search across open and closed issues:
 
    ```bash
-   gh issue list --repo "$HOST/$REPO" --state all --search "$QUERY" --limit 1000
+   gh issue list --repo "$TARGET" --state all --search "$QUERY" --limit 1000
    ```
 
-   If 1000 results are returned or completeness remains uncertain, narrow the search, use read-only API discovery, or stop and ask before publishing.
-
-3. If an issue already covers the same behavior, comment there instead of creating a duplicate.
-4. Choose a repository-provided template only when its purpose matches the report.
-5. Fill every required template field from known evidence. Ask for missing facts rather than inventing them.
-6. Apply labels only when they exist and repository guidance establishes who should apply them.
-7. Publish only after the title, body, target repository, and selected template or fallback have been reviewed, and the pre-submission privacy review below has passed.
-
-## Pre-submission Privacy Review
-
-Pre-submission privacy review is mandatory. Scan every issue body immediately before `gh issue create`. The scan replaces — never deletes — environment-specific data with explicit placeholders so the reproduction still teaches:
-
-| Category | Replace with | Example (before → after) |
-|----------|---------------|---------------------------|
-| Private project names | `<project-name>` | `my-private-project-b` → `<project-name>` |
-| Usernames | `<user>` | `C:\Users\my-real-username\go\bin` → `C:\Users\<user>\go\bin` |
-| Hostnames | `<hostname>` | `devbox-macbook.local` → `<hostname>` |
-| Home paths | `/home/<user>` or `C:\Users\<user>` | (covered above) |
-| API keys, tokens, passwords | `<token>` / `<password>` | `ghp_abc123...` → `<token>` |
-| Internal ports / hostnames | `<host>:<port>` | `10.0.0.42:5432` → `<host>:<port>` |
-
-Do NOT redact intentionally public identifiers: tool names (`gentle-ai`, `engram`, `go`, `node`, `python`), package names, public documentation URLs, generic example domains (`example.com`, `localhost`). Keep reproduction structure with placeholders — never redact an example into nothingness.
-
-**Rule of thumb:** if the reader can run the reproduction step after you replace every identifier with its placeholder, the sanitization is correct. If a step becomes impossible (because the placeholder consumed a needed value), that step needs the value — and you should mark it `<value-required>` and explain in the body what the user should fill in.
+   If results are saturated or completeness is uncertain, narrow the read-only search or stop. Comment on a confirmed duplicate instead of creating one. Before commenting on a confirmed duplicate, perform the same privacy scan/redaction on the exact comment body as for publication.
+2. Select one repository-provided form only when its declared purpose matches. If multiple forms match and policy does not distinguish them, stop and request that decision.
+3. For a YAML form, read its schema and establish controls in declared order. Support only `input`, `textarea`, `dropdown`, and `checkboxes`. Markdown controls are non-answer guidance: honor their visible instructions when collecting and materializing adjacent answers, but do not render them as response sections. Fail closed before mutation on malformed, unsupported, missing, or ambiguous required structure or answers. A malformed schema, or missing or ambiguous required answers, fail closed: do not open a browser or mutate. A browser handoff is available only when the user explicitly requests browser completion or a syntactically valid selected form cannot safely/faithfully be represented by the automated path; otherwise report why automation is unsafe and stop.
 
-## Template Paths
+| Control | Required handling |
+| --- | --- |
+| `input` / `textarea` | Preserve the visible label. Require an answer when `validations.required` is true; otherwise render `_No response_`. |
+| `dropdown` | Preserve visible labels and options. Require exact selected option text; single-select has one selection, and multi-select preserves selections in declared options order. A required dropdown needs at least one valid selection; an optional dropdown with no selection renders `_No response_`. |
+| `checkboxes` | Preserve the visible label and every option as `- [x]` or `- [ ]` in declared order. Enforce individually required checkboxes and require explicit first-person affirmation for first-person option text. |
 
-Do not guess a template filename. If multiple templates could apply and repository guidance does not distinguish them, stop and ask which one to use.
+For each answer, render `### <visible label>` followed by its materialized value. For `textarea.attributes.render`, fence the answer with the declared language and a fence long enough for its content. Never invent answers, selections, confirmations, or labels.
 
-- .yml and .yaml files are GitHub Issue Forms. Do not parse or render their schema. Open the web issue chooser and stop for human completion:
+A Markdown template may be completed only from known evidence into the same private `BODY_FILE`. If no matching template exists, use the reviewed structured blank fallback only when blank issues are explicitly enabled; otherwise stop without publishing.
 
-  ```bash
-  gh issue create --repo "$HOST/$REPO" --web "${LABEL_ARGS[@]}"
-  ```
+## Review And Publication
 
-- .md files are Markdown templates. Read the matching template, complete it from known evidence into a reviewed BODY_FILE, then publish it:
+Before the single create attempt, review the target, title, selected form or permitted fallback, exact body, and permitted labels. Perform a privacy scan immediately before publication: replace private project names, usernames, hostnames, home paths, credentials, and private network addresses with useful placeholders without removing reproduction structure.
 
-  ```bash
-  gh issue create --repo "$HOST/$REPO" --title "$TITLE" --body-file "$BODY_FILE" "${LABEL_ARGS[@]}"
-  ```
-
-## No-Template Fallback
-
-When the repository permits issue creation, provides no matching template, and isBlankIssuesEnabled is explicitly true, prepare a structured body with these sections:
-
-- problem or requested outcome;
-- reproduction or motivating example;
-- expected behavior;
-- actual behavior or current limitation;
-- environment and relevant evidence;
-- alternatives or workarounds, when applicable.
-
-Publish the reviewed fallback explicitly:
+Create one owner-only temporary directory outside the repository for both private files; restrict it to the current user and clean up both files on every exit/outcome:
 
 ```bash
-gh issue create --repo "$HOST/$REPO" --title "$TITLE" --body "$BODY" "${LABEL_ARGS[@]}"
+umask 077
+REPO_ROOT="$(git rev-parse --show-toplevel)" || exit 1
+REPO_ROOT="$(cd "$REPO_ROOT" && pwd -P)" || exit 1
+if [ "$REPO_ROOT" = "/" ]; then
+  printf '%s\n' "Temporary directory is inside the repository" >&2; exit 1
+fi
+TMP_DIR="$(TMPDIR=/tmp mktemp -d /tmp/gentle-ai-issue.XXXXXXXX)" || exit 1
+trap 'rm -rf -- "$TMP_DIR"' EXIT
+TMP_DIR_REAL="$(cd "$TMP_DIR" && pwd -P)" || exit 1
+case "$TMP_DIR_REAL/" in
+  "$REPO_ROOT/"*) printf '%s\n' "Temporary directory is inside the repository" >&2; exit 1 ;;
+esac
+chmod 700 "$TMP_DIR_REAL"
+BODY_FILE="$TMP_DIR_REAL/body.md"
+READBACK_FILE="$TMP_DIR_REAL/readback.json"
 ```
 
-If blank issues are not explicitly enabled, follow discovered contact links or stop and ask. Never publish a no-template fallback.
-
-## Labels And Approval
+Make one mutation attempt through the automated path and publish exactly once:
 
-Treat labels and approval gates as conditional:
+```bash
+gh issue create --repo "$TARGET" --title "$TITLE" --body-file "$BODY_FILE" "${LABEL_ARGS[@]}"
+```
 
-- use only labels returned by repository discovery;
-- follow contribution guidance for who may apply each label;
-- wait when repository policy requires maintainer approval before implementation;
-- do not invent a status or priority taxonomy when none is documented.
+When browser completion is available under the form decision above, an optional, separate browser handoff may open the repository form. It is never proof of publication and is never a response to malformed schemas or missing/ambiguous required answers:
 
-## Questions And Discussions
+```bash
+gh issue create --repo "$TARGET" --web
+```
 
-Use Discussions only when `hasDiscussionsEnabled` is true and repository guidance routes the question there. Otherwise follow documented support/contact links or ask the user where the question belongs. Never link to another repository's Discussions page.
+Do not retry a timeout, network failure, missing identity, or other uncertain result. Capture the returned issue number, then read it back from the verified target host before reporting success:
 
-## Triage Decision
+```bash
+gh issue view "$NUMBER" --repo "$TARGET" --json number,url,title,body,state,labels >"$READBACK_FILE"
+```
 
-Before approving or closing an issue, verify:
+Confirm that read-back identifies the target-host issue and that title and body match after only CRLF-to-LF and trailing-final-newline normalization. Report `confirmed` only after this target-host read-back. Otherwise report `no_write` when an authoritative rejection proves no issue was created, or `unknown` and stop all later mutations.
 
-- it describes a concrete bug or scoped improvement rather than an unsupported question;
-- it is not a duplicate;
-- the report contains enough evidence for an implementation decision;
-- the requested behavior is in repository scope;
-- labels and status changes follow the current repository's policy.
+## Triage
 
-If any point is uncertain, keep the issue in the repository's review state and request the smallest missing evidence.
+Before approving or closing an issue, verify it is concrete, non-duplicate, sufficiently evidenced, in scope, and consistent with repository label/status policy. If any point is uncertain, retain the repository review state and request the smallest missing evidence.

package/skills/judgment-day/SKILL.md

@@ -11,9 +11,11 @@ metadata:
 
 Load this skill only when the user explicitly requests Judgment Day, Judgement Day, dual/adversarial review, or an equivalent trigger. Resolve one exact target before starting.
 
-Judgment Day is a standalone developer tool: judges run whenever asked, on any runtime, and need no review transaction, runtime identity, or delivery-receipt machinery to start. It replaces ordinary 4R as the adversarial method for that target; never run both.
+Judgment Day is a standalone developer tool: judges run whenever asked, on any runtime, and need no review transaction, runtime identity, or delivery-receipt machinery to start. It neither enables nor replaces an ordinary 4R lifecycle; a separately requested ordinary review remains independent.
 
-Judgment Day starts only when explicitly requested and replaces ordinary review for that lineage.
+Judgment Day starts only when explicitly requested. It does not start, configure, or consume ordinary review for that lineage.
+
+Historical compatibility note (obsolete): Judgment Day starts only when explicitly requested and replaces ordinary review for that lineage. Current behavior is the independent lifecycle above.
 
 ## Transaction Rules
 
@@ -63,11 +65,7 @@ Each scoped fix returns candidate-tree and fix-diff evidence. It cannot mint aut
 
 ## Lifecycle Boundary
 
-A judgment issues no receipt and carries no delivery authority: it satisfies no commit, push, PR, or release gate. When the caller explicitly wants delivery authority for the same target, run the ordinary negotiated review lifecycle as its own step; a runtime that cannot uphold receipt guarantees loses the receipt, not the judgment.
-
-Pre-commit, pre-push, and PR gates validate approved receipts and exact typed targets with zero actors.
-Release from protected `main` may bypass receipt validation only when the tag targets the current immutable `origin/main` SHA, required CI for that exact SHA is successful, the remote head is rechecked before tag push, and no fresh risk evidence exists; otherwise release fails closed through native receipt validation.
-Major and post-incident releases require explicit extraordinary review even when fast-path checks pass.
+Judgment Day is independent: it creates no delivery authority, enables no ordinary review, and changes no commit, push, PR, or release policy. A separately requested ordinary review remains an independent lifecycle and cannot consume a Judgment Day result as a receipt or authority. Ordinary repository policy owns delivery.
 
 Dangerous-command safety remains independent and authoritative.