arkgate 3.6.1 → 3.7.0

package/templates/skills/ark-explore.md

@@ -123,6 +123,7 @@ Useful split: **core product tree** | **field path** (`examples/`, starters) | *
 6. **§G spaghetti / design-depth** when signals fire (or always on brownfield).
 7. Ranked rows that **change a decision**; each bet has a **success signal** (not a file count).
 8. Hard lines: never weaken the contract; never invent mechanical-safe kinds; never claim ENFORCE from type-only cleanup while false-green doctor ids are active.
+9. **Parse honesty:** if `doctor.parseHealth.affectedFiles > 0`, open and name those paths; never describe them as clean or successfully inspected. The advisory does not change the gate verdict.
 
 ## Reconnaissance pass (do all that apply)
 
@@ -150,6 +151,12 @@ Useful split: **core product tree** | **field path** (`examples/`, starters) | *
 
 Mark the **golden** pattern to copy. Do not only list layer file counts.
 
+When `doctor.physicalCohesion` includes `reshapeDecisions`, treat current rejected/deferred
+targets as explicit adopter decisions, not residual to re-fight. Keep their mirror facts in the
+map. When the user accepts, defers, or rejects a live `reshapePilot.nextPilot`, record the card's
+exact `decisionTarget` with a reason (and optional `reviewBy`) in
+`.ark/reshape-decisions.json`. Never infer or suppress from free-form golden-pattern prose.
+
 ### C. Coupling & debt (measure, don’t guess)
 Prefer evidence over aesthetics:
 - **Fan-in / importers** of hot modules (who imports the suspect file?).
@@ -215,7 +222,7 @@ ENFORCE without Shape progress is **`ENFORCE · design-weak`** — say that out
 | Smell id (label) | How you detect it in source |
 |------------------|-----------------------------|
 | `io-under-application` | I/O clients under Application; empty Domain/Persistence (also doctor when present) |
-| `handler-in-persistence` | HTTP/route bodies under repo/db globs |
+| `handler-in-persistence` | Static framework HTTP imports, `defineRoute` calls, or route bodies under Persistence-role repo/db globs (first 800 sorted candidates; no advisory is not whole-tree proof above that bound) |
 | `god-module` | High fan-in + wide export surface + mixed concerns |
 | `domain-logic-in-ui` | `can*` / `calculate*` / policy constants in hooks/pages |
 | `mixed-pattern-cluster` | Same feature area uses ≥2 incompatible layouts |

package/templates/skills/ark-fix.md

@@ -105,12 +105,22 @@ If the “fix” is really a missing business intent or Domain home for a rule:
 - Prefer mechanical-safe kinds when the plan tags them; otherwise design judgment carefully.
 - Code only — no DB migrations unless user asked.
 
+## Mechanical-edit hygiene (Y04 — outcome gate)
+
+- Header injection must **merge into the existing doc comment**; the kept result has one `/**`, not stacked headers.
+- Route completion or movement must **preserve the original typed `defineRoute<…>(opts, handler)` call**; reconstruct that call instead of extracting untyped opts/handler constants that drop generics or contextual typing.
+- A convention-only `*-data.ts` stub is not a fix: move the real code or **leave the placeholder file uncreated**; never write `import "server-only"; export {}` as an empty naming token.
+- Keep the edit only when the **previously clean file stays typecheck-clean**. Otherwise roll it back and treat the change as judgment.
+
 ## Reshape findings (X04 — never mechanical)
 
 If `doctor.physicalCohesion` fires while you fix: do **not** fold reshape moves into your fix
 batch. Physical moves run only through `/ark-loop`'s one-pilot loop; merge decisions only as
 `/ark-architect` merge cards. A cohesion finding is context for your fix, never a license to
-reorganize.
+reorganize. Respect `physicalCohesion.reshapeDecisions`: never revive a current rejected/deferred
+target from the still-visible facts. If the user makes a verdict while reviewing the finding,
+record its exact `decisionTarget` + reason in `.ark/reshape-decisions.json`; never infer one from
+golden-pattern prose.
 
 ## Done
 

package/templates/skills/ark-loop.md

@@ -82,12 +82,21 @@ feature dirs, plan clusters), you **may** dispatch **subagents**:
 
 Never auto: free value uses of imports, multi-import files, dynamic import/require, forbidden globals, cycles, port-proof inject, multi-file adapter scaffolding without proof.
 
+## Mechanical-edit hygiene (Y04 — outcome gate)
+
+- Header injection must **merge into the existing doc comment**; the kept result has one `/**`, not stacked headers.
+- Route completion or movement must **preserve the original typed `defineRoute<…>(opts, handler)` call**; reconstruct that call instead of extracting untyped opts/handler constants that drop generics or contextual typing.
+- A convention-only `*-data.ts` stub is not a fix: move the real code or **leave the placeholder file uncreated**; never write `import "server-only"; export {}` as an empty naming token.
+- Keep the edit only when the **previously clean file stays typecheck-clean**. Otherwise roll it back and treat the change as judgment.
+
 ## Reshape pilots (X04 — physical cohesion, advisory)
 
 When `ark-check --doctor --json` carries `doctor.physicalCohesion.reshapePilot.nextPilot`,
 you may run **that one pilot** — never more:
 
-1. Read the card: `pilotTarget`, `moveSample`/`movesTotal`, `successSignal`, `killSwitch`, `doNot[]`.
+1. Read `physicalCohesion.reshapeDecisions` first. A current rejected/deferred target has no live
+   card: respect the explicit record and do not reconstruct it from raw facts. Read a live card's
+   `pilotTarget`, `decisionTarget`, `moveSample`/`movesTotal`, `successSignal`, `killSwitch`, `doNot[]`.
 2. Moves are **proposed only** — enumerate the full move set for the pilot anchor, express it as
    an architecture change map, and validate through the atomic preflight (`ark_prepare_change` /
    the write gate) **before** any file moves. A move the preflight rejects is a finding, not a
@@ -97,6 +106,10 @@ you may run **that one pilot** — never more:
 4. After the move set: full gate re-run + re-doctor. Success = the concept's cluster count drops
    and the verdict stays green; otherwise use the kill switch (revert the move set, nothing else).
 5. Re-doctor decides whether a next card exists. One pilot per loop iteration, always.
+6. If the user accepts, defers, or rejects the target, persist that explicit verdict in
+   `.ark/reshape-decisions.json` using the card's exact `decisionTarget`, a reason, and optional
+   `reviewBy`. `accepted` keeps this execution path; `deferred`/`rejected` stop repeat pressure.
+   Never infer a decision from `.ark/golden-pattern.json` prose.
 
 ## Steps