@event4u/agent-config 8.13.0 → 9.0.0

package/dist/agent-src/skills/docx-authoring/SKILL.md

@@ -0,0 +1,102 @@
+---
+model_tier: medium
+name: docx-authoring
+description: "Use when generating or editing a Word .docx — create, fill a template, or edit body XML via a consumer library; round-trip validated. Triggers on 'generate a docx', 'fill this Word template'."
+status: active
+tier: senior
+domain: process
+compatibility: "Requires a consumer-installed OOXML library (python-docx for create/fill; a zip+xml toolchain for the unpack→edit→pack path). No LibreOffice/soffice dependency — that surface is gated (see pptx, road-to-ecosystem-harvest-document-skills Phase 2). Ships zero runtime in this package."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+---
+
+# docx-authoring
+
+Wing-1 engineering skill for **writing** Word documents — the generation half of
+the read→write cycle whose read side is [`markitdown`](../markitdown/SKILL.md).
+Ships zero runtime in this package: the agent drives a library the consumer
+already has (python-docx, or a zip+XML toolchain), exactly as `markitdown` wraps
+a consumer-installed converter. Re-implements the **pattern**, never any
+proprietary source.
+
+## When to use
+
+- "Generate a .docx report / letter / contract from this content."
+- "Fill this Word template with these values."
+- "Edit the body of this .docx" (a heading, a table cell, a style).
+
+Do NOT use for: reading a docx → Markdown (that is `markitdown`); slide decks
+(`html-deck`, or the gated pptx surface); PDFs (`pdf-tools`).
+
+## Procedure
+
+### 1. Pick the path by task
+
+| Task | Path |
+|---|---|
+| Create from scratch / structured content | Library create (python-docx `Document()`) — build paragraphs, tables, styles programmatically |
+| Fill a supplied template | Open the template, replace placeholder runs in place, save a copy — never mutate the original |
+| Surgical edit of existing body | **unpack → edit XML → pack-with-validate**: a `.docx` is a ZIP of XML; unzip, edit `word/document.xml`, re-zip preserving the archive structure |
+
+### 2. Honor the hard-won gotchas (encode as rules, not hope)
+
+- **Page size defaults to US Letter** in most libraries — set A4 explicitly when the locale needs it; never assume.
+- **Table columns need dual widths** — set BOTH the table grid width and each cell width, or renderers ignore one and collapse the layout.
+- **No Unicode bullet glyphs** as literal characters (`•`, `‣`) — use the list-style paragraph, or the document loses its list semantics and screen readers skip it.
+- **Runs, not paragraphs, carry formatting** — a placeholder that spans two runs will not match a naive whole-paragraph replace; split/merge runs first.
+
+### 3. Validate — round-trip, do not trust the write
+
+1. Re-open the generated file with the SAME library; assert it parses (a corrupt ZIP or malformed XML throws here).
+2. Read back one written value (a heading text, a table cell) and assert it equals what was written.
+3. For the unpack→pack path: confirm the archive still contains `[Content_Types].xml` and `word/document.xml` (dropping either produces a file Word refuses to open).
+
+## Output format
+
+1. The generated/edited `.docx` path.
+2. The validation result: parses ✅, read-back value matched ✅, required parts present ✅.
+3. Any gotcha that applied (e.g. "set A4 explicitly; template used Letter").
+
+## Gotcha
+
+The most common silent failure is a file that **saves without error but Word
+refuses to open**: an unpack→pack cycle that re-zipped with a directory entry,
+wrong compression, or a dropped `[Content_Types].xml`. The round-trip re-open in
+step 3 is the only check that catches it — a green "file written" line does not.
+
+- **Silent corruption:** an unpack→pack cycle re-zipped with a directory entry or a dropped `[Content_Types].xml` → saves fine, Word shows "file is corrupt". Only the round-trip re-open catches it.
+
+## Do NOT
+
+- Do NOT bundle or ship a Python toolkit in this package — drive the consumer's library (zero-runtime posture, like `markitdown`).
+- Do NOT mutate a supplied template in place — always write a copy.
+- Do NOT claim success on "file written"; claim it only after the round-trip re-open.
+- Do NOT reach for LibreOffice/soffice — that dependency is gated (pptx surface).
+
+## Related Skills
+
+**WHEN to use this**
+
+- The target artifact is a Word `.docx` — a report, letter, contract, or a filled template.
+- A `.docx` body needs a surgical edit (heading, table cell, style) via the unpack→edit→pack path.
+
+**WHEN NOT to use this**
+
+- Reading a docx into the conversation → [`markitdown`](../markitdown/SKILL.md).
+- PDFs → [`pdf-tools`](../pdf-tools/SKILL.md); spreadsheets → [`spreadsheet-authoring`](../spreadsheet-authoring/SKILL.md); slide decks → [`html-deck`](../html-deck/SKILL.md).
+- The task needs LibreOffice-backed rendering (pptx) — that surface is gated, do not reach for it here.
+
+## When the agent should load this
+
+- "Generate a Word report from this content."
+- "Fill this .docx template with these values."
+- "Edit the heading / a table cell in this .docx."
+- "Produce a contract as a .docx."
+
+## Output
+
+1. **Generated document** — the `.docx` path. Cite as `docx-output`.
+2. **Validation receipt** — parses on re-open ✅, read-back value matched ✅, required OOXML parts present ✅. Cite as `docx-validation`.
+3. **Gotcha log** — present only when a gotcha applied (page-size override, run-split for a template placeholder). Cite as `docx-gotchas`.

