@event4u/agent-config 8.1.0 → 8.2.0

package/dist/agent-src/skills/design-tokens/scripts/tokens.ts

@@ -26,7 +26,7 @@
 import * as fs from 'node:fs';
 import * as path from 'node:path';
 import process from 'node:process';
-import { pathToFileURL } from 'node:url';
+import { fileURLToPath, pathToFileURL } from 'node:url';
 
 // ── Python-shim helpers ──────────────────────────────────────────────────
 
@@ -867,9 +867,30 @@ function _exists(p: string): boolean {
 }
 
 // `raise SystemExit(main())` — set process.exitCode, never call process.exit.
+function _isCliEntry(): boolean {
+    if (process.argv[1] === undefined) {
+        return false;
+    }
+    const argvUrl = pathToFileURL(path.resolve(process.argv[1])).href;
+    if (import.meta.url === argvUrl) {
+        return true;
+    }
+    // A symlinked invocation (e.g. via an installed `.augment/` projection,
+    // or macOS /var → /private/var temp dirs) makes the raw URLs differ:
+    // import.meta.url is the resolved real path while argv[1] keeps the
+    // symlink path. Compare realpaths so the entry guard still fires
+    // (without this the CLI silently no-ops when run through a symlink).
+    try {
+        const here = fs.realpathSync(fileURLToPath(import.meta.url));
+        const argv = fs.realpathSync(path.resolve(process.argv[1]));
+        return here === argv;
+    } catch {
+        return false;
+    }
+}
+
 const _INVOKED_DIRECTLY =
-    typeof process.argv[1] === 'string' &&
-    import.meta.url === pathToFileURL(process.argv[1]).href;
+    _isCliEntry();
 
 if (_INVOKED_DIRECTLY) {
     process.exitCode = main();

package/dist/agent-src/skills/existing-ui-audit/SKILL.md

@@ -37,7 +37,7 @@ Do NOT use when:
 
 ### 0. Inspect stack and input
 
-1. Read `state.stack.frontend` — set by `scripts/work_engine/stack/detect.py` (one of `blade-livewire-flux`, `react-shadcn`, `vue`, `plain`).
+1. Read `state.stack.frontend` — set by `scripts/work_engine/stack/detect.ts` (one of `blade-livewire-flux`, `react-shadcn`, `vue`, `plain`).
 2. Read `state.input` — the request being processed. The audit must answer: "what already exists that is similar to this request?"
 
 ### 1. Enumerate components and templates
@@ -207,7 +207,7 @@ so the import path is uniform.
 
 ## Gotcha
 
-- The model tends to skip the audit and start designing straight from the request — the dispatcher gate at `directives/ui/audit.py` enforces "no design without audit findings". Never treat this skill as optional for non-trivial UI.
+- The model tends to skip the audit and start designing straight from the request — the dispatcher gate at `directives/ui/audit.ts` enforces "no design without audit findings". Never treat this skill as optional for non-trivial UI.
 - The model tends to misidentify a single Tailwind utility as a "design token" — tokens come from the config or `:root`, not from class strings in templates.
 - Don't assume a Radix-only `package.json` means shadcn — shadcn requires `components.json` at repo root.
 - `state.ui_audit.shadcn_inventory.version` is often missing; the shadcn CLI does not always pin itself in `package.json`. Record `null` rather than guessing.
@@ -227,7 +227,7 @@ consistency) or introduce a corrective direction change.
 
 ## Do NOT
 
-- Do NOT advance to `directives/ui/design.py` or `apply.py` if `state.ui_audit` is empty.
+- Do NOT advance to `directives/ui/design.ts` or `apply.ts` if `state.ui_audit` is empty.
 - Do NOT advance to design or apply if `state.ui_audit.greenfield == true` and `state.ui_audit.greenfield_decision` is unset.
 - Do NOT silently skip the greenfield halt because "Tailwind has defaults" — the user picks the path explicitly.
 - Do NOT write paths outside the project root into the inventory.

package/dist/agent-src/skills/fe-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: medium
 name: fe-design
-description: "Reference for frontend-design heuristics — component architecture, layout patterns, form/table design, responsive strategy, a11y, UX principles. Stack-agnostic; cited by directives/ui/design.py."
+description: "Reference for frontend-design heuristics — component architecture, layout patterns, form/table design, responsive strategy, a11y, UX principles. Stack-agnostic; cited by directives/ui/design.ts."
 personas:
   - frontend-engineer
 domain: engineering
@@ -21,11 +21,11 @@ own the flow.
 
 | Concern | Owner |
 |---|---|
