@event4u/agent-config 2.17.0 → 2.19.0

package/.agent-src/commands/refine-ticket.md

@@ -77,6 +77,9 @@ persona voices) plus the close-prompt. Stop there. Do **not** chain into
 /refine-ticket PROJ-123
 /refine-ticket                              # uses current branch
 /refine-ticket --personas=+qa PROJ-123
+/refine-ticket --user-type=galabau-field-crew PROJ-123
+/refine-ticket --personas=+qa --user-type=truck-driver PROJ-123
+/refine-ticket --user-type=metalworking-shop PROJ-123
 /refine-ticket --fresh-eyes https://acme.atlassian.net/browse/PROJ-123
 ```
 

package/.agent-src/personas/README.md

@@ -5,6 +5,14 @@
 > expectations. Skills cite personas in a `personas:` frontmatter key.
 > Users invoke them via `--personas=<id>`.
 
+> For end-user-of-the-software lenses (galabau field crew, truck
+> driver, metalworking shop), see the parallel
+> [`user-types/`](../user-types/README.md) axis — personas describe
+> **how** we review (methodology), user-types describe **who** we
+> simulate (end user). They compose orthogonally on the CLI:
+> `--personas=qa --user-type=truck-driver`. No existing persona moves
+> to `user-types/`.
+
 ## Why this directory exists
 
 Before personas, every multi-lens skill (`adversarial-review`,

package/.agent-src/skills/refine-ticket/SKILL.md

@@ -240,6 +240,9 @@ open questions surfaced>
 - **Critical Challenger** — <one paragraph>
 - **AI Agent** — <one paragraph>
 - **[qa]** — *(only when `--personas=+qa`)* <one paragraph>
+- **User: <label>** — *(only when `--user-type=<id>`)* <one paragraph
+  citing Daily Workflow / Vocabulary / Operational Constraints /
+  Ticket Red Flags from the loaded user-type>
 
 ## Orchestration notes
 

package/.agent-src/templates/agents/agent-project-settings.example.yml

@@ -39,7 +39,7 @@ schema_version: 1
 # CI guard: a release bump of `package.json` must update this value
 # in lockstep — see scripts/check_template_pin_drift.py (road-to-
 # portable-runtime-and-update-check P3.3).
-agent_config_version: "2.16.0"
+agent_config_version: "2.18.0"
 
 # --- Project identity ---
 project:

package/.agent-src/user-types/README.md

@@ -0,0 +1,124 @@
+# User-types
+
+> Reusable **end-user simulation lenses** as a first-class primitive,
+> parallel to `personas/`. A user-type declares a *who*: a real
+> end-user of the software under review (a galabau field crew, a
+> truck driver, a metalworking shop). Skills consume them via
+> `--user-type=<id>` on the CLI.
+
+## Why this directory exists
+
+`personas/` answered one question well: *how* we review (qa,
+senior-engineer, critical-challenger, product-owner). It collapsed
+when "personas" like `galabau-field-crew` or `truck-driver` started
+landing — those are not review methodologies, they are the end-user
+viewpoint a methodology reviewer should adopt while reviewing.
+
+The two axes compose orthogonally:
+
+```
+/refine-ticket --personas=qa --user-type=truck-driver PROJ-123
+```
+
+QA methodology applied through a truck-driver end-user lens. The
+split is locked in [`../../docs/contracts/adr-user-types-axis.md`](../../docs/contracts/adr-user-types-axis.md).
+
+## What a user-type is — and is NOT
+
+- **Is**: a small Markdown file declaring an end-user simulation —
+  workflow, vocabulary, operational constraints, the questions only
+  this viewpoint would ask.
+- **Is NOT**: a persona. Personas describe review methodology, never
+  an end-user viewpoint.
+- **Is NOT**: an operational manual. User-types are review lenses
+  only — they flag ticket gaps, they never instruct a trade. No
+  welding procedures, no electrical work, no structural advice, no
+  dangerous how-to. The Anti-Patterns section in every file
+  encodes this floor.
+- **Is NOT**: an install-time filter. The vocabulary overlaps with
+  the install-time `user-types/` axis at the package root (see
+  [`../../docs/contracts/adr-install-user-type-axis.md`](../../docs/contracts/adr-install-user-type-axis.md)),
+  but the two live in different directories and consume different
+  config keys. Same word, different layer — by design.
+
+## Schema
+
+Locked in [`../../docs/contracts/user-type-schema.md`](../../docs/contracts/user-type-schema.md).
+
+- **Spine** — 7 sections (Focus · Daily Workflow · Vocabulary ·
+  Operational Constraints · Unique Questions · Ticket Red Flags ·
+  Anti-Patterns), ≤ 120 lines.
+- **Frontmatter** — `id · kind: user-type · description · version · source`.
+
+Run `task lint-skills` to enforce the schema, the size budget, and
+the Anti-Generic Quality Bar.
+
+## Anti-Generic Quality Bar (merge gate)
+
+Every user-type encodes **≥ 5 concrete, domain-specific review
+points** across `Daily Workflow`, `Vocabulary`, `Operational
+Constraints`, and `Ticket Red Flags`. Generic prose is REJECTED:
+
+- ❌ "consider mobile usability"  →  ✅ "capacitive touch fails with
+  wet leather gloves at 4 °C; tap targets ≥ 60 px or voice command"
+- ❌ "think about offline"  →  ✅ "no signal in cellar yards; queue
+  changes locally, conflict-resolve on the morning brief"
+
+Reviewer test: a generic reviewer persona could not have produced
+the `Unique Questions` or `Ticket Red Flags` of this file. If they
+could, the file is generic and must be rewritten.
+
+## Guardrails (encoded in every Anti-Patterns block)
+
+User-types are review lenses, not operational manuals. Every file's
+`## Anti-Patterns` section MUST explicitly forbid:
+
+- Trade-execution instructions (welding procedure, electrical work,
+  structural advice, anything that could harm if followed)
+- Dangerous how-to (chemical handling, equipment operation,
+  work-at-height procedures)
+- Medical / legal / engineering advice requiring a licensed
+  practitioner
+
+Allowed: workflow realism, ticket gap analysis, terminology
+correction, mobile / offline / safety / approval signals as
+ticket-requirement signals.
+
+## How skills use user-types
+
+CLI-only in v1 — skills do NOT declare a default `user-types:`
+frontmatter key. The migration path to v2 (skill-level default key)
+is documented in [`../../docs/contracts/adr-user-types-axis.md § Consequences`](../../docs/contracts/adr-user-types-axis.md).
+
+```
+/refine-ticket --user-type=truck-driver PROJ-123
+```
+
+If `--user-type=` is omitted, no end-user lens applies — persona
+review proceeds without simulation.
+
+## Authoring rules
+
+- Every user-type is drafted via the `artifact-drafting-protocol` rule.
+- Every user-type must pass the Anti-Generic Quality Bar (≥ 5
+  concrete review points, ≥ 3 Unique Questions falsifiable against a
+  ticket).
+- Project-specific user-types live in the consumer repo
+  (`.agent-src/user-types/` overrides), never in this package — the
+  three seeds shipped here are illustrative reference content.
+- Template: [`./_template/user-type.md`](./_template/user-type.md) (7 sections, ≤ 120 lines).
+
+## No-move policy
+
+No existing persona moves into this directory. The three seeds
+shipped here (`galabau-field-crew`, `metalworking-shop`,
+`truck-driver`) were born as user-types. Existing personas stay as
+personas. See [`../../docs/contracts/adr-user-types-axis.md § Migration`](../../docs/contracts/adr-user-types-axis.md).
+
+## Related
+
+- [`../../docs/contracts/user-type-schema.md`](../../docs/contracts/user-type-schema.md) — locked schema
+- [`../../docs/contracts/adr-user-types-axis.md`](../../docs/contracts/adr-user-types-axis.md) — the axis split decision
+- [`../../docs/contracts/adr-install-user-type-axis.md`](../../docs/contracts/adr-install-user-type-axis.md) — install-time `user_type` axis (distinct layer)
+- [`../personas/README.md`](../personas/README.md) — sister axis (methodology vs end-user)
+- [`../rules/artifact-drafting-protocol.md`](../rules/artifact-drafting-protocol.md) — mandatory per new user-type