package/dist/agent-src/skills/github-ci/evals/evals.json

@@ -0,0 +1,25 @@
+{
+  "skill": "github-ci",
+  "_calibration": "Seed for eval-schema v2 (ecosystem-harvest skill-quality-gates Phase 2). The requires_human scenario is skipped in CI and reported manual-pending — never a silent pass.",
+  "scenarios": [
+    {
+      "id": "fetches-real-ci-logs-not-guess",
+      "prompt": "The PR's Node Tests check is red. Diagnose why.",
+      "environment": "an open PR with a failing CI check",
+      "assertions": [
+        { "kind": "tool-choice", "must_use": ["bash"], "must_not_use": [] },
+        { "kind": "contains", "value": "log" }
+      ]
+    },
+    {
+      "id": "operator-confirms-rerun",
+      "prompt": "Re-run the failed CI job after the fix is pushed.",
+      "environment": "an open PR whose fix was just pushed",
+      "requires_human": true,
+      "human_instructions": "Confirm the agent fetched the real run id and did not fabricate a green result; verify the re-run was triggered against the actual failing job.",
+      "assertions": [
+        { "kind": "contains", "value": "run" }
+      ]
+    }
+  ]
+}

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

@@ -48,8 +48,12 @@ human voice there; don't inject personality or restructure.
    smuggled instructions. Then rewrite the visible content.
 1. **Load catalog on demand.** Read
    [`data/patterns.md`](data/patterns.md) — five pattern groups,
-   before/after pairs, false-positive guards. Don't paraphrase from
-   memory; catalog is the reference.
+   before/after pairs, false-positive guards — and
+   [`references/anti-aiisms.md`](references/anti-aiisms.md) for the
+   orthogonal **severity axis** (High / Medium / Low) + self-validation
+   thresholds. Don't paraphrase from memory; catalog is the reference.
+   Act on a single **High** tell; require a cluster (≥ 2) for **Medium**;
+   leave isolated **Low** tells alone.
 2. **Draft rewrite.** Replace tells with plain alternatives; cover
    everything the original covers (five paragraphs in → five out), preserve
    meaning, match active voice source. Voice precedence fixed:
@@ -66,6 +70,75 @@ human voice there; don't inject personality or restructure.
    `npx tsx src/scripts/detect_ai_tells.ts --stdin --fail` on final
    draft. No runtime → step-3 audit is the fallback (degrade, don't
    skip audit).
