@stacksjs/defaults 0.75.108 → 0.75.110

package/ai/skills/stacks-implement-spec/PLAYBOOK.md

@@ -0,0 +1,37 @@
+> Adapted playbook. Read [the Stacks rules](../stacks-flow/ENGINEERING.md) first. Commit, push, publish, and tracker mutations are conditional on the user's authorization.
+
+
+You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.
+
+Read the existing tracker convention; otherwise use local Markdown as described in the Stacks adaptation rules.
+
+The goal is the entire spec implemented on a single **integration branch**, with every ticket resolved the way the issue tracker closes work.
+
+The tickets are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tickets which are ready to be grabbed.
+
+Communication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.
+
+**Implementer subagents** should be run in the background where possible for maximum concurrency.
+
+## Steps
+
+1. Read the spec and tickets to understand the task graph.
+
+2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.
+
+3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.
+
+4. Use **implementer subagents** to implement each ticket, each in its own worktree on its own branch. Each implementer subagent:
+   - confirms its worktree is based on the integration branch before starting, and resets onto it if not;
+   - calls the Skill tool with `stacks-tdd` to build the ticket;
+   - merges the integration branch tip into its own branch before reporting done
+
+5. Once an **implementer subagent** completes, merge its work to the integration branch with a **merger subagent**.
+
+6. If this changes the **frontier** of available tickets, kick off more **implementer subagents** to work on the new tickets. This allows for maximum concurrency.
+
+7. Once all tickets are complete, call the Skill tool with `stacks-review` on the integration branch. Fix all issues raised by the code review in a single **implementer subagent**.
+
+8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.
+
+9. Clean up all **implementer subagent** worktrees.

package/ai/skills/stacks-implement-spec/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: stacks-implement-spec
+description: Implement the result of /to-spec and /to-tickets in code. Covers Stacks engineering workflows.
+disable-model-invocation: true
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Implement Spec
+
+Read [the Stacks adaptation rules](../stacks-flow/ENGINEERING.md), then
+[PLAYBOOK.md](PLAYBOOK.md). The playbook preserves this workflow's decision
+criteria; the Stacks rules govern APIs, tooling, tracking, and authorization.
+
+Credit: adapted from Matt Pocock's `implement-spec` skill, MIT licensed.
+See [NOTICE.md](NOTICE.md) and [LICENSE](LICENSE).
+
+## Completion
+
+Produce the requested behavior or reviewable artifact and satisfy the
+playbook's completion criteria. Preserve existing decisions and user edits.
+Use the native Stacks skills for implementation and verification, and carry
+existing authorization through the workflow.

package/ai/skills/stacks-improve-codebase-architecture/HTML-REPORT.md