package/.agent-src/user-types/_template/user-type.md

@@ -0,0 +1,95 @@
+---
+id: {user-type-id}
+kind: user-type
+description: "One sentence — who this lens simulates and the operational reality they bring; ≤ 160 chars."
+version: "1.0"
+source: project
+---
+
+# {Human-readable user-type name}
+
+## Focus
+
+One paragraph. Who this lens is, the operational context they work
+in (site, shop, vehicle, office), and what no persona catches.
+State the workflow shape and the time pressure that frames every
+decision they make.
+
+End with one sentence pinning the boundary: this lens is a **review
+lens only**, never an operational instruction source. No trade
+execution. No dangerous how-to.
+
+## Daily Workflow
+
+Concrete day-shape. What happens at 06:00, 10:00, 15:00. Who they
+talk to, what they touch, what they wait for. Avoid generic prose
+("they manage tasks"). Encode the actual rhythm.
+
+- {Morning routine — concrete trigger, tool, deliverable.}
+- {Mid-day workflow — concrete trigger, tool, deliverable.}
+- {End-of-day proof / close-out — concrete artefact + verification step.}
+
+## Vocabulary
+
+Domain terms the software must use (or must NOT substitute).
+Bilingual where the trade is bilingual. Plain-language over
+engineer-language where the user is non-technical.
+
+- {Term 1 — what it means, why the substitution fails.}
+- {Term 2.}
+- {Term 3.}
+
+## Operational Constraints
+
+Each constraint is a UI / flow signal, not generic empathy.
+
+- {Mobile / offline / connectivity / dead-zone constraint.}
+- {PPE / gloves / noise / lighting / weather constraint.}
+- {Time-pressure / hours-of-service / break-window constraint.}
+- {Hardware constraint — device, screen size, input mode.}
+- {Optional: legal / safety / certification constraint.}
+
+## Unique Questions
+
+Three or more questions no persona asks verbatim. Each must be
+falsifiable against the ticket under review.
+
+- {Question 1 — direct, scoped, answerable from the ticket.}
+- {Question 2.}
+- {Question 3.}
+- {Optional Question 4.}
+
+## Ticket Red Flags
+
+What this lens flags as missing or unrealistic when reviewing a
+ticket. Bullet list — each item names a concrete signal a generic
+reviewer would miss.
+
+- {Red flag 1 — concrete signal + why it matters in this domain.}
+- {Red flag 2.}
+- {Red flag 3.}
+
+## Anti-Patterns
+
+Non-negotiable. Guardrails are encoded here.
+
+- **Review-only, never operational.** No trade execution
+  instructions (welding procedure, electrical work, structural
+  advice). No dangerous how-to. No medical / legal / engineering
+  advice that requires a licensed practitioner.
+- **No generic prose.** "Consider usability" / "think about offline"
+  fails the Anti-Generic Quality Bar — every observation cites a
+  concrete signal.
+- {Anti-pattern 3 — domain-specific failure mode this lens refuses to validate.}
+- {Anti-pattern 4 — optional.}
+
+---
+
+*Author note (delete before publishing): this template targets the
+7-section spine locked in
+[`docs/contracts/user-type-schema.md`](../../../docs/contracts/user-type-schema.md).
+Stay within the **≤ 120 line** budget (file total, including
+frontmatter). Replace every `{placeholder}` with concrete content
+that passes the Anti-Generic Quality Bar (≥ 5 concrete review
+points; ≥ 3 Unique Questions). Run `task lint-skills` before
+commit.*