+6. **Deterministic self-check + factual-integrity guard.** Re-scan the
+   final draft against the [`anti-aiisms.md`](references/anti-aiisms.md)
+   self-validation thresholds (dash density, consecutive-staccato cap,
+   uniform-bullet run, hedge stack, stock-vocabulary density): did the
+   rewrite clear flagged tells **without introducing new ones**? Re-run
+   over already-clean prose is a **no-op**. Where the rewrite touched a
+   number, date, name, quantity, or claim, emit
+   `[VERIFY: <original> → <rewritten>]` — a humanizing pass changes *how*
+   something is said, never *what is true*; a silent factual edit is a
+   defect, not a style win. **Long-rewrite re-anchor (guards against style slippage):** before
+   finishing a long rewrite, re-state the active style ruleset (intensity
+   level + voice precedence) so late paragraphs match early ones.
+   (`context-hygiene` may later own the generic re-anchor primitive; here
+   scoped to the humanize pass.)
+
+## Intensity levels
+
+Pick the level from the request; default **balanced**. The level tunes the
+self-validation thresholds, never the guards below:
+
+- **subtle** — remove only Tier-High tells; leave register untouched.
+- **balanced** (default) — High + clustered Medium; keep the author's cadence.
+- **full** — High + Medium + over-used Low; the strongest de-slop.
+- **voice-match** — full, then conform to a supplied voice sample (§ Voice-match).
+
+**Excluded by design (do NOT build or invoke):**
+
+- **Detector-evasion / anti-detector mode** — rewriting to defeat an
+  AI-text classifier. Conflicts with the media/disclosure transparency
+  floors ([`media-governance-routing`](../../rules/media-governance-routing.md),
+  the ghostwriter disclosure footer). Goal is prose that reads human
+  because the tells are gone, never prose engineered to fool a detector.
+- **A shipped ML detector.** No runtime ML-classifier dependency
+  (no-new-runtime-dependency constraint). Deterministic
+  `detect_ai_tells.ts` is the only checker that ships. The score →
+  rewrite → re-score loop shape is kept only as an **optional
+  bring-your-own-checker** step: if the operator supplies a checker
+  command, the loop may call it with an audit trail; absent one, the
+  step-3 audit + step-6 self-check degrade gracefully. The suite never
+  ships the checker.
+
+## Voice-match — six fixed signals, not a vibe
+
+When a voice sample is supplied (`--voice`, a profile fingerprint), extract a
+small **fixed signal set** and match against it, not an impression:
+
+1. **Sentence-length rhythm** — the short/long alternation pattern.
+2. **Vocabulary register** — plain / technical / formal / colloquial.
+3. **Punctuation habits** — dash use, parentheticals, semicolons, ellipses.
+4. **Hedging density** — how often the author qualifies a claim.
+5. **Structural cadence** — paragraph length, list vs prose preference.
+6. **Idiom** — recurring phrases, era-bound references, signature asides.
+
+Two distinct voice samples produce measurably different targets on these six
+axes; matching means moving the draft toward the sample's values, never
+inventing personality the sample does not show.
+
+## Principles (non-negotiable)
+
+- **Subtract, don't add.** AI tone is a *residue to remove*, not warmth to
+  add. Adding warmth adds sycophancy — the loudest AI tell (wire to
+  [`direct-answers`](../../rules/direct-answers.md) Iron Law 1: no flattery).
+  Humanizing lowers the AI signal; never raises the agreeableness.
+- **Style and stance are separate.** A request for a humanized *voice* is
+  not a request for *agreement*. Preserve disagreement, uncertainty,
+  hedged-because-genuinely-uncertain claims, and refusals **regardless of
+  intensity level** — a pass that softens a "no" into a "maybe" has
+  corrupted the stance, not the style. When the input takes a position or
+  declines, the rewrite keeps that position or declining, in plainer words.
 
 ## Guards (non-negotiable)
 
@@ -144,4 +217,7 @@ human voice there; don't inject personality or restructure.
 
 Pattern catalog root source: Wikipedia, "Signs of AI writing" (WikiProject
 AI Cleanup) — catalog wording in `data/patterns.md` authored fresh
-for this suite.
+for this suite. Severity tiers + self-validation thresholds:
+[`references/anti-aiisms.md`](references/anti-aiisms.md). Worked fixtures
+for stance-preservation and voice-match:
+[`references/fixtures.md`](references/fixtures.md).

package/dist/agent-src/skills/humanizer/references/anti-aiisms.md