@@ -0,0 +1,126 @@
+# HTML Report Format
+
+Render the architectural review as a standalone HTML file in the OS temp
+directory with local CSS or precompiled Crosswind styles. Mermaid is optional
+when already available; static diagrams should remain legible without a network
+dependency. Use graph diagrams for dependencies and sequences, and simple
+layout diagrams where that better explains a change.
+
+## Scaffold
+
+```html
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <title>Architecture review for {{repo name}}</title>
+    <script type="module">
+      import mermaid from "https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs";
+      mermaid.initialize({ startOnLoad: true, theme: "neutral", securityLevel: "loose" });
+    </script>
+    <style>
+      /* Include the report's complete layout styles here:
+         dashed seam lines, hand-drawn-feeling arrow heads, etc. */
+      .seam { stroke-dasharray: 4 4; }
+      .leak { stroke: #dc2626; }
+      .deep { background: linear-gradient(135deg, #0f172a, #1e293b); }
+    </style>
+  </head>
+  <body class="font-sans text-slate-900 bg-stone-50">
+    <main class="mx-auto px-6 py-12 space-y-12 max-w-5xl">
+      <header>...</header>
+      <section id="candidates" class="space-y-10">...</section>
+      <section id="top-recommendation">...</section>
+    </main>
+  </body>
+</html>
+```
+
+## Header
+
+Repo name, date, and a compact legend: solid box = module, dashed line = seam, red arrow = leakage, thick dark box = deep module. No introduction paragraph. Straight into the candidates.
+
+## Candidate card
+
+The diagrams carry the weight. Prose is sparse, plain, and uses the glossary terms (from the `/stacks-codebase-design` skill) without ceremony.
+
+Each candidate is one `<article>`:
+
+- **Title**: short, names the deepening (e.g. "Collapse the Order intake pipeline").
+- **Badge row**: recommendation strength (`Strong` = emerald, `Worth exploring` = amber, `Speculative` = slate), plus a tag for the dependency category (`in-process`, `local-substitutable`, `ports & adapters`, `mock`).
+- **Files**: monospaced list, `font-mono text-sm`.
+- **Before / After diagram**: the centrepiece. Two columns, side by side. See patterns below.
+- **Problem**: one sentence. What hurts.
+- **Solution**: one sentence. What changes.
+- **Wins**: bullets, ≤6 words each. e.g. "Tests hit one interface", "Pricing logic stops leaking", "Delete 4 shallow wrappers".
+- **ADR callout** (if applicable): one line in an amber-tinted box.
+
+No paragraphs of explanation. If the diagram needs a paragraph to be understood, redraw the diagram.
+
+## Diagram patterns
+
+Pick the pattern that fits the candidate. Mix them. Don't make every diagram look the same. Variety is part of the point.
+
+### Mermaid graph (the workhorse for dependencies / call flow)
+
+Use a Mermaid `flowchart` or `graph` when the point is "X calls Y calls Z, and look at the mess." Wrap it in a Tailwind-styled card so it doesn't feel parachuted in. Style with classDef to colour leakage edges red and the deep module dark. Sequence diagrams work well for "before: 6 round-trips; after: 1."
+
+```html
+<div class="p-4 bg-white border border-slate-200 rounded-lg">
+  <pre class="mermaid">
+    flowchart LR
+      A[OrderHandler] --> B[OrderValidator]
+      B --> C[OrderRepo]
+      C -.leak.-> D[PricingClient]
+      classDef leak stroke:#dc2626,stroke-width:2px;
+      class C,D leak
+  </pre>
+</div>
+```
+
+### Hand-built boxes-and-arrows (when Mermaid's layout fights you)
+
+Modules as `<div>`s with borders and labels. Arrows as inline SVG `<line>` or `<path>` elements positioned absolutely over a relative container. Reach for this when you want the "after" diagram to feel like one thick-bordered deep module with greyed-out internals, since Mermaid won't render that with the right weight.
+
+### Cross-section (good for layered shallowness)
+
+Stack horizontal bands (`h-12 border-l-4`) to show layers a call passes through. Before: 6 thin layers each doing nothing. After: 1 thick band labelled with the consolidated responsibility.
+
+### Mass diagram (good for "interface as wide as implementation")
+
+Two rectangles per module: one for interface surface area, one for implementation. Before: interface rectangle is nearly as tall as the implementation rectangle (shallow). After: interface rectangle is short, implementation rectangle is tall (deep).
+
+### Call-graph collapse
+
+Before: a tree of function calls rendered as nested boxes. After: the same tree collapsed into one box, with the now-internal calls shown faded inside it.
+
+## Style guidance
+
+- Lean editorial, not corporate-dashboard. Generous whitespace. Serif optional for headings (`font-serif` works well with stone/slate).
+- Colour sparingly: one accent (emerald or indigo) plus red for leakage and amber for warnings.
+- Keep diagrams ~320px tall so before/after sits comfortably side by side without scrolling.
+- Use `text-xs uppercase tracking-wider` for module labels inside diagrams, so they read as schematic, not as UI.
+- The only scripts are the local CSS and the Mermaid ESM import. The report is otherwise static: no app code, no interactivity beyond Mermaid's own rendering.
+
+## Top recommendation section
+
+One larger card. Candidate name, one sentence on why, anchor link to its card. That's it.
+
+## Tone
+
+Plain English, concise, but the architectural nouns and verbs come straight from the `/stacks-codebase-design` skill. Concision is not an excuse to drift.
+
+**Use exactly:** module, interface, implementation, depth, deep, shallow, seam, adapter, leverage, locality.
+
+**Never substitute:** component, service, unit (for module) · API, signature (for interface) · boundary (for seam) · layer, wrapper (for module, when you mean module).
+
+**Phrasings that fit the style:**
+
+- "Order intake module is shallow: interface nearly matches the implementation."
+- "Pricing leaks across the seam."
+- "Deepen: one interface, one place to test."
+- "Two adapters justify the seam: HTTP in prod, in-memory in tests."
+
+**Wins bullets** name the gain in glossary terms: *"locality: bugs concentrate in one module"*, *"leverage: one interface, N call sites"*, *"interface shrinks; implementation absorbs the wrappers"*. Don't write *"easier to maintain"* or *"cleaner code"*, because those terms aren't in the glossary and don't earn their place.
+
+No hedging, no throat-clearing, no "it's worth noting that…". If a sentence could be a bullet, make it a bullet. If a bullet could be cut, cut it. If a term isn't in the `/stacks-codebase-design` glossary, reach for one that is before inventing a new one.