package/.agent-src/user-types/galabau-field-crew.md

@@ -0,0 +1,100 @@
+---
+id: galabau-field-crew
+kind: user-type
+description: "Landscape-build crew on site — gloves, mud, no-signal, billable-photo proofs, bilingual plain-German vocabulary."
+version: "1.0"
+source: project
+---
+
+# Galabau Field Crew
+
+## Focus
+
+Two- to four-person crew on a landscape / garden-build site —
+paver-laying, retaining walls, planting, irrigation. Phone or
+rugged tablet in a pouch, gloves on, lifting something heavy every
+fifteen minutes. Workday shaped by weather, delivery slots, and
+customer arriving unannounced for "just one more thing". No
+reliable signal on half the sites. Every customer-requested change
+is either billable later or silently swallowed; documentation at
+the moment of change is the only way that decision survives.
+
+Review lens only, never operational instruction source. No
+paver-laying procedure, no soil-prep chemistry, no structural
+advice on retaining walls.
+
+## Daily Workflow
+
+- 06:30 — depot pickup, materials loaded, route confirmed; lead
+  reads day plan once, on phone, gloves off.
+- 07:30–11:30 — execution on site; phone back in pouch. UI reads
+  happen at coffee breaks or when customer interrupts.
+- 11:30 — billable-change moment: customer asks for an extra step,
+  crew lead captures it as timestamped photo + short note +
+  ideally signature, **before** next task starts.
+- 15:30 — end-of-day proof: photo of finished section, geotagged,
+  uploaded if signal exists, queued offline if not.
+- 17:00 — depot return; office reconciles day from photos +
+  notes, not from memory.
+
+## Vocabulary
+
+- **Aufmass** — measured-on-site quantity that becomes invoice
+  basis; never substitute with "estimate" or "measurement".
+- **Nachtrag** — billable change-request added to a running job;
+  losing one = losing money, not just data.
+- **Sauberkeitsschicht** — gravel layer under pavers; plain-German,
+  not "base course".
+- **Plain-German over engineer-German.** Crew is bilingual (often
+  DE / PL / TR); noun must be the one on the delivery slip, not
+  the one in the BOQ.
+
+## Operational Constraints
+
+- **No signal on half the sites.** Every write must queue and sync;
+  every read must work from cache. Conflict resolution on sync is
+  a ticket requirement, not a nice-to-have.
+- **Capacitive touch fails with wet or dirty gloves.** Primary
+  flows survive with stylus, knuckle, or large-target taps. No
+  pinch-zoom on the critical path.
+- **Photo is the proof, not the form.** A billable-change flow
+  needing three text fields before camera opens loses changes
+  silently — crew defers, then forgets.
+- **Screen washout in direct sun.** High-contrast mode on by
+  default for outdoor flows, never opt-in via settings.
+- **Rugged hardware, slow CPU.** Animations and skeleton loaders
+  burn battery; crew runs 10+ hours per charge on the device.
+
+## Unique Questions
+
+- Does this flow survive a 4-hour offline window plus a sync with
+  conflicting edits from the office?
+- Can a gloved hand complete the primary action in one tap from
+  the home screen without typing?
+- Is there a photo-first path for capturing a billable change, or
+  does the form block the camera?
+- Is the noun on screen the one written on the delivery slip, in
+  the language the crew actually uses?
+
+## Ticket Red Flags
+
+- "User enters …" without specifying input mode — gloves rule out
+  the keyboard on the critical path.
+- Sync described as "auto" with no conflict-resolution UI sketched.
+- High-contrast / outdoor visibility treated as a settings toggle
+  rather than the default for outdoor flows.
+- No mention of what happens when the customer signature step is
+  refused or skipped.
+
+## Anti-Patterns
+
+- **Review-only, never operational.** No paver-laying procedure,
+  soil chemistry, structural retaining-wall advice, or anything a
+  licensed Galabauer must sign off.
+- **No generic prose.** "Consider offline support" fails the
+  Anti-Generic Quality Bar — every observation cites a concrete
+  signal (gloves, signal-loss, Nachtrag, Aufmass).
+- **No engineer-vocabulary substitution.** Renaming Nachtrag to
+  "change request" in the UI breaks the billing chain.
+- **No photo-after-form flows.** Photo must be reachable in one
+  tap from the moment customer asks for the change.