@@ -0,0 +1,112 @@
+# AI-ism severity tiers + self-validation thresholds
+
+> On-demand reference for the [`humanizer`](../SKILL.md) skill
+> (road-to-ecosystem-harvest-prose-authenticity, Source I — a prose
+> anti-slop humanizer skill; provenance in the harvest index). Loaded only
+> during an active humanize pass. Five **pattern groups** live in
+> [`../data/patterns.md`](../data/patterns.md); this file adds the
+> orthogonal **severity axis** (how reliable a tell each construction is)
+> and the **self-validation thresholds** the deterministic self-check reads.
+>
+> Every threshold here is a **default, not a suite measurement** — a
+> starting bound with its source, tunable per voice, never a validated
+> claim about human prose.
+
+## Why a severity axis (orthogonal to the group taxonomy)
+
+`patterns.md` groups tells by *kind* (content / language / style /
+communication / filler). This file grades them by *diagnostic weight* — how
+much a single occurrence tells you. Rewrite discipline is the same
+(rewrite, don't delete); the tier decides **how hard to look** and **whether
+one hit is worth acting on**. Clusters still win: two Medium tells
+co-occurring outweigh one isolated High.
+
+## Tier High — almost always a tell (act on a single occurrence)
+
+Single instance is strong evidence of machine authorship; these rarely
+survive in genuine human prose.
+
+- **Chat artifacts** in a deliverable — "I hope this helps", "Let me know
+  if…", "Would you like me to…", "Here is an overview of…". (patterns.md 4.1)
+- **Knowledge-cutoff disclaimers** — "As of my last update…", "While
+  specific details are limited…". (4.2)
+- **Sycophancy** — "Great question!", "You're absolutely right". (4.4)
+- **Negative parallelism as a reflex** — "It's not just X — it's Y", "not
+  merely a song, but a statement". (2.3)
+- **Significance inflation** — "marks a pivotal moment", "leaves an
+  indelible mark". (1.1)
+- **Aphorism formulas** — "X is the currency of Y", "X is not a tool but a
+  mirror". (3.9)
+- **Spaced double hyphens** (` -- `) — always a machine artifact. (3.1)
+
+## Tier Medium — a tell in combination (act when ≥2 co-occur)
+
+Individually defensible; a cluster of two or more is a signature.
+
+- **AI vocabulary** — delve, tapestry, showcase, testament, pivotal,
+  vibrant, intricate, seamless, underscore, ever-evolving. One is noise;
+  three in a paragraph is a confession. (2.1)
+- **Rule-of-three padding** — forced triplets. (2.4)
+- **Copula avoidance** — "serves as", "stands as", "represents a shift". (2.2)
+- **Promotional register** — "nestled", "boasts", "rich cultural heritage". (1.4)
+- **Superficial "-ing" analysis** — "…, highlighting the region's heritage". (1.3)
+- **Weasel attributions** — "experts argue", "observers have cited". (1.5)
+- **Staccato drama / manufactured punchlines** — runs of short fragments
+  engineered for quotability. (3.8)
+- **Em/en-dash density above the deliverable cap** (~2 per 500 words). (3.1)
+- **Signposting** — "let's dive in", "here's what you need to know". (5.4)
+- **Fake-candid openers** — "Honestly?", "Look,", "Here's the thing". (5.6)
+
+## Tier Low — only when over-used (never act on isolated hits)
+
+Common in ordinary human writing; a tell only at high density.
+
+- **Filler phrases** — "in order to", "due to the fact that". (5.1)
+- **Hedge stacks** — "could potentially possibly". (5.2)
+- **Mechanical boldface / bold-header vertical lists** — a tell in chat/post
+  prose; **house style in this repo's own docs** (see the scope note below). (3.2, 3.3)
+- **Title Case Headings**, **curly quotes**, **generic upbeat endings**. (3.4, 3.6, 5.3)
+- **Synonym cycling**, **false ranges**. (2.5, 2.6)
+
+## Scope note — deliverables, not repo docs
+
+This severity axis governs **deliverable prose** (posts, articles, ghostwriter
+output, on-request README sections). It does **not** apply to this repo's own
+`docs/**` reference prose: em dashes and bold inline headers are the suite's
+**intentional house style** there (council 2026-07-11, recorded on
+`detect_ai_tells.ts` and `road-to-humanized-writing`). A humanize pass never
+runs over repo documentation — see SKILL.md § When NOT to use.
+
+## Self-validation thresholds (U4 — deterministic self-check bounds)
+
+Read after a rewrite; each bound is a **default, not a suite measurement**.
+The deterministic subset is enforced by
+[`detect_ai_tells.ts`](../../../scripts/detect_ai_tells.ts) when a runtime is
+available; without one, the step-3 audit checks these by eye.
+
+| Bound | Default | Source |
+|---|---|---|
+| Em/en-dash density | ≤ ~2 per 500 words | patterns.md 3.1 (CP1 parity with design-antipatterns) |
+| Consecutive staccato fragments | ≤ 3 short declaratives in a row | patterns.md 3.8 |
+| Uniform-shape bullets | merge a run of ≥ 4 identically-shaped `- **X:** …` bullets into prose or real sentences | patterns.md 3.3 |
+| Hedge stack | ≤ 1 hedge per claim | patterns.md 5.2 |
+| Stock-vocabulary density | ≤ 2 Tier-Medium AI-vocabulary words per 100 words | patterns.md 2.1 |
+
+**Did the rewrite clear the flagged tells without introducing new ones?** A
+re-run over already-clean prose is a no-op. If a bound is intentionally
+exceeded by a voice fingerprint (a person who genuinely writes in dashes),
+the fingerprint wins and the bound is suppressed for that pass.
+
+## Factual-integrity guard (U4)
+
+Where a rewrite touches factual content — a number, date, name, quantity, or
+claim — emit a flag rather than silently altering it:
+
+```
+[VERIFY: <original span> → <rewritten span>]
+```
+
+A humanizing pass changes *how* something is said, never *what is true*. The
+flag makes any factual delta reviewable; the author confirms or reverts. A
+rewrite that would drop or alter a fact without a `[VERIFY:]` flag is a
+defect, not a style improvement.

package/dist/agent-src/skills/humanizer/references/fixtures.md

@@ -0,0 +1,70 @@
+# Humanizer worked fixtures
+
+> On-demand fixtures for the [`humanizer`](../SKILL.md) skill — the
+> behavioral cases the U2 (style/stance separation) and U5 (six-signal
+> voice-match) verify clauses reference
+> (road-to-ecosystem-harvest-prose-authenticity, Source I).
+
+## Fixture 1 — stance survives the style pass (U2)
+
+A humanize pass lowers the AI signal; it must **not** soften a refusal or a
+disagreement into agreement. Input takes a firm negative position with two
+Tier-High tells (sycophancy + chat artifact + significance inflation):
+
+**Before (AI-toned refusal):**
+
+> Great question! Unfortunately, I'm not able to merge this to `main` right
+> now — doing so would mark a pivotal moment that bypasses the review gate.
+> Let me know if you'd like me to walk through the alternatives!
+
+**After (humanized — tells gone, refusal intact):**
+
+> I can't merge this to `main` — it would skip the review gate. The
+> alternatives are to open a PR for review or to get an explicit override
+> from a maintainer.
+
+The rewrite removed the flattery, the chat artifact, and the significance
+inflation, and **kept the "no"**. A rewrite that turned this into "I could
+probably merge this if you'd like!" would have corrupted the stance — a
+defect, not a humanize. Same rule for hedged-because-genuinely-uncertain
+claims: uncertainty the author actually holds stays.
+
+## Fixture 2 — two voice samples, measurably different targets (U5)
+
+The six-signal extraction produces distinct targets for distinct samples —
+matching moves the draft toward the sample's values, never toward a generic
+"human" vibe.
+
+**Sample A — terse operator:**
+
+> Deploy failed. Rolled back. Root cause: the migration locked the orders
+> table for 40s. Fix lands tomorrow.
+
+| Signal | Sample A target |
+|---|---|
+| Sentence-length rhythm | very short, uniform (4–8 words) |
+| Vocabulary register | plain / operational |
+| Punctuation habits | periods only; no dashes, no parentheticals |
+| Hedging density | zero |
+| Structural cadence | clipped declaratives, no lists |
+| Idiom | incident-log shorthand ("root cause:", "lands") |
+
+**Sample B — discursive essayist:**
+
+> What struck me, reading the migration post-mortem again, was how ordinary
+> the failure looked in advance — a lock we'd all seen a hundred times, on a
+> table nobody thought of as hot until, suddenly, it was.
+
+| Signal | Sample B target |
+|---|---|
+| Sentence-length rhythm | long, winding; one sentence per idea |
+| Vocabulary register | reflective / literary |
+| Punctuation habits | em dashes + nested clauses (fingerprint allows dashes) |
+| Hedging density | moderate ("looked", "thought of as") |
+| Structural cadence | single flowing paragraph |
+| Idiom | narrative asides ("What struck me…") |
+
+The two targets diverge on every axis — a draft matched to A is not a draft
+matched to B. Sample B is also a case where the dash-density default is
+**suppressed**: the fingerprint genuinely writes in dashes, so the fingerprint
+wins (SKILL § voice precedence).

package/dist/agent-src/skills/judge-bug-hunter/SKILL.md

@@ -70,7 +70,13 @@ not reviewable — flag it and stop.
 - Does it introduce a new implicit assumption (ordering, timezone,
   encoding, locale)?
 
-### 4. Verdict
+### 4. False-positive gate — restate before you flag
+
+Before an issue enters the verdict, restate as one falsifiable sentence naming the concrete input or state that triggers it + wrong behavior that follows. Issue whose trigger you cannot name from the diff is not a finding — drop it (or return `revise` asking for missing context, never a speculative flag).
+
+For 🔴 findings, run devil's-advocate pass before finalizing: actively try to refute (guard upstream in same diff? caller already validates? branch unreachable for claimed input?). Models systematically overrate severity — a 🔴 that survives refutation is credible; one never challenged is noise. Reject rationalizations "it looks wrong" (pattern-recognition is not analysis) and "flag it just in case" (over-reporting erodes the verdict's trust).
+
+### 5. Verdict
 
 | Verdict  | When to return it |
 |---|---|

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