package/ai/skills/stacks-improve-codebase-architecture/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Matt Pocock
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-improve-codebase-architecture/NOTICE.md

@@ -0,0 +1,10 @@
+# Source and license
+
+The upstream MIT notice is preserved in [LICENSE](LICENSE).
+
+## improve-codebase-architecture
+
+Source: [skills/engineering/improve-codebase-architecture/SKILL.md](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/improve-codebase-architecture/SKILL.md),
+revision `49dd158d1076134a641b33efb035946536778336`.
+
+Ported with Stacks skill names, canonical guidance, local-tracker fallback, TypeScript/Bun tooling, and conditional external actions.

package/ai/skills/stacks-improve-codebase-architecture/PLAYBOOK.md

@@ -0,0 +1,68 @@
+> Adapted playbook. Read [the Stacks rules](../stacks-flow/ENGINEERING.md) first. Commit, push, publish, and tracker mutations are conditional on the user's authorization.
+
+
+# Improve Codebase Architecture
+
+Surface architectural friction and propose **deepening opportunities**: refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
+
+This command is _informed_ by the project's domain model and built on a shared design vocabulary:
+
+- Call the Skill tool with "stacks-codebase-design" for the architecture vocabulary (**module**, **interface**, **depth**, **seam**, **adapter**, **leverage**, **locality**) and its principles (the deletion test, "the interface is the test surface", "one adapter = hypothetical seam, two = real"). Use these terms exactly in every suggestion, and don't drift into "component," "service," "API," or "boundary."
+- The domain language in `GLOSSARY.md` gives names to good seams; ADRs in `docs/adr/` record decisions this command should not re-litigate.
+
+## Process
+
+### 1. Explore
+
+**Scope before you scan: YAGNI.** Deepening a module pays off by making future changes to it easier, so put extra weight on the parts of the codebase that have recently changed. Decide _where_ to look before you look:
+
+- If the user named a direction (a module, a subsystem, a pain point), take it, and skip the inference below.
+- Otherwise, walk back a good stretch of the commit history (`git log --oneline`) to find the codebase's hot spots, the files and areas that keep coming up, and let those paths pull your attention first. If the changes are scattered with no clear hot spot, widen the net.
+
+Read the project's domain glossary (`GLOSSARY.md`) and any ADRs in the area you're touching first.
+
+Then spawn a sub-agent to walk the codebase. Don't follow rigid heuristics; explore organically and note where you experience friction:
+
+- Where does understanding one concept require bouncing between many small modules?
+- Where are modules **shallow**, with an interface nearly as complex as the implementation?
+- Where have pure functions been extracted just for testability, but the real bugs hide in how they're called (no **locality**)?
+- Where do tightly-coupled modules leak across their seams?
+- Which parts of the codebase are untested, or hard to test through their current interface?
+
+Apply the **deletion test** to anything you suspect is shallow: would deleting it concentrate complexity, or just move it? A "yes, concentrates" is the signal you want.
+
+### 2. Present candidates as an HTML report
+
+Write a self-contained HTML file to the OS temp directory so nothing lands in the repo. Resolve the temp dir from `$TMPDIR`, falling back to `/tmp` (or `%TEMP%` on Windows), and write to `<tmpdir>/architecture-review-<timestamp>.html` so each run gets a fresh file. Open it for the user (`xdg-open <path>` on Linux, `open <path>` on macOS, `start <path>` on Windows) and tell them the absolute path.
+
+The report uses **local CSS or Crosswind** for layout and styling, and **Mermaid via CDN** for diagrams where a graph/flow/sequence reliably communicates the structure. Mix Mermaid with hand-crafted CSS/SVG visuals: use Mermaid when relationships are graph-shaped (call graphs, dependencies, sequences), and hand-built divs/SVG when you want something more editorial (mass diagrams, cross-sections, collapse animations). Each candidate gets a **before/after visualisation**. Be visual.
+
+For each candidate, render a card with:
+
+- **Files**: which files/modules are involved
+- **Problem**: why the current architecture is causing friction
+- **Solution**: plain English description of what would change
+- **Benefits**: explained in terms of locality and leverage, and how tests would improve
+- **Before / After diagram**: side-by-side, custom-drawn, illustrating the shallowness and the deepening
+- **Recommendation strength**: one of `Strong`, `Worth exploring`, `Speculative`, rendered as a badge
+
+End the report with a **Top recommendation** section: which candidate you'd tackle first and why.
+
+**Use GLOSSARY.md vocabulary for the domain, and the `/stacks-codebase-design` vocabulary for the architecture.** If `GLOSSARY.md` defines "Order," talk about "the Order intake module," not "the FooBarHandler," and not "the Order service."
+
+**ADR conflicts**: if a candidate contradicts an existing ADR, only surface it when the friction is real enough to warrant revisiting the ADR. Mark it clearly in the card (e.g. a warning callout: _"contradicts ADR-0007, but worth reopening because…"_). Don't list every theoretical refactor an ADR forbids.
+
+See [HTML-REPORT.md](HTML-REPORT.md) for the full HTML scaffold, diagram patterns, and styling guidance.
+
+Do NOT propose interfaces yet. After the file is written, ask the user: "Which of these would you like to explore?"
+
+### 3. Grilling loop
+
+Once the user picks a candidate, call the Skill tool with "stacks-grilling" to walk the decision tree with them: constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
+
+Side effects happen inline as decisions crystallize; call the Skill tool with "stacks-domain-modeling" to keep the domain model current as you go:
+
+- **Naming a deepened module after a concept not in `GLOSSARY.md`?** Add the term to `GLOSSARY.md`. Create the file lazily if it doesn't exist.
+- **Sharpening a fuzzy term during the conversation?** Update `GLOSSARY.md` right there.
+- **User rejects the candidate with a load-bearing reason?** Offer an ADR, framed as: _"Want me to record this as an ADR so future architecture reviews don't re-suggest it?"_ Only offer when the reason would actually be needed by a future explorer to avoid re-suggesting the same thing; skip ephemeral reasons ("not worth it right now") and self-evident ones.
+- **Want to explore alternative interfaces for the deepened module?** Call the Skill tool with "stacks-codebase-design" and use its design-it-twice parallel sub-agent pattern.