package/.agent-src/user-types/metalworking-shop.md

@@ -0,0 +1,105 @@
+---
+id: metalworking-shop
+kind: user-type
+description: "Shop-floor metalworking team — job travelers, material certs, machine-time gates, PPE/noise constraints on UI."
+version: "1.0"
+source: project
+---
+
+# Metalworking Shop
+
+## Focus
+
+Small-to-mid metalworking shop — laser-cut, press-brake, weld,
+finish. Two surfaces: shop-floor tablets bolted near machines
+(loud, dirty, gloves) and an office desktop where quoting,
+scheduling, and material-cert tracking happen. Shop runs on **job
+travelers** (route cards) — one per job following the work through
+every station, getting stamped, ending in the shipping bay.
+Material certificates (heat numbers, mill certs) must trace from
+incoming bar stock through to the customer; losing the chain
+breaks the audit and can void the order.
+
+Review lens only, never operational instruction source. No
+welding-procedure spec, no electrical guidance, no
+structural-engineering advice. Trade execution stays with the
+certified welder, the EHS officer, and the engineer.
+
+## Daily Workflow
+
+- 06:00 — shift starts, lead reviews day's travelers at office
+  desktop; priority shifts printed and pinned at the station.
+- 07:00–15:30 — execution per station; each station scans the
+  traveler QR or punches job number on tablet to start / pause /
+  complete time on that step.
+- Material check-in — incoming bar stock photographed with mill
+  cert; heat number bound to lot at moment of receipt, not later
+  from memory.
+- Safety sign-off — process steps requiring PPE or second-person
+  check (overhead crane, confined-space weld) cannot start until
+  sign-off is recorded on the tablet.
+- 15:30 — end-of-shift, lead reconciles open travelers, flags any
+  step where the material-cert chain is broken.
+
+## Vocabulary
+
+- **Job traveler / route card** — single canonical record that
+  moves with the part; never substitute with "ticket" or "task".
+- **Heat number / mill cert** — material identity; lose the link
+  and the part is unsellable to a regulated customer.
+- **Sign-off** — recorded, named, timestamped; "approved" without
+  a name fails audit.
+- **Setup vs run time** — booked separately on the machine;
+  merging them destroys costing accuracy.
+
+## Operational Constraints
+
+- **Shop-floor tablet bolted at the station.** Two-arm reach,
+  gloves on, noise > 85 dB → no voice input, large tap targets,
+  high contrast on by default.
+- **PPE prevents fine touch.** Welding gloves + safety glasses;
+  drop-down pickers with > 6 options are a fail mode.
+- **Machine-time is money.** A flow adding 30 seconds per
+  job-step start, run 200 times/day, costs the shop one
+  machine-hour per shift.
+- **Material-cert chain is regulatory.** Every step touching
+  material must capture or carry the heat-number link; breaking
+  it silently is the worst failure mode.
+- **Two-surface split.** Office desktop has Excel-grade density;
+  shop tablet has one-action-per-screen. Same flow cannot share
+  a layout.
+
+## Unique Questions
+
+- Does this flow carry the heat-number / material-cert link from
+  receipt to ship, with no manual re-entry step that can drop it?
+- Can a gloved welder complete the station start / pause / end in
+  one tap each, without picking from a long drop-down?
+- Is the safety-sign-off step a hard prerequisite enforced by the
+  system, or a soft reminder a tired operator can dismiss?
+- Does the layout adapt between bolted-tablet (shop) and desktop
+  (office), or is one surface compromised to match the other?
+
+## Ticket Red Flags
+
+- "User selects job from dropdown" — long list, gloves, no QR
+  alternative.
+- Material-cert mentioned only at receipt, not propagated through
+  the route.
+- Setup time and run time collapsed into a single "time on job"
+  field.
+- Safety sign-off treated as optional metadata rather than a gate.
+- One layout described for both surfaces without saying which.
+
+## Anti-Patterns
+
+- **Review-only, never operational.** No welding procedure (WPS),
+  no electrical work, no PPE selection guidance, no structural or
+  fatigue-engineering advice — those require certified humans.
+- **No generic prose.** "Consider shop-floor usability" fails the
+  Anti-Generic Quality Bar — every observation cites traveler,
+  heat number, sign-off, machine-time, or PPE.
+- **No collapsing setup-and-run time.** Costing depends on the
+  split; merging it for "UI simplicity" destroys the model.
+- **No silent loss of material-cert link.** A flow that lets the
+  chain break without an audit signal is rejected.