@@ -188,6 +188,16 @@ When generating Laravel code:
 - Do NOT use facades in service classes — use dependency injection.
 - Do NOT skip middleware for route groups that need authentication.
 
+## Known pitfalls
+
+| Symptom | Root cause | Fix |
+|---|---|---|
+| A list endpoint fires hundreds of queries / is slow under load | N+1: a relation is accessed inside a loop without eager loading | Eager-load with `with('relation')`; enable `Model::preventLazyLoading()` in non-prod to catch it early |
+| Config changes / new env vars have no effect in production | `config:cache` cached the old config, and `env()` returns `null` once config is cached | Read env only in `config/*`, use `config()` elsewhere; re-run `config:cache` on deploy |
+| A form field silently isn't saved | The attribute isn't in `$fillable` and mass-assignment drops it | Add it to `$fillable` (or set it explicitly); never blanket-`$guarded = []` on user input |
+| Queued jobs never run / run with stale code | No worker is running, or workers weren't restarted after a deploy so they hold the old code in memory | Run/supervise `queue:work`; `queue:restart` on every deploy |
+| Timestamps or times are off by hours | Comparing/formatting a Carbon instance without honoring `config('app.timezone')` vs the DB's UTC storage | Store UTC; convert for display; set the app timezone explicitly, don't assume server local time |
+
 ## Gotcha
 
 - `env()` only works in config files — use `config()` everywhere else.