-| Layout / states / microcopy lock | [`directives/ui/design.py`](../../templates/scripts/work_engine/directives/ui/design.py) |
-| Stack-dispatched implementation | [`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py) → `blade-ui` / `livewire` / `flux` / `react-shadcn-ui` |
+| Layout / states / microcopy lock | [`directives/ui/design.ts`](../../templates/scripts/work_engine/directives/ui/design.ts) |
+| Stack-dispatched implementation | [`directives/ui/apply.ts`](../../templates/scripts/work_engine/directives/ui/apply.ts) → `blade-ui` / `livewire` / `flux` / `react-shadcn-ui` |
 | Existing-component inventory + tokens | [`existing-ui-audit`](../existing-ui-audit/SKILL.md) (mandatory pre-step) |
 | Grounded selection (style, color tokens, typography, pattern, anti-patterns) | [`design-intelligence`](../design-intelligence/SKILL.md) — corpus-grounded; this skill stays the heuristic layer and *invokes* it |
-| Design-review polish loop | [`directives/ui/review.py`](../../templates/scripts/work_engine/directives/ui/review.py) + [`directives/ui/polish.py`](../../templates/scripts/work_engine/directives/ui/polish.py) |
+| Design-review polish loop | [`directives/ui/review.ts`](../../templates/scripts/work_engine/directives/ui/review.ts) + [`directives/ui/polish.ts`](../../templates/scripts/work_engine/directives/ui/polish.ts) |
 
 ## When to use
 
@@ -45,7 +45,7 @@ Do NOT use this skill to:
 
 ## How the directive set cites this skill
 
-`directives/ui/design.py` produces the design brief (layout, components,
+`directives/ui/design.ts` produces the design brief (layout, components,
 states, microcopy, a11y). Selection decisions (style, semantic color
 tokens, typography pairing, layout pattern, anti-patterns) come **grounded**
 from [`design-intelligence`](../design-intelligence/SKILL.md) — run its
@@ -317,7 +317,7 @@ Surface the chosen direction in the design brief as a one-line statement (e.g. `
 
 ## Procedure
 
-When `directives/ui/design.py` (or any caller) cites this skill:
+When `directives/ui/design.ts` (or any caller) cites this skill:
 
 1. **Inspect `state.ui_audit` first** — review the audit produced by [`existing-ui-audit`](../existing-ui-audit/SKILL.md); it is mandatory. Stop and request the audit if missing.
 2. **Pick the smallest matching section** — Component Architecture, Form Design, Table Design, Responsive Strategy, Accessibility, or UX Principles. Cite by H2/H3 heading, never paste the whole skill.
@@ -364,4 +364,4 @@ approach or explicitly invoke the override condition in the design brief.
 - Do NOT skip mobile viewport testing.
 - Do NOT use fixed pixel widths for responsive layouts.
 - Do NOT ignore accessibility requirements.
-- Do NOT use this skill as an executor — it is a reference cited by `directives/ui/design.py`.
+- Do NOT use this skill as an executor — it is a reference cited by `directives/ui/design.ts`.

package/dist/agent-src/skills/finishing-a-development-branch/SKILL.md

@@ -60,8 +60,13 @@ or [`fix-pr-comments`](../../commands/fix-pr-comments.md) instead.
 
 ### 2. Verify readiness
 
-Run the full end-of-work gate before presenting any options — see
-[`verify-before-complete`](../verify-before-complete/SKILL.md):
+Run the end-of-work gate before presenting any options — see
+[`verify-before-complete`](../verify-before-complete/SKILL.md).
+Steps 1–3 run only when `quality.local_auto_run: true`; under the
+default (`false` / missing) skip them without asking — user runs
+quality tools manually, remote CI on the PR is the authoritative gate,
+readiness report says *"quality gates delegated to remote CI"* instead
+of claiming them green:
 
 1. Targeted tests green
 2. Full test suite green
@@ -69,8 +74,8 @@ Run the full end-of-work gate before presenting any options — see
 4. `git status` clean — nothing unstaged, no stray files
 5. Branch is pushed or explicitly marked local-only
 
-If any step fails → **stop**. Report the failure, do not present ship
-options. Fixing the failure comes first.
+If any executed step fails → **stop**. Report the failure, do not
+present ship options. Fixing the failure comes first.
 
 ### 3. Determine the base branch
 
@@ -236,6 +241,8 @@ After the chosen option completes, report:
 Before reporting "done" after this skill runs:
 
 * [ ] Full gate (tests + quality pipeline) verified green in this turn
+      when `quality.local_auto_run: true` — under the default `false`
+      the report states "quality gates delegated to remote CI" instead
 * [ ] Base branch determined and confirmed with the user when ambiguous
 * [ ] Exactly four numbered options were presented, no narration added
 * [ ] User's choice recorded literally, not reinterpreted

package/dist/agent-src/skills/flux/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: medium
 name: flux
-description: "Use when the project uses `livewire/flux` — dispatched by `directives/ui/{apply,review,polish}.py`. Covers Flux components, slots, variants, and form primitives."
+description: "Use when the project uses `livewire/flux` — dispatched by `directives/ui/{apply,review,polish}.ts`. Covers Flux components, slots, variants, and form primitives."
 domain: engineering
 workspaces:
   - engineering
@@ -17,7 +17,8 @@ install:
 # flux
 
 > **Grounded stack guidance:** Tailwind-layer Do/Don't + docs URLs via
-> `ground.py search --manifest <skills-root>/design-intelligence/data/manifest.json
+> `./scripts-run <skills-root>/corpus-grounding/scripts/ground search
+> --manifest <skills-root>/design-intelligence/data/manifest.json
 > --stack html-tailwind "<topic>"`. See
 > [`design-intelligence`](../design-intelligence/SKILL.md).
 
@@ -25,15 +26,15 @@ install:
 
 `flux` is the **primitive-library executor** for projects on the
 Livewire + Flux stack. It is invoked by
-[`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py)
-once the design brief is locked, and revisited by `review.py` /
-`polish.py` during the design-review loop. It does **not** own the
+[`directives/ui/apply.ts`](../../templates/scripts/work_engine/directives/ui/apply.ts)
+once the design brief is locked, and revisited by `review.ts` /
+`polish.ts` during the design-review loop. It does **not** own the
 flow, does **not** drive the audit, and does **not** lock the design.
 
 | Concern | Owner |
 |---|---|
 | Audit + token inventory (mandatory pre-step) | [`existing-ui-audit`](../existing-ui-audit/SKILL.md) |