package/.agent-src/user-types/truck-driver.md

@@ -0,0 +1,113 @@
+---
+id: truck-driver
+kind: user-type
+description: "Commercial truck driver — voice-first, hours-of-service gated, dead-zone tolerant, photo+GPS proof-of-delivery."
+version: "1.0"
+source: project
+---
+
+# Truck Driver
+
+## Focus
+
+Commercial truck driver doing regional or long-haul delivery —
+typically single driver, phone or in-cab tablet on a mount, gloves
+optional but hands often busy with the wheel, paperwork, or a
+pallet jack. Day is gated by **hours-of-service (HOS)** — legally
+bounded driving and rest windows that cannot be ignored without
+losing the licence. Cargo moves through warehouses, loading docks,
+customer yards; signal drops in tunnels, basements, rural
+stretches. Proof-of-delivery (photo + signature + GPS + timestamp)
+is the moment the invoice becomes collectable.
+
+Review lens only, never operational instruction source. No driving
+advice, no HOS legal interpretation, no vehicle-maintenance
+guidance, no hazmat procedure. Trade execution stays with the
+dispatcher, the safety officer, and the certified driver-trainer.
+
+## Daily Workflow
+
+- 05:00 — pre-trip inspection, vehicle check captured on tablet;
+  driver swipes into HOS clock at start of duty.
+- 06:00 — first loading-dock arrival; wait time on the dock can be
+  15 minutes or 3 hours; status (waiting / loading / loaded)
+  matters for billing and HOS attribution.
+- 07:30 — driving: device must not require typing or precise taps
+  while in motion; voice input or large single-tap actions only.
+- Multiple stops — route may reorder mid-day (cancelled stop, new
+  rush stop); ETA must recalc and propagate to the customer
+  without driver intervention beyond confirming.
+- Per delivery — photo of the pallet, customer signature
+  on-screen, GPS pin, timestamp; the four-tuple is the invoice
+  trigger.
+- End of duty — HOS clock closes; if next break-window starts
+  mid-route, system warns **before** the driver commits.
+
+## Vocabulary
+
+- **HOS (hours-of-service)** — legally enforced driving / rest
+  windows; not "shift hours" or "working time".
+- **POD (proof-of-delivery)** — the photo + signature + GPS +
+  timestamp four-tuple; missing one element = unbilled delivery.
+- **Dock dwell / detention** — wait time at a dock, often billable
+  to the shipper; capturing the timestamps is the negotiation
+  evidence.
+- **Bill of lading (BOL)** — paper or electronic; the legal cargo
+  manifest, not a "shipment summary".
+
+## Operational Constraints
+
+- **Driving-while-using is prohibited.** No typing flow on the
+  critical path while in motion; voice or large single-tap only.
+  Anything else risks the licence and the company.
+- **HOS is hard law.** A UI that lets the driver accept a stop
+  that would breach the remaining break-window is rejected — the
+  system warns first, dispatcher reroutes.
+- **Dead zones are routine.** Tunnels, basements, rural roads;
+  every write queues, every read works from cache, and POD
+  uploads sync with photo intact when signal returns.
+- **One-handed operation.** Other hand on the wheel, paperwork,
+  or pallet jack; bottom-thumb-reachable primary actions, no
+  precision drag.
+- **Cold / wet / glare.** Outdoor docks in winter; gloves on,
+  screen wet, sun directly on the display — same outdoor-default
+  high-contrast as the field-crew lens.
+
+## Unique Questions
+
+- Does the primary flow work hands-busy at a loading dock, with
+  voice or one large tap, and not collapse if the connection
+  drops mid-step?
+- Does the POD step capture photo + signature + GPS + timestamp
+  in a single offline-resilient action, or are they four separate
+  forms that can each drop?
+- Does the system block or warn before the driver accepts a stop
+  that would breach the remaining HOS break-window?
+- Is dock-dwell time captured automatically from arrival to
+  loaded, or does it rely on the driver remembering to tap?
+
+## Ticket Red Flags
+
+- "Driver enters …" with text input on the in-motion path.
+- POD described as a single field rather than a four-element
+  bundle (photo + signature + GPS + timestamp).
+- HOS treated as informational ("show remaining hours") rather
+  than a constraint on what stops can be accepted.
+- Sync described as online-only; no queue + retry sketched for
+  dead-zone delivery.
+- Dock-dwell capture left to manual tap with no arrival-trigger
+  fallback.
+
+## Anti-Patterns
+
+- **Review-only, never operational.** No driving advice, no HOS
+  legal interpretation, no vehicle-maintenance procedure, no
+  hazmat-handling guidance. Those need certified humans.
+- **No generic prose.** "Consider mobile usability" fails the
+  Anti-Generic Quality Bar — every observation cites HOS, POD,
+  dock-dwell, dead-zone, or hands-busy.
+- **No in-motion typing on the critical path.** A flow needing
+  the driver to type while driving is rejected outright.
+- **No partial POD acceptance.** Missing any element of the
+  four-tuple = unbilled; the flow must hold the action open
+  until all four are captured or explicitly waived by dispatch.

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Shared agent configuration \u2014 skills for AI coding tools (Claude Code, Augment, Cursor, Cline, Windsurf, Gemini CLI).",
-    "version": "2.17.0",
+    "version": "2.19.0",
     "keywords": [
       "agent-config",
       "skills",

package/CHANGELOG.md

@@ -702,6 +702,74 @@ our recommendation order, not its support status.
 > that forces a new era split (`# Era: 2.16.x`, etc.) — see
 > [`docs/contracts/CHANGELOG-conventions.md § Era splits`](docs/contracts/CHANGELOG-conventions.md).
 
+## [2.19.0](https://github.com/event4u-app/agent-config/compare/2.18.0...2.19.0) (2026-05-16)
+
+### Features
+
+* **user-types:** land three seed user-types (galabau, metalworking, truck) ([361745e](https://github.com/event4u-app/agent-config/commit/361745ec88d32c7f6faa8f50ac4d350f95f6b6d1))
+* **refine-ticket:** add --user-type lens, orthogonal to --personas ([7d70138](https://github.com/event4u-app/agent-config/commit/7d7013840d92d53ead0b8dba15bf6613398dcd5b))
+* **linter:** add user-type artifact-type support ([bce874c](https://github.com/event4u-app/agent-config/commit/bce874cdb7e925585b74b478b0f4f0e4a7f40380))
+* **user-types:** wire compile pipeline + author scaffolding ([8637dae](https://github.com/event4u-app/agent-config/commit/8637dae4463796726b0d7e737d37169334a0283b))
+* **user-types:** lock schema + ADR for runtime user-type axis ([0ce1549](https://github.com/event4u-app/agent-config/commit/0ce1549a1e5037521cb06e9d1c467fa4ebf87d06))
+* **eval-findings:** add schema template for step-13 closure evidence ([2b2daa4](https://github.com/event4u-app/agent-config/commit/2b2daa46fbf348f5a2901b185c91901de06a1025))
+* **recruits:** add intake template for step-13 P1 recruit walkthroughs ([a569071](https://github.com/event4u-app/agent-config/commit/a569071853d665ca57813fc4c4676bba38716fac))
+
+### Bug Fixes
+
+* **adr:** drop transient roadmap links from user-types axis ADR ([e8d30fe](https://github.com/event4u-app/agent-config/commit/e8d30fe80c2d0b87406571b2c3dbbdd031312998))
+* **contracts:** clamp user-type beta-review markers to 90-day window ([25af8cc](https://github.com/event4u-app/agent-config/commit/25af8ccd650d6ea304f5060ebb55c2d034d746a2))
+* **refine-ticket:** sync compressed SKILL.md with --user-type persona-voice bullet ([14b9dcd](https://github.com/event4u-app/agent-config/commit/14b9dcdab69f063e1dcfc8d9070892b4d56305b1))
+* **refs:** inline AI Council Phase 4 convergence summary ([0e6a578](https://github.com/event4u-app/agent-config/commit/0e6a5780773fbabba6f98a01bd4b25726c996903))
+* **adr:** drop transient roadmap links from MCP runtime ADR ([8f2691e](https://github.com/event4u-app/agent-config/commit/8f2691e90130a9333bd9e01d0863ecb0c9f7ec97))
+* **template:** bump agent_config_version pin to 2.18.0 ([dd7441d](https://github.com/event4u-app/agent-config/commit/dd7441d2fc0fd785a70272b6520eb0eb29a61a66))
+
+### Documentation
+
+* **user-types:** cross-link personas↔user-types and surface metalworking-shop example ([ac0b0ce](https://github.com/event4u-app/agent-config/commit/ac0b0ce2e356654352d3c4caf1528b3d5772047c))
+* **step-13:** link new recruit + eval-finding templates from prerequisites ([57b729a](https://github.com/event4u-app/agent-config/commit/57b729a236bf1b442df140fb2efbdecd9e73ffd9))
+* **adr:** record MCP server runtime as Anthropic Python SDK ([5f5d689](https://github.com/event4u-app/agent-config/commit/5f5d6895d4369b313e1a5058eca21807e5566cfd))
+
+### Tests
+
+* **user-types:** add coverage audit script + tests ([ca403bb](https://github.com/event4u-app/agent-config/commit/ca403bb714fd505f539715fe25b7948714d0ee66))
+* **user-types:** lock schema, lint, and composition contracts ([cfeb48a](https://github.com/event4u-app/agent-config/commit/cfeb48a9d04956ff9d6744383b44bcabeaa57702))
+
+### Chores
+
+* **roadmap:** close step-6 user-types axis and refresh progress dashboard ([2f50a96](https://github.com/event4u-app/agent-config/commit/2f50a96eeec1ea1bf832ed560553d4e940a94812))
+* **roadmap:** close step-14 phases 1+2 against shipped MCP server ([2dcf04b](https://github.com/event4u-app/agent-config/commit/2dcf04bdf5f71bd546b7ec9cf27bbbb7fc6d0ec4))
+
+Tests: 4493 (+17 since 2.18.0)
+
+## [2.18.0](https://github.com/event4u-app/agent-config/compare/2.17.0...2.18.0) (2026-05-16)
+
+### Features
+
+* **lint:** user-type axis frontmatter audit + task wiring ([322bf1d](https://github.com/event4u-app/agent-config/commit/322bf1dc805550cb8c234808bde4235aaf0ba39e))
+* **mcp:** filter skill prompts by personal.user_type ([0b09911](https://github.com/event4u-app/agent-config/commit/0b09911ea6ed2870b12b52ee67a922c3df1f919c))
+* **install:** wire --user-type flag across install entrypoints ([6589c6b](https://github.com/event4u-app/agent-config/commit/6589c6bce4682d521c12727adc4903e7333a421d))
+* **install:** add user_type schema + template placeholder + ADR ([3ede84d](https://github.com/event4u-app/agent-config/commit/3ede84d79ce0d3612ae6d2a862ae239cb01f8762))
+
+### Documentation
+
+* **roadmaps:** close step-9 user-types axis + flip parent step-12 ([f1926dc](https://github.com/event4u-app/agent-config/commit/f1926dc6905128bfcb909dc03e47a37c7754e4e3))
+
+### Tests
+
+* **install:** cover --user-type + sync user_type preservation ([349478f](https://github.com/event4u-app/agent-config/commit/349478fccc608a2a9818585f7c2a43368ee076c0))
+
+### Chores
+
+* **docs:** drop broken step-12 link from getting-started-by-role ([351505a](https://github.com/event4u-app/agent-config/commit/351505a8fbc6626db5dd26cea494d2a4dbaead89))
+* **contracts:** inline council verdict + pragma roadmap source-trails ([4442030](https://github.com/event4u-app/agent-config/commit/4442030543b02511ced3643d9c6062e0722448d9))
+* **contracts:** drop transient roadmap refs from stable artifacts ([ecad21e](https://github.com/event4u-app/agent-config/commit/ecad21e16b7269257ba95d104b2dce06a9f140a5))
+* **contracts:** align keep-beta-until with 90-day window cap ([5c87588](https://github.com/event4u-app/agent-config/commit/5c8758854d19f5790b21bba41c4631e8460caa5e))
+* **roadmaps:** retag step-13/14 complexity to lightweight ([e87cd35](https://github.com/event4u-app/agent-config/commit/e87cd35483cb16eb39574a10318c2f9cb720e9a7))
+* **template:** bump agent_config_version pin to 2.17.0 ([f6bb24e](https://github.com/event4u-app/agent-config/commit/f6bb24e1267623bd49dffd1deb0c9ae071ea4906))
+* **index:** regenerate index after upstream privacy-review desc edit ([fd7fe24](https://github.com/event4u-app/agent-config/commit/fd7fe248b2297021912ec41aff5dd5b1596c9989))
+
+Tests: 4476 (+17 since 2.17.0)
+
 ## [2.17.0](https://github.com/event4u-app/agent-config/compare/2.16.0...2.17.0) (2026-05-15)
 
 ### Features