package/dist/agent-src/skills/launch-readiness/SKILL.md

@@ -68,6 +68,41 @@ Walk the diff with the following gates:
 Cells without evidence block the launch — surface, do not
 hand-wave.
 
+### 2b. Epistemics block — the diagnostic report (contract-backed)
+
+For a consumer-facing diagnostic (not just the merge decision), emit a
+report per [`docs/contracts/prelaunch-diagnostics.md`](../../../docs/contracts/prelaunch-diagnostics.md)
+(schema: `prelaunch-report.schema.json`). Rules:
+
+- **Coverage backbone** — diagnose exactly the fixed area vocabulary
+  (`prelaunch-areas.yml`): auth · migrations · secrets · observability ·
+  rollback · agent-governance. No ad-hoc areas.
+- **Every area gets one state:** `pass` (cited evidence REQUIRED) ·
+  `finding` (IDs listed) · `unknown` (honest default — **absence of
+  findings is Unknown, never an automatic Pass**) · `not-applicable`
+  (reason required).
+- **Findings carry immutable IDs** (`AC-<AREA>-NNN`) — retitle freely,
+  never re-assign; the ID is the diff key across runs.
+- **Verdict:** any open P0 → NOT ready, regardless of every other area;
+  any open P1 or a launch-gate area not at pass/N-A → NOT ready. Ready is
+  the residual state, never the default.
+- **Questions section** — list the questions that would change the
+  diagnosis; the next run converts them into evidence or findings.
+- Validate + verdict via
+  `./scripts-run src/scripts/prelaunch_diagnostics validate <report.json>`;
+  regression-gate against the committed baseline via
+  `… diff <baseline> <current> --ci` (contract § 4–6).
+
+### 2c. Fix loop (approval-gated, read-only diagnostic)
+
+Rank open findings by severity, then launch-gate membership; propose the
+**safest first approval batch** (reversible, small blast radius — explicitly
+not the full backlog). Status vocabulary per finding: `open · fixed ·
+accepted-risk · deferred-with-reason · suppressed-with-evidence ·
+not-applicable` — everything except open/fixed carries a reason. Rescore
+whenever evidence changes. The diagnostic itself never mutates the project;
+fixes flow through the normal approval-gated engines.
+
 ### 3. Plan the rollout
 
 - **Mechanism** — flag, canary cohort, blue-green, immediate.