-| Design brief (layout / states / microcopy) | [`directives/ui/design.py`](../../templates/scripts/work_engine/directives/ui/design.py) |
+| Design brief (layout / states / microcopy) | [`directives/ui/design.ts`](../../templates/scripts/work_engine/directives/ui/design.ts) |
 | Universal design heuristics | [`fe-design`](../fe-design/SKILL.md) |
 | Component logic / state / actions | [`livewire`](../livewire/SKILL.md) |
 | Static Blade partials | [`blade-ui`](../blade-ui/SKILL.md) |
@@ -42,7 +43,7 @@ flow, does **not** drive the audit, and does **not** lock the design.
 
 Cite this skill when:
 
-- The project depends on `livewire/flux` and `directives/ui/apply.py` dispatches Flux primitives
+- The project depends on `livewire/flux` and `directives/ui/apply.ts` dispatches Flux primitives
 - Building forms, modals, dropdowns, toasts, or other standard UI elements that Flux already provides
 
 Do NOT use when:
@@ -84,8 +85,8 @@ Do NOT use when:
 
 ### Review pass — a11y findings + preview envelope
 
-When this skill is dispatched by `directives/ui/review.py` (test slot)
-or `directives/ui/polish.py` (verify slot) — i.e. a review/polish run,
+When this skill is dispatched by `directives/ui/review.ts` (test slot)
+or `directives/ui/polish.ts` (verify slot) — i.e. a review/polish run,
 not the initial apply — it also emits:
 
 - `state.ui_review.a11y` — `{violations: [{rule, selector, severity}, ...],

package/dist/agent-src/skills/git-workflow/SKILL.md

@@ -64,10 +64,9 @@ gh pr view <number> --json number,state,mergeStateStatus,mergedAt,baseRefName
 
 ## Procedure: Before opening a PR
 
-1. Run the project's quality pipeline (see `quality-tools` skill) — typically: type-checker → auto-fixer → linter → type-checker.
-2. Run the project's test command — detect from manifest: `php artisan test` / `vendor/bin/phpunit` (PHP), `npm test` / `pnpm test` / `vitest` / `jest` (JS-TS), `pytest` (Python), `cargo test` (Rust), `go test ./...` (Go).
-3. Rebase onto `main`.
-4. Fill in PR template completely.
+1. Quality pipeline + tests — only when `quality.local_auto_run: true` (see [`quality-tools` § Execution policy](../quality-tools/SKILL.md)): type-checker → auto-fixer → linter → type-checker, then the project's test command (detect from manifest: `php artisan test` / `vendor/bin/phpunit` (PHP), `npm test` / `pnpm test` / `vitest` / `jest` (JS-TS), `pytest` (Python), `cargo test` (Rust), `go test ./...` (Go)). Under the default (`false` / missing) skip both — remote CI on the PR is the gate; say so instead of claiming they passed.
+2. Rebase onto `main`.
+3. Fill in PR template completely.
 
 ## Procedure: Finish a branch
 
@@ -83,7 +82,7 @@ Work complete. What would you like to do?
 
 ### Option 1: Push and create PR
 
-1. Run quality pipeline + tests.
+1. Run quality pipeline + tests (only when `quality.local_auto_run: true`; default `false` → skip, remote CI is the gate).
 2. `git push -u origin <branch>`.
 3. `gh pr create` using PR template.
 

package/dist/agent-src/skills/guideline-writing/SKILL.md

@@ -123,7 +123,7 @@ Above the split signal, break by sub-topic into sibling files in the same folder
 
 1. Complete guideline at `docs/guidelines/{topic}/{name}.md`
 2. At least one skill or rule linking to it
-3. Linter + `check_references.py` clean
+3. Linter + `check_references.ts` clean
 4. `bash scripts/condense.sh --sync` confirmation
 
 ## Gotchas
@@ -167,7 +167,7 @@ to every guideline you author.
 ## Cloud Behavior
 
 On cloud surfaces (Claude.ai Web, Skills API) the package's
-`scripts/check_references.py`, `scripts/skill_linter.py`, and `task`
+`scripts/check_references.ts`, `scripts/skill_linter.ts`, and `task`
 runner are not reachable. The skill still applies — with prose-only
 validation:
 

package/dist/agent-src/skills/learning-to-rule-or-skill/SKILL.md

@@ -29,7 +29,7 @@ Use this skill when:
 * Mining the audit log (`agents/runtime/state/audit/<YYYY-MM>.jsonl`,
   [`audit-log-v1`](../../../docs/contracts/audit-log-v1.md)) surfaced
   a repeated phase pattern via
-  [`extract_audit_patterns.py`](../../../scripts/extract_audit_patterns.py)
+  [`extract_audit_patterns.ts`](../../../scripts/extract_audit_patterns.ts)
   — the pattern's `count` ≥ 2 already satisfies the repetition gate
 
 Do not use this skill when:
@@ -334,7 +334,7 @@ the gap is documented in its skill body.
 ## Audit-derived learnings (optional source)
 
 When the input is a pattern surfaced by
-[`extract_audit_patterns.py`](../../../scripts/extract_audit_patterns.py)
+[`extract_audit_patterns.ts`](../../../scripts/extract_audit_patterns.ts)
 mining `agents/runtime/state/audit/<YYYY-MM>.jsonl`
 ([`audit-log-v1`](../../../docs/contracts/audit-log-v1.md)):
 

package/dist/agent-src/skills/livewire/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: medium
 name: livewire
-description: "Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.py`. Covers reactive state, events, lifecycle hooks, and component/view separation."
+description: "Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.ts`. Covers reactive state, events, lifecycle hooks, and component/view separation."
 domain: engineering
 workspaces:
   - engineering