package/ai/skills/stacks-improve-codebase-architecture/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: stacks-improve-codebase-architecture
+description: Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Covers Stacks engineering workflows.
+disable-model-invocation: true
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Improve Codebase Architecture
+
+Read [the Stacks adaptation rules](../stacks-flow/ENGINEERING.md), then
+[PLAYBOOK.md](PLAYBOOK.md). The playbook preserves this workflow's decision
+criteria; the Stacks rules govern APIs, tooling, tracking, and authorization.
+
+Credit: adapted from Matt Pocock's `improve-codebase-architecture` skill, MIT licensed.
+See [NOTICE.md](NOTICE.md) and [LICENSE](LICENSE).
+
+## Completion
+
+Produce the requested behavior or reviewable artifact and satisfy the
+playbook's completion criteria. Preserve existing decisions and user edits.
+Use the native Stacks skills for implementation and verification, and carry
+existing authorization through the workflow.

package/ai/skills/stacks-investigate/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Matt Pocock
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-investigate/NOTICE.md

@@ -0,0 +1,10 @@
+# Source and license
+
+The upstream MIT notice is preserved in [LICENSE](LICENSE).
+
+## diagnosing-bugs
+
+Source: [skills/engineering/diagnosing-bugs/SKILL.md](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/diagnosing-bugs/SKILL.md),
+revision `49dd158d1076134a641b33efb035946536778336`.
+
+Reviewed against the existing Stacks workflow. Stacks API guidance is retained; current workflow changes and supporting references are integrated where applicable.