package/dist/agent-src/skills/merge-conflicts/SKILL.md

@@ -43,6 +43,27 @@ For each conflicted file:
 3. **Understand "theirs"** — what does the incoming branch intend?
 4. **Check if both changes are needed** — often both sides added different things.
 
+### 2b. Merge Resolution Plan — mandatory before touching a conflict
+
+After reading both sides, write the plan; under `autonomous-execution` the
+approval gate applies (a standing mandate states the plan and proceeds; an
+interactive session surfaces it and waits):
+
+```
+## Merge Resolution Plan
+- Conflicts: {N files / M hunks}
+- Execution order: {dependency leaves first — a file nothing else imports
+  resolves before the files that import it}
+| file | strategy | rationale |
+|---|---|---|
+- Decisions needed from the user: {semantic/deleted-modified items, or none}
+- Validation: {targeted checks to run after resolution}
+```
+
+**Backup before resolution:** every deleted-modified file is copied to a
+temp path (`$TMPDIR/merge-backup-<ts>/<file>`) and the path noted in the
+plan BEFORE any resolution touches it.
+
 ### 3. Resolution strategies
 
 | Situation | Strategy |
@@ -54,6 +75,8 @@ For each conflicted file:
 | Migration conflicts (same timestamp) | **Rename** — adjust timestamp to avoid collision |
 | Auto-generated files (OpenAPI spec, baselines) | **Regenerate** — resolve source, then regenerate the output |
 | Formatting-only conflicts | **Accept either** — then run quality tools to normalize |
+| Import-block conflicts (both sides added imports) | **Keep both** — union the imports, drop duplicates, let the linter order them |
+| Binary files (images, archives, compiled assets) | **Pick one side whole** — never splice; regenerate from source if generated, else ask which side wins |
 
 ### 4. File-type specific rules (stack-aware)
 
@@ -104,6 +127,13 @@ For each conflicted file:
 - Import statement ordering
 - Formatting-only differences
 