@@ -17,22 +17,23 @@ install:
 # livewire
 
 > **Grounded stack guidance:** pull idiomatic Blade/UI Do/Don't + docs URLs
-> via `ground.py search --manifest <skills-root>/design-intelligence/data/manifest.json
+> via `./scripts-run <skills-root>/corpus-grounding/scripts/ground search
+> --manifest <skills-root>/design-intelligence/data/manifest.json
 > --stack laravel "<topic>"` (UI-scoped corpus). See
 > [`design-intelligence`](../design-intelligence/SKILL.md).
 
 ## Positioning — dispatched, not standalone
 
 `livewire` is the **apply-step executor** for the Livewire stack. It is
-invoked by [`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py)
-once the design brief is locked, and revisited by `review.py` /
-`polish.py` during the design-review loop. It does **not** own the
+invoked by [`directives/ui/apply.ts`](../../templates/scripts/work_engine/directives/ui/apply.ts)
+once the design brief is locked, and revisited by `review.ts` /
+`polish.ts` during the design-review loop. It does **not** own the
 flow, does **not** drive the audit, and does **not** lock the design.
 
 | Concern | Owner |
 |---|---|
 | Audit + token inventory (mandatory pre-step) | [`existing-ui-audit`](../existing-ui-audit/SKILL.md) |
-| Design brief (layout / states / microcopy) | [`directives/ui/design.py`](../../templates/scripts/work_engine/directives/ui/design.py) |
+| Design brief (layout / states / microcopy) | [`directives/ui/design.ts`](../../templates/scripts/work_engine/directives/ui/design.ts) |
 | Universal design heuristics | [`fe-design`](../fe-design/SKILL.md) |
 | Static Blade partials inside the view | [`blade-ui`](../blade-ui/SKILL.md) |
 | Flux primitives inside the view | [`flux`](../flux/SKILL.md) |