package/ai/skills/stacks-investigate/SKILL.md

@@ -245,3 +245,9 @@ Required before declaring done:
 
 > **Fix applied.** Run `/stacks-review` to review it, and `/stacks-retro` when
 > the real lesson is that the environment let the bug hide.
+
+## Upstream provenance
+
+The reviewed source revision and MIT notice are in [NOTICE.md](NOTICE.md) and
+[LICENSE](LICENSE). Read [the Stacks adaptation rules](../stacks-flow/ENGINEERING.md)
+with this workflow. Existing Stacks APIs and supporting helpers remain authoritative.

package/ai/skills/stacks-jobs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: stacks-jobs
-description: Use when creating background job classes in app/Jobs/ - job structure, the handle method, job configuration (queue, tries, backoff, timeout, rate), dispatching patterns (dispatch, dispatchIf, dispatchAfter, dispatchNow), or the Every schedule constants. For the queue system internals (workers, batching, events, drivers, testing), see stacks-queue.
+description: Use when creating background job classes in app/Jobs/ - job structure, the handle method, job configuration (queue, tries, backoff, timeout, rate), dispatching patterns (dispatch, dispatchIf, dispatchAfter, dispatchNow), or the Every schedule constants. For the queue system internals (workers, batching, events, drivers, testing), see stacks-queue. Covers app/Jobs, the native Job class and typed by-name dispatch.
 license: MIT
 compatibility: Bun >= 1.3.0, TypeScript
 allowed-tools: Read Edit Write Bash Grep Glob