+### 5b. Resolution log — one line per conflict
+
+Every resolved conflict gets a one-line explanation ("kept both — additive
+imports"; "took theirs — lockfile regenerated") collected into the final
+summary: the auditable log the reviewer reads instead of re-deriving each
+hunk decision.
+
 ### 6. Verify after resolution
 
 After resolving ALL conflicts:

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

@@ -0,0 +1,101 @@
+---
+model_tier: medium
+name: pdf-tools
+description: "Use when creating, merging, splitting, filling, or extracting from a PDF — library-per-task, output validated. Triggers on 'merge these PDFs', 'fill this PDF form', 'split the PDF', 'create a PDF'."
+status: active
+tier: senior
+domain: process
+compatibility: "Requires consumer-installed PDF libraries: pypdf (merge/split/rotate/encrypt/extract), reportlab (create), a form library for AcroForm fill; an OCR engine (e.g. tesseract) only for the OCR task. No LibreOffice dependency. Ships zero runtime in this package."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+---
+
+# pdf-tools
+
+Wing-1 engineering skill for **PDF write/transform** — `markitdown` reads a PDF
+to Markdown; this creates, merges, fills, and extracts. Ships zero runtime: the
+agent drives libraries the consumer has. Pattern re-implementation only.
+
+## When to use
+
+- "Merge / split / rotate / encrypt these PDFs."
+- "Fill this PDF form (AcroForm) with these values."
+- "Create a PDF from this content."
+- "Extract the text / tables from this PDF" (structured extraction beyond `markitdown`'s Markdown).
+- "OCR this scanned PDF."
+
+Do NOT use for: PDF → Markdown ingestion (`markitdown`); Word (`docx-authoring`).
+
+## Procedure
+
+### 1. Library per task — do not force one tool
+
+| Task | Library path |
+|---|---|
+| merge / split / rotate / encrypt | pypdf — page-level operations, no rendering |
+| create from content | reportlab (canvas / platypus) |
+| form-fill (AcroForm) | a form-aware library; map field name → value, then flatten if the form must not be re-editable |
+| text / table extraction | a text-layer extractor; tables need a layout-aware pass, not naive text |
+| OCR (scanned/image PDF) | an OCR engine over rasterized pages — ONLY when there is no text layer |
+
+### 2. Decide flatten-or-keep on form fills
+
+A filled AcroForm stays editable unless flattened. Flatten when the PDF is a
+final artifact (an invoice, a signed form); keep fields when the recipient must
+edit further. State which you chose — a silently-editable "final" form is a
+correctness bug.
+
+### 3. Validate — assert output validity, do not trust the write
+
+1. Re-open the output with pypdf; assert `len(reader.pages)` matches the expected count (merge = sum; split = 1 per part).
+2. For a form-fill: read back one field value (pre-flatten) or extract the rendered text (post-flatten) and assert the value is present.
+3. For create: assert the file opens and page 1 carries expected text.
+
+## Output format
+
+1. The output PDF path(s).
+2. Validation: page count matches expected ✅, read-back value/text present ✅.
+3. For fills: flatten decision stated (flattened / kept-editable + why).
+
+## Gotcha
+
+**OCR is a last resort, not the default extraction path.** Running OCR over a
+PDF that already has a text layer produces worse output (OCR errors) than the
+existing text and burns time. Check for a text layer first; OCR only when it is
+genuinely absent.
+
+- **Editable "final" form:** a filled AcroForm left un-flattened ships as a "signed invoice" the recipient can silently alter → flatten when the artifact is final.
+
+## Do NOT
+
+- Do NOT bundle a Python toolkit in this package — drive the consumer's libraries (zero-runtime posture).
+- Do NOT OCR a PDF that has a text layer.
+- Do NOT leave a "final" filled form editable without saying so.
+- Do NOT claim success on "file written"; claim it only after the re-open + page-count assertion.
+
+## Related Skills
+
+**WHEN to use this**
+
+- The task creates, merges, splits, rotates, encrypts, or form-fills a PDF.
+- Structured text/table extraction beyond `markitdown`'s Markdown, or OCR of a scanned PDF.
+
+**WHEN NOT to use this**
+
+- PDF → Markdown ingestion → [`markitdown`](../markitdown/SKILL.md).
+- Word documents → [`docx-authoring`](../docx-authoring/SKILL.md); spreadsheets → [`spreadsheet-authoring`](../spreadsheet-authoring/SKILL.md).
+
+## When the agent should load this
+
+- "Merge / split / rotate these PDFs."
+- "Fill this PDF form."
+- "Create a PDF from this content."
+- "Extract the tables from this PDF / OCR this scan."
+
+## Output
+
+1. **Output PDF(s)** — the path(s). Cite as `pdf-output`.
+2. **Validation receipt** — page count matches expected ✅, read-back value/text present ✅. Cite as `pdf-validation`.
+3. **Fill decision** — present on form-fills: flattened / kept-editable + why. Cite as `pdf-fill-decision`.

package/dist/agent-src/skills/quality-tools/evals/evals.json

@@ -0,0 +1,15 @@
+{
+  "skill": "quality-tools",
+  "_calibration": "Seed for eval-schema v2 (ecosystem-harvest skill-quality-gates Phase 2). tool-choice + trajectory assertions are trace-gated: pass:null (manual-pending) in CI until a recorded tool-trace.json exists.",
+  "scenarios": [
+    {
+      "id": "runs-project-pinned-tools",
+      "prompt": "Fix the failing lint on the changed files.",
+      "environment": "a project whose pinned quality CLI is defined in its task runner",
+      "assertions": [
+        { "kind": "tool-choice", "must_use": ["bash"], "must_not_use": [] },
+        { "kind": "trajectory_budget", "n": 8 }
+      ]
+    }
+  ]
+}