@@ -41,7 +42,7 @@ flow, does **not** drive the audit, and does **not** lock the design.
 
 Cite this skill when:
 
-- `state.stack.frontend == "livewire"` and `directives/ui/apply.py` dispatches to this skill
+- `state.stack.frontend == "livewire"` and `directives/ui/apply.ts` dispatches to this skill
 - Editing or creating Livewire components — reactive state, forms, tables, real-time updates
 
 Do NOT use when:
@@ -96,8 +97,8 @@ Do NOT use when:
 
 ### Review pass — a11y findings + preview envelope
 
-When this skill is dispatched by `directives/ui/review.py` (test slot)
-or `directives/ui/polish.py` (verify slot) — i.e. a review/polish run,
+When this skill is dispatched by `directives/ui/review.ts` (test slot)
+or `directives/ui/polish.ts` (verify slot) — i.e. a review/polish run,
 not the initial apply — it also emits:
 
 - `state.ui_review.a11y` — `{violations: [{rule, selector, severity}, ...],

package/dist/agent-src/skills/memory-consolidation/SKILL.md

@@ -234,7 +234,7 @@ The miner is host-agnostic by design. A `TranscriptAdapter` for host
   `.agent-settings.yml` under `memory.redact_patterns`.
 
 The GATHER implementation lives in the single mining command
-`/memory:mine-session` (`scripts/mine_session.py`). It reads the
+`/memory:mine-session` (`scripts/mine_session.ts`). It reads the
 **cross-host** chat-history JSONL log (`agents/runtime/.agent-chat-history`,
 written by platform hooks on every host), falling back to the per-host
 Claude-Code transcript when the log is absent. `--mode=[signals|proposals|both]`
@@ -299,7 +299,7 @@ in-task notes stay in-task and are discarded with the task.
 - A fact tagged `gotcha + invariant` lands in the `gotcha` JSONL
   (primary tag); the promoter reads tag intersection to decide the
   curated YAML target.
-- Date-discipline: the `check_memory.py` linter rejects
+- Date-discipline: the `check_memory.ts` linter rejects
   `yesterday|today|tomorrow|last/next/this week|month|year` in curated
   YAML without an `YYYY-MM-DD` anchor within ±20 chars. Re-anchor
   before commit.

package/dist/agent-src/skills/module-detect-on-the-fly/SKILL.md

@@ -32,14 +32,14 @@ the config — once, without nagging.
 1. `modules.enabled` is `true` (already configured — use `module-management`).
 2. `modules.detection_acknowledged` is `true` (user already answered).
 3. The path matches a `_NOISE_SEGMENTS` entry (`vendor`, `node_modules`,
-   `dist`, `build`, etc.) — see `scripts/_lib/module_detection.py`.
+   `dist`, `build`, etc.) — see `scripts/_lib/module_detection.ts`.
 
 Confirm both flags via `get_modules_config()` before running detection.
 
 ## Procedure
 
 1. **Detect** — call `detect_module_roots(project_root)` from
-   `scripts/_lib/module_detection.py`. Returns a list of
+   `scripts/_lib/module_detection.ts`. Returns a list of
    `ModuleCandidate` ordered `high → medium` confidence.
 2. **Bail early** — if the list is empty OR every candidate has
    `confidence: "medium"` AND no candidate matches the path the agent
@@ -65,7 +65,7 @@ Confirm both flags via `get_modules_config()` before running detection.
 
 4. **Persist the choice**:
 
-   - **Option 1** — build the payload (matches `propose_modules_config.py
+   - **Option 1** — build the payload (matches `propose_modules_config.ts
      --json` shape, includes `detection_acknowledged: true`), pipe into
      `./scripts-run src/scripts/apply_modules_config --project <root>`.
    - **Option 2** — run `./scripts-run src/scripts/apply_modules_config
@@ -122,9 +122,9 @@ Confirm both flags via `get_modules_config()` before running detection.
 ## See also
 
 - `module-management` — the active skill once modules are configured.
-- `scripts/_lib/module_detection.py` — `detect_module_roots()` +
+- `scripts/_lib/module_detection.ts` — `detect_module_roots()` +
   `is_module_like_path()` helpers.
-- `scripts/apply_modules_config.py` — persistence with
+- `scripts/apply_modules_config.ts` — persistence with
   `--acknowledge-only` for option 2.
 - `commands/agents/init.md` — the explicit re-entry point if the user
   wants to revisit detection later.

package/dist/agent-src/skills/module-management/SKILL.md

@@ -43,7 +43,7 @@ stack-native auto-loading, or duplicating existing modules.
 ## Procedure: Work with modules
 
 1. Read `modules:` block from `.agent-project-settings.yml` via the
-   loader (`get_modules_config()` in `scripts/_lib/agent_settings.py`).
+   loader (`get_modules_config()` in `scripts/_lib/agent_settings.ts`).
 2. For each path in `modules.root_paths`, read the module's `README.md`
    (or `package.json` / `pyproject.toml` description) for purpose.
 3. If module-level agent docs exist under
@@ -58,7 +58,7 @@ When `modules.enabled` is unset / false, the skill consults the
 auto-detection table in
 [`/module explore` Step 1](../../commands/module/explore.md) — same six
 stack shapes, fallback only. The skill never writes the `modules:`
-block automatically; that is `propose_modules_config.py` plus user
+block automatically; that is `propose_modules_config.ts` plus user
 confirmation per
 [`/agents init`](../../commands/agents/init.md) Step 7.
 

package/dist/agent-src/skills/prediction-pool-optimizer/SKILL.md

@@ -62,7 +62,7 @@ more. **Always optimize the pool's points, never the truth of the match.**
   from real markets **or** the executed Poisson helper — never a claimed
   "I ran 10,000 simulations".
 - **Scorelines computed, not guessed.** EV-max tip per match from the executed
-  grid optimiser (`score_ev.py`, step 4a), never the eye. A 3:2 / 4:1 / 1:4 in
+  grid optimiser (`score_ev.ts`, step 4a), never the eye. A 3:2 / 4:1 / 1:4 in
   the output = signature of a skipped computation.
 - **One-sentence justification** per answer. Short.
 
@@ -265,16 +265,16 @@ gate — the skill never enters or submits anything.
   base from a sharp-weighted consensus across several; an outlier is a flag to
   investigate, not a number to copy.
 - **Tipping the modal result, not the EV-maximal one.** The single most likely
-  scoreline rarely maximizes partial points — run `score_ev.py` across the
+  scoreline rarely maximizes partial points — run `score_ev.ts` across the
   result grid, don't eyeball the favourite.
 - **Hand-picking a high scoreline.** 3:2 / 4:1 / 1:4 never EV-max under partial
   points — moderate favourites peak at 1:0 / 2:0 / 2:1. A high tip = grid
-  skipped; run `score_ev.py`.
+  skipped; run `score_ev.ts`.
 - **Under-tipping draws.** A correct draw banks the goal-difference tier on
   every draw scoreline, so a close match can want 1:1 (or 0:0). Let the grid
   decide; the eye tips too few draws.
 - **"Rough Kelly" variance for a large pool.** Don't guess deviation amount —
-  run `pool_winsim.py`; returns the exact flips that raise P(finish 1st) most
+  run `pool_winsim.ts`; returns the exact flips that raise P(finish 1st) most
   per unit EV given up.
 - **Forgetting to de-vig.** Raw bookmaker odds sum to >100%; treating them as
   probabilities inflates the favourite. Remove the margin **per book** before
@@ -282,18 +282,18 @@ gate — the skill never enters or submits anything.
 - **Contrarian under fixed points.** Deviating "to stand out" only helps under
   quote/rarity rules or a win-a-large-pool goal — otherwise it burns EV.
 - **Claimed-but-unrun simulation.** "I ran 10,000 tournaments" without
-  executing `poisson_sim.py` is hallucinated — run the code or use outright odds.
+  executing `poisson_sim.ts` is hallucinated — run the code or use outright odds.
 
 ## Do NOT
 
 - Leave any open pool question (bonus / award / special) unanswered.
 - Build the base from a single bookmaker, or skip de-vigging before aggregating.
 - Tip the most likely result instead of the EV-maximal one.
-- Hand-pick a scoreline instead of running `score_ev.py` — never emit a
+- Hand-pick a scoreline instead of running `score_ev.ts` — never emit a
   3:2 / 4:1 / 1:4 tip, never EV-max under partial points.
 - Go contrarian under standard fixed-point scoring with a "place well" goal.
-- Guess large-pool variance ("rough Kelly") instead of running `pool_winsim.py`.
-- Report Monte-Carlo numbers without running `poisson_sim.py` / `pool_winsim.py`.
+- Guess large-pool variance ("rough Kelly") instead of running `pool_winsim.ts`.
+- Report Monte-Carlo numbers without running `poisson_sim.ts` / `pool_winsim.ts`.
 - Treat raw odds as probabilities without removing the vig.
 - Give betting or financial advice — this optimizes a game; the human submits.
 
@@ -306,9 +306,9 @@ gate — the skill never enters or submits anything.
   question taxonomy with a per-type method.
 - [`reference/ev-fixtures.md`](reference/ev-fixtures.md) — known-good
   rules+odds → EV examples.
-- [`scripts/prediction-pool/score_ev.py`](../../../../scripts/prediction-pool/score_ev.py) —
+- [`scripts/prediction-pool/score_ev.ts`](../../../../scripts/prediction-pool/score_ev.ts) —
   executed exact-score EV optimiser (step 4a; λ + rule → EV-max scoreline).
-- [`scripts/prediction-pool/pool_winsim.py`](../../../../scripts/prediction-pool/pool_winsim.py) —
+- [`scripts/prediction-pool/pool_winsim.ts`](../../../../scripts/prediction-pool/pool_winsim.ts) —
   executed field model + P(finish 1st) simulator and flip-finder (step 4b).
-- [`scripts/prediction-pool/poisson_sim.py`](../../../../scripts/prediction-pool/poisson_sim.py) —
+- [`scripts/prediction-pool/poisson_sim.ts`](../../../../scripts/prediction-pool/poisson_sim.ts) —
   the executed tournament simulator (step 5).

package/dist/agent-src/skills/prediction-pool-optimizer/reference/ev-fixtures.md

@@ -17,7 +17,7 @@ No quote rule. No strategy limit. Goal: place well.
 
 **Match (football):** Poisson on market xG ≈ 1.7 : 0.8.
 
-**Script-verified** (`score_ev.py --lh 1.7 --la 0.8 --exact 4 --diff 3 --tendency 2`):
+**Script-verified** (`score_ev.ts --lh 1.7 --la 0.8 --exact 4 --diff 3 --tendency 2`):
 
 ```
 EV-max tip : 1:0  (EV 1.574)