@@ -45,7 +45,7 @@ export default new Job({
   description?: string       // human-readable description
   queue?: string             // queue name (default: 'default')
   tries?: number             // max retry attempts
-  backoff?: number           // seconds between retries
+  backoff?: number | number[] // seconds between retries
   backoffConfig?: {          // advanced backoff
     strategy: 'fixed' | 'exponential' | 'linear'
     initialDelay: number
@@ -54,7 +54,7 @@ export default new Job({
     jitter?: { enabled: boolean, factor: number }
   }
   timeout?: number           // max seconds per attempt
-  rate?: string              // cron schedule (e.g., Every.Hour)
+  rate?: string              // schedule, e.g. Every.Hour; use an explicit schedule for custom policy
   enabled?: boolean          // enable/disable job
   handle: (payload?) => any  // job logic
 }
@@ -99,7 +99,7 @@ await job('SendWelcomeEmail', { email, name })
 Use the `rate` property for automatic scheduling:
 
 ```typescript
-import { Every } from '@stacksjs/enums'
+import { Every } from '@stacksjs/types'
 
 export default new Job({
   name: 'CleanupExpiredTokens',
@@ -129,11 +129,32 @@ buddy queue                  # queue management
 ```
 
 ## Gotchas
-- Jobs must export `default new Job({...})` — not a plain object
+- Prefer `default new Job({...})` for dispatch methods. Discovery also supports default objects with handle and class exports with a handle method
 - The `handle()` method receives the payload passed to `dispatch()`
-- `dispatchNow()` runs immediately in the current process — no queue involved
-- Default queue driver is `sync` — jobs run immediately unless changed to `database` or `redis`
+- `dispatchNow()` runs immediately in the current process - no queue involved
+- Default queue driver is `sync` - jobs run immediately unless changed to `database` or `redis`
 - Jobs with `rate` are auto-discovered by the scheduler
 - Backoff array `[10, 30, 60]` means: retry after 10s, then 30s, then 60s
-- Jobs should be idempotent — safe to retry on failure
+- Jobs should be idempotent - safe to retry on failure
 - For queue workers, batching, events, and testing, see the `stacks-queue` skill
+
+
+## Durable dispatch and context
+
+The fluent `job(name, payload)` builder checks job names and payloads against
+the generated registry. `.withContext(context)` passes a second argument to
+the handler; JSON serialization applies to both payload and context on a durable
+driver. `.withIdempotencyKey(key)` claims a persistent dispatch key.
+Inside `db.transaction()` dispatch defers until commit by default;
+`.afterCommit()` states that intent, and `.withoutCommit()` explicitly opts
+out. Outside a transaction, afterCommit warns and dispatches immediately.
+See `stacks-queue` for the complete envelope and batch lifecycle.
+
+Scheduling a named job through `schedule.job()` runs it in the scheduler by
+default. Chain `.onQueue(name)` to dispatch it through the configured queue;
+durable drivers require a worker. The explicit Scheduler entry wins over a
+job's rate in runScheduler, so keep the policy in that explicit registration.
+Source: `core/queue/src/job.ts`,
+`action.ts`, `discovery.ts` and `core/scheduler/src/schedule.ts`.
+Tests: `core/queue/tests/job-context.test.ts`,
+`job-declared-retries.test.ts` and `job-payload.test-d.ts`.

package/ai/skills/stacks-listeners/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: stacks-listeners
-description: Use when creating event listeners in app/Listeners/ - the listener file structure, registering listeners in app/Events.ts, the listener-to-action mapping pattern, CLI event listeners in Console.ts, or debugging listener execution. For the event system API (dispatch, listen, emitter, model events), see stacks-events.
+description: Use when creating event listeners in app/Listeners/ - the listener file structure, registering listeners in app/Events.ts, the listener-to-action mapping pattern, CLI event listeners in Console.ts, or debugging listener execution. For the event system API (dispatch, listen, emitter, model events), see stacks-events. Covers app/Listeners, app/Events.ts and native listener discovery.
 license: MIT
 compatibility: Bun >= 1.3.0, TypeScript
 allowed-tools: Read Edit Write Bash Grep Glob
@@ -118,12 +118,20 @@ export default function(cli: CLI) {
 }
 ```
 
-Listeners execute sequentially (not in parallel) — each awaits completion.
+Handlers are invoked in registration order. `dispatch()` does not await async completion. Use `dispatchAsync()` to wait sequentially or `dispatchAndCollect()` to observe each failure.
 
 ## Gotchas
-- Listeners are Action names, not file paths — `'SendWelcomeEmail'` resolves to `app/Actions/SendWelcomeEmail.ts`
+- Map values are listener names, resolved in app/Listeners before app/Actions, then framework defaults
 - The action must have a `handle(event)` method
-- Listeners run sequentially per event — order in the array matters
-- Action modules are cached after first load — no hot-reload for listeners
+- Listener invocation follows registration order; awaiting completion depends on the dispatch API. Read stacks-events before chaining side effects
+- Action modules are cached after first load - no hot-reload for listeners
 - CLI listeners are separate from HTTP event listeners
 - For the event API (dispatch, listen, emitter), see the `stacks-events` skill
+
+
+## Source and evidence
+
+`storage/framework/core/events/src/discover.ts` owns discovery, map registration
+and handler adaptation. Retained tests: `core/events/tests/register.test.ts`,
+`listener.test.ts` and `boot.test.ts`. A standalone defineListener handle takes
+`(payload, eventName)`; a raw bus glob handler takes `(eventName, payload)`.

package/ai/skills/stacks-logging/SKILL.md

@@ -8,71 +8,74 @@ allowed-tools: Read Edit Write Bash Grep Glob
 
 # Stacks Logging
 
-Uses @stacksjs/clarity Logger with file writing to `storage/logs/stacks.log`.
-
-## Key Paths
-- Core package: `storage/framework/core/logging/src/`
-- Configuration: `config/logging.ts`
-- Log model: `storage/framework/defaults/app/Models/Log.ts`
-- Log file: `storage/logs/stacks.log`
-
-## Log Facade
-
-```typescript
-import { log } from '@stacksjs/logging'
-
-await log.info('User created', { userId: 1 })
-await log.success('Deployment complete')
-await log.warn('Rate limit approaching', { remaining: 10 })
-await log.warning('Alias for warn')
-await log.error(new Error('Something failed'), { context: 'handler' })
-await log.debug('Debug info', { query: 'SELECT ...' })
-```
-
-### Error with Exit
-```typescript
-await log.error(err, { shouldExit: true })  // logs and exits process
-```
-
-## Dump & Die
-
-```typescript
-import { dump, dd, echo } from '@stacksjs/logging'
-
-await dump(variable1, variable2)    // inspect without stopping
-await dd(variable1, variable2)      // inspect and exit (never returns)
-await echo('simple output')
-```
-
-## Timing
-
-```typescript
-const done = log.time('database-query')
-await performQuery()
-await done()  // logs elapsed time
-```
-
-## Logger Instance
-
-```typescript
-import { logger } from '@stacksjs/logging'
-
-const l = logger  // underlying clarity Logger instance
-```
-
-## config/logging.ts
-```typescript
-{
-  logsPath: 'storage/logs',
-  deploymentsPath: 'storage/logs/deployments'
-}
-```
-
-## Gotchas
-- All log methods are async — they write to both console and file
-- Log file is at `storage/logs/stacks.log`
-- `dd()` never returns — it exits the process after dumping
-- `dump()` continues execution — use for non-destructive debugging
-- The Log model enables database-backed log storage and querying
-- Error logging can optionally exit the process with `shouldExit: true`
-- Logging is a dependency of many other packages — it's available everywhere
+Use the native log facade, request context and transports. Console output,
+local files, remote log shipping and exception reporting are separate sinks.
+
+## Calls and context
+
+~~~ts
+import { log, withLogContext } from '@stacksjs/logging'
+
+await withLogContext({ requestId: 'request-7', userId: 7 }, async () => {
+  await log.info('Order created', { orderId: 42 })
+})
+~~~
+
+info/debug accept multiple arguments; success accepts a message; warn(message,
+context?) and warning(message) are aliases with different signatures.
+Prefer log.error(message, error?, context?) so Error name/message/stack/cause
+are retained. withLogContext uses an async scope; getLogContext reads it.
+Do not hold one user's context in a global object for later requests.
+
+log.time(label) returns an async completion callback accepting optional metadata.
+logger() is an async function returning the underlying clarity Logger, not an
+exported instance. dump/dd/echo are async inspection helpers; dd exits after
+inspection and does not belong in a serving request path.
+
+## Shutdown and synchronous paths
+
+Ordinary log methods return promises. struct.request/query/slowQuery/job and
+other structured helpers queue tracked writes and return void. Use log.flush()
+before an explicit exit to drain writes, transport buffers and error reporters.
+The native beforeExit hook drains once on natural shutdown; process.exit bypasses
+that opportunity. log.exit(message?, code?) flushes before exiting.
+
+syncWarn/syncError write synchronously; fatal(message, code?) synchronously
+prints and exits. Legacy shouldExit error options remain compatibility behavior;
+use the explicit exit API for a CLI and return/throw from an HTTP action instead.
+
+## Levels, formats and destinations
+
+Effective settings resolve env override, then config, then framework default.
+parseLogLevel/currentLevel use debug/info/success/warning/error (warn aliases
+warning). LOG_FORMAT chooses text/json; resolveLogSettings supports configured
+format/file-writing options. Read config/logging.ts rather than inventing a
+separate severity vocabulary from another logger.
+
+Default local logs live under storage/logs; selected file paths and runtime
+fallbacks come from the logger/config. The Log model does not automatically make
+every log call a database insert. normalizeError/normalizeContext retain embedded
+Error detail and bound cause traversal; they are not secret redaction policies.
+
+registerTransport(transport) returns a detach function; transports() returns a
+copy. A LogTransport has name, log(record), optional level and flush(). log must
+return immediately; buffer external I/O and drain it through flush. Records retain
+args and scoped context before formatting. Transport exceptions are contained
+and reported once, so logging a failure does not throw a second one at the caller.
+
+LogHQ transport is exported from `@stacksjs/logging/loghq`. config/logging.ts
+uses LOGHQ_KEY/project/baseUrl and initializeIntegration; the shared environment
+gate normally allows production/staging. Credentials alone do not justify sending
+local or CI telemetry. BugHQ reporters are a separate error-reporting sink.
+
+report(error, options?) is the framework exception chokepoint: ordinary 4xx are
+debug diagnostics; server failures reach captureError and log.error. Duplicate
+Error identity is deduplicated at the reporter layer. See stacks-error-handling.
+
+## Source and verification
+
+Public narrow runtime: `@stacksjs/logging/runtime`. Implementation:
+`storage/framework/core/logging/src/index.ts` and loghq.ts.
+Tests under core/logging/tests: trace-context.test.ts, transports.test.ts,
+level-filtering.test.ts, context-normalization.test.ts, beforeexit-drain.test.ts,
+exit-flushes.test.ts and loghq.test.ts.