@@ -65,7 +65,7 @@ Away 22%.
 
 **Reasoning:** N ≥ 100 and you behind → pure EV converges with the field, can't
 create the gap; target is **P(finish 1st)**, not E(points). Don't guess the
-variance: run `pool_winsim.py` with the pool's `N` and your `my_lead`. Shows
+variance: run `pool_winsim.ts` with the pool's `N` and your `my_lead`. Shows
 P(win) collapsing under EV-max-everywhere, returns the **specific flips**
 (higher-variance scorelines on high-consensus matches) that raise P(win) most
 per unit EV given up.
@@ -132,7 +132,7 @@ medium.) **Not** team B — the modal-player trap.
 
 **Rule:** kicktipp 2 / 3 / 5 — tendency = 2, goal-difference = 3, exact = 5.
 
-**Matches (script-verified, `score_ev.py … --tendency 2 --diff 3 --exact 5`):**
+**Matches (script-verified, `score_ev.ts … --tendency 2 --diff 3 --exact 5`):**
 
 | Match (λ) | EV-max | a high tip's EV | verdict |
 |---|---|---|---|
@@ -148,7 +148,7 @@ EV-max.** Adding goals — especially the underdog's — only shrinks the hit
 probability without protecting the diff/tendency points.
 
 **Known-good behaviour:** any 3:2 / 4:x / x:4 tip in the run → the grid wasn't
-run; `score_ev.py` is the gate. (Risk: low; correctness fixture, not strategy.)
+run; `score_ev.ts` is the gate. (Risk: low; correctness fixture, not strategy.)
 
 ---
 
@@ -156,7 +156,7 @@ run; `score_ev.py` is the gate. (Risk: low; correctness fixture, not strategy.)
 
 **Rule:** kicktipp 2 / 3 / 5 (as Fixture 7).
 
-**Matches (script-verified, `score_ev.py … --tendency 2 --diff 3 --exact 5`):**
+**Matches (script-verified, `score_ev.ts … --tendency 2 --diff 3 --exact 5`):**
 
 ```
 λ 1.0:1.0  ->  EV-max 0:0 (1.196), 1:1 tied (1.196)   # a draw IS the optimum
@@ -171,5 +171,5 @@ As λ rises past ~1.1 a one-goal win edges ahead, but the draw stays in the top
 tips. Grid surfaces this; intuition suppresses it.
 
 **Known-good behaviour:** a tip set with **near-zero draws across many
-low-scoring even matches** is a red flag — re-run `score_ev.py`, let the grid
+low-scoring even matches** is a red flag — re-run `score_ev.ts`, let the grid
 decide, don't default every close game to 1:0.

package/dist/agent-src/skills/prediction-pool-optimizer/reference/odds-and-bonus.md

@@ -86,7 +86,7 @@ does. Optimize each on expected points under its point weight.
 
 | Question type | Example | Method |
 |---|---|---|
-| **Outright winner** | "Who wins the tournament?" | Outright "to win" market, consensus per A; or `poisson_sim.py` `title_pct`. EV-max under the question's points. |
+| **Outright winner** | "Who wins the tournament?" | Outright "to win" market, consensus per A; or `poisson_sim.ts` `title_pct`. EV-max under the question's points. |
 | **Group / stage** | "Who wins group X?", "Who advances?" | "To win group" / "to qualify" markets; or `advance_pct` from the simulator. |
 | **Finalists / matchup** | "Who reaches the final?" | "To reach final" market per team; simulator pairing is approximate — prefer the market. |
 | **Top scorer (player)** | "Tournament top scorer?" | "Top goalscorer" outright market, consensus per A; EV-max player (favourite unless rarity scoring rewards a longer shot). |

package/dist/agent-src/skills/premortem/SKILL.md

@@ -109,7 +109,7 @@ If the analysis surfaces a pattern worth preserving for future decisions:
   not a prediction; label scenarios as prospective.
 - Do NOT auto-promote memory candidates — `/memory propose` is the intake;
   `/memory promote` requires explicit human action and passes
-  `check_memory_proposal.py`.
+  `check_memory_proposal.ts`.
 
 ## Gotchas
 

package/dist/agent-src/skills/project-docs/SKILL.md

@@ -79,7 +79,7 @@ regulations, workflows, and edge cases that the agent needs to understand the pr
 3. **List `agents/reference/docs/`** — read detail docs for the specific topic you're working on.
 4. **Check module docs** — if working in a module, resolve `{module_root}` from
    `modules.root_paths` and `{agent_folder}` from `modules.agent_folder` (see
-   `scripts/_lib/agent_settings.py::enumerate_modules()`), then check:
+   `scripts/_lib/agent_settings.ts::enumerate_modules()`), then check:
    - `{module_root}/{Module}/{agent_folder}/` — module-specific docs
    - `{module_root}/{Module}/{agent_folder}/settings/contexts/` — module-specific contexts (if exists)
    - `{module_root}/{Module}/{agent_folder}/settings/contexts/domain/` — module-specific domain knowledge (if exists)

package/dist/agent-src/skills/quality-tools/SKILL.md

@@ -23,6 +23,30 @@ Use this skill whenever running or configuring code quality tools:
 - **PHP**: PHPStan (static analysis), Rector (automated refactoring), ECS (coding standards)
 - **JS/TS**: Biome (linting + formatting), TypeScript compiler (type checking), Jest/Vitest (tests)
 
+## Execution policy — on demand only, never proactive
+
+```
+NEVER RUN QUALITY TOOLS PROACTIVELY WHEN quality.local_auto_run IS
+false OR MISSING (THE DEFAULT). DO NOT ASK WHETHER TO RUN THEM.
+THE USER RUNS THEM MANUALLY. REMOTE CI IS THE AUTHORITATIVE GATE.
+```
+
+Toolchains differ per language and project, often unknown to the agent —
+discovery + execution burns time and tokens. Under the default, exactly
+three triggers justify running a quality tool:
+
+1. **Explicit ask this turn** — user says so or invokes `/quality-fix`.
+2. **Concrete CI failure** — remote pipeline reports a failing check;
+   run exactly that failing check to reproduce and fix (`/fix:ci` is
+   the canonical flow).
+3. **New-gate carve-out** — change itself introduces a NEW CI gate,
+   smoke test, or test file; must run once locally to be proven.
+
+`quality.local_auto_run: true` restores legacy autonomous behaviour
+(run pipeline when work is ready for verification). When runs are
+suppressed, completion message says *"quality gates delegated to
+remote CI"* — never that the tools passed.
+
 ## Language detection
 
 Detect which tools to run based on **what files were changed**:
@@ -37,9 +61,9 @@ If both PHP and JS/TS files changed → run **both** pipelines.
 
 ## Related rules and guidelines
 
-- `verify-before-complete` rule — timing: run quality tools ONCE at the end, not after each edit
+- `verify-before-complete` rule — no pass claims without fresh output; suppressed runs surfaced as "delegated to remote CI", never claimed
 - `php-coding` rule → PHPStan section — inline ignores, PHPDoc rules
-- `verify-before-complete` rule — must run quality checks before claiming work is done
+- `contexts/execution/verification-mechanics.md` — Gate zero (`local_auto_run`) + timing when `true` (quality tools ONCE at the end, not after each edit)
 - [`testing-anti-patterns`](../testing-anti-patterns/SKILL.md) and
   [`process-anti-patterns.md`](../testing-anti-patterns/process-anti-patterns.md) —
   test-side rationalizations these tools cannot catch (e.g. "CI is red,