@jaimevalasek/aioson 1.28.0 → 1.29.1

package/template/.aioson/docs/dev/stack-conventions.md

@@ -1,5 +1,8 @@
 ---
 description: "Dev stack conventions — Laravel, UI/UX, design skill, motion, Web3, and any-stack separation rules."
+agents: [dev, deyvin]
+task_types: [implementation, conventions]
+triggers: [stack conventions, framework patterns, implementing features]
 ---
 
 # Dev Stack Conventions

package/template/.aioson/docs/deyvin/continuity-recovery.md

@@ -1,24 +1,27 @@
 ---
 description: "Deyvin continuity recovery — session start order, resumption rules, brownfield guardrails, SDD bridge, and Git fallback."
+agents: [deyvin]
+task_types: [continuity, recovery]
+triggers: [continuity recovery, recent work, stale state]
 ---
 
 # Deyvin Continuity Recovery
 
-Load this module only when the task is continuity recovery, recent-work reconstruction, stale-state diagnosis, or resuming an existing slice.
+Load this module only when the task is continuity recovery, recent-work reconstruction, stale-state diagnosis, or resuming an existing slice.
 
 ## Session start order
 
-Build context in this order:
-
-1. If `aioson` is available, run `aioson memory:summary . --last=5` as the fast continuity bootstrap.
-2. Read `.aioson/context/project.context.md`
-3. Run `aioson context:select . --agent=deyvin --mode=planning --task="<task>" --paths="<known paths>"`.
-4. Load only the selected PLANNING files. Do not load full `.aioson/rules/`, `.aioson/docs/`, `.aioson/design-docs/`, `discovery.md`, or `architecture.md` from this step alone.
-5. If a feature slug is known, load its dossier/spec only when `context:select`, `dev-state.md`, or `project-pulse.md` points to that slug; use `spec-current.md` for active spec and `spec-history.md` only for history.
-6. If code inspection/editing is about to start, run `aioson context:select . --agent=deyvin --mode=executing --task="<task>" --paths="<files to touch>"` and load only the selected EXECUTING files.
-7. When the task matches procedural tags, run `aioson brain:query . --tags=<tags> --min-quality=4`.
-8. Inspect recent runtime state in `.aioson/runtime/aios.sqlite` when memory summary is insufficient.
-9. Use Git only as a fallback after memory + runtime + selected rules/docs.
+Build context in this order:
+
+1. If `aioson` is available, run `aioson memory:summary . --last=5` as the fast continuity bootstrap.
+2. Read `.aioson/context/project.context.md`
+3. Run `aioson context:select . --agent=deyvin --mode=planning --task="<task>" --paths="<known paths>"`.
+4. Load only the selected PLANNING files. Do not load full `.aioson/rules/`, `.aioson/docs/`, `.aioson/design-docs/`, `discovery.md`, or `architecture.md` from this step alone.
+5. If a feature slug is known, load its dossier/spec only when `context:select`, `dev-state.md`, or `project-pulse.md` points to that slug; use `spec-current.md` for active spec and `spec-history.md` only for history.
+6. If code inspection/editing is about to start, run `aioson context:select . --agent=deyvin --mode=executing --task="<task>" --paths="<files to touch>"` and load only the selected EXECUTING files.
+7. When the task matches procedural tags, run `aioson brain:query . --tags=<tags> --min-quality=4`.
+8. Inspect recent runtime state in `.aioson/runtime/aios.sqlite` when memory summary is insufficient.
+9. Use Git only as a fallback after memory + runtime + selected rules/docs.
 
 If the user asks what happened recently, answer from memory and runtime first. Go to Git only if those sources are insufficient.
 
@@ -35,12 +38,12 @@ Do not duplicate or rewrite the shared SDD references inside `@deyvin`.
 
 ## Brownfield guardrails
 
-If `framework_installed=true` in `project.context.md` and the task depends on existing system behavior:
-
-- prefer selected module memory, `memory-index.md`, dossier, or spec before opening broad `discovery.md` / `architecture.md`
-- use `skeleton-system.md` or `memory-index.md` first for faster orientation
-- if `discovery.md` is missing but scan artifacts exist, stop and hand off to `@analyst`
-- if broad architecture decisions are required, hand off to `@architect`
+If `framework_installed=true` in `project.context.md` and the task depends on existing system behavior:
+
+- prefer selected module memory, `memory-index.md`, dossier, or spec before opening broad `discovery.md` / `architecture.md`
+- use `skeleton-system.md` or `memory-index.md` first for faster orientation
+- if `discovery.md` is missing but scan artifacts exist, stop and hand off to `@analyst`
+- if broad architecture decisions are required, hand off to `@architect`
 
 ## Git fallback
 

package/template/.aioson/docs/deyvin/debugging-escalation.md

@@ -1,5 +1,8 @@
 ---
 description: "Deyvin debugging and escalation — root-cause protocol, retry limits, and when to hand off."
+agents: [deyvin]
+task_types: [debugging, bugfix]
+triggers: [bug diagnosis, failing test, debugging escalation]
 ---
 
 # Deyvin Debugging and Escalation

package/template/.aioson/docs/deyvin/pair-execution.md

@@ -1,5 +1,8 @@
 ---
 description: "Deyvin pair execution — working mode, small-slice loop, memory updates, and implementation governance."
+agents: [deyvin]
+task_types: [implementation, pair-session]
+triggers: [pair execution, small slice, polish]
 ---
 
 # Deyvin Pair Execution

package/template/.aioson/docs/deyvin/runtime-handoffs.md

@@ -1,5 +1,8 @@
 ---
 description: "Deyvin runtime and handoffs — tracked session behavior, live milestones, direct sessions, and dashboard visibility."
+agents: [deyvin]
+task_types: [runtime, handoff]
+triggers: [live session, runtime handoff, tracked session]
 ---
 
 # Deyvin Runtime and Handoffs

package/template/.aioson/docs/dossier/agent-templates.md

@@ -1,5 +1,8 @@
 ---
 description: "Templates concretos por agente da cadeia (9 chain agents) para escrita no dossier via dossier:add-finding, dossier:add-codemap, dossier:link-rule e dossier:add-research. Bumped Phase 4 (agent-chain-continuity): @sheldon override (Why → Agent Trail + Research Index); novos templates para @ux-ui, @pm, @orchestrator; convenção DRIFT: para @dev."
+agents: [product, analyst, sheldon, architect, pm, dev, qa, tester, briefing]
+task_types: [dossier]
+triggers: [dossier, agent trail, add finding]
 ---
 
 # Agent Dossier Templates

package/template/.aioson/docs/dossier/schema.md

@@ -1,5 +1,8 @@
 ---
 description: "Feature dossier schema (canônico v1.0 + v1.1 Phase 3 + v1.2 Research Index) e handoff-protocol artifact_uris v2. Lido por src/dossier/schema.js e src/session-handoff.js — toda mudança aqui exige bump de schema_version."
+agents: [product, analyst, sheldon, architect, pm, dev, qa, tester, briefing]
+task_types: [dossier]
+triggers: [dossier schema, dossier structure]
 ---
 
 # Feature Dossier — Schema canônico

package/template/.aioson/docs/example-external-api-context.md

@@ -1,5 +1,7 @@
 ---
 description: "Template for documenting an external API integration context — replace with real content"
+task_types: [integration]
+triggers: [external api, integration context]
 scope: "global"
 agents: []
 ---

package/template/.aioson/docs/handoff-persistence.md

@@ -1,94 +1,96 @@
----
-description: "Persist context to plans/{slug}.md before suggesting /clear in a cross-session handoff — preserves the diagnostic so the next agent works from an artifact, not from chat memory."
----
-
-# Handoff Persistence
-
-Load this when you are about to issue a routing recommendation that involves `/clear`, a fresh terminal, or any other context boundary that drops the current conversation. Same-session handoffs (the next agent inherits the same chat) do not need this — skip the doc.
-
-## The problem
-
-A routing agent (`@neo`, `@deyvin`) ends a session by suggesting:
-1. `/agent` — activate the next agent
-2. `/clear` — fresh context window before continuing
-
-If the recommendation depends on diagnostic work done in this session (file reads, line numbers, decisions made, options weighed), and the user runs `/clear` first, **all of that context is lost**. The next agent reads only the seed prompt the user types — which can never capture the nuance of the actual diagnostic.
-
-A seed prompt is a memory of a conversation. An artifact is a memory of work.
-
-## The rule
-
-Before suggesting `/clear` to the user, persist the actionable diagnostic to `plans/{slug}.md` at the project root. Then the recommendation becomes:
-
-```
-1. Activate /briefing (or /product / /architect / …)
-2. /clear is safe — the next agent reads plans/{slug}.md
-```
-
-`plans/` is the canonical input directory for `/aioson:agent:briefing` (and a useful seed for `/aioson:agent:product` too). The directory may not exist yet — create it.
-
-## When to apply
-
-| Situation | Persist? |
-|---|---|
-| Handoff routes to an agent that takes raw plans (`/aioson:agent:briefing` first and foremost, sometimes `/aioson:agent:product`) | Yes |
-| Handoff routes to an agent that needs a discovery pass (`/aioson:agent:analyst`, `/aioson:agent:architect`, `/aioson:agent:sheldon`) | Yes — they read context from `.aioson/context/` AND from raw plans |
-| Same-session continuation (`/aioson:agent:dev` keeps going, `/aioson:agent:qa` reviews implementation just done) | No — context is in chat |
-| Handoff happens via tracked live session (`aioson live:handoff`) | No — telemetry already carries the trail |
-| Trivial routing ("you want `/aioson:agent:setup` first") with no diagnostic to preserve | No |
-
-## What to write
-
-Structure of `plans/{slug}.md` (lightweight — `/aioson:agent:briefing` will enrich it):
-
-```md
-# {Short title} — raw plan
-
-> Status: raw input for /{next-agent}. Generated {date} during a /{this-agent} session.
-
-## Why this exists
-1-2 paragraphs framing the problem in the user's terms.
-
-## Symptoms observed
-Concrete pinned facts: line numbers, file paths, command outputs. Not opinions.
-
-## What's already delivered
-If part of the work landed in this session, name the commits/files.
-
-## Proposed scope (if applicable)
-Layers / phases / options the next agent should consider. Mark recommendations.
-
-## Open decisions for the next agent to surface
-Questions that need user input but were out of scope for this session.
-
-## Pointers
-Files, commits, line numbers, related plans/. The next agent reads these directly.
-
-## Out of scope
-What you deliberately did NOT cover. Prevents the next agent from re-litigating.
-```
-
-Slug rules: kebab-case, descriptive, unique inside `plans/`. Examples: `lay-user-agent-mode.md`, `payment-integration.md`, `auth-rewrite-rfc.md`. Avoid generic names like `notes.md` or `plan.md`.
-
-## What to tell the user
-
-After persisting, end with a clear handoff block. Example:
-
-```
-## Next Up
-- Routed to: /briefing
-- Activate: /briefing
-- Context persisted: plans/lay-user-agent-mode.md
-- /clear is safe — the next agent reads from the file
-
-Session artifacts written:
-- [x] plans/lay-user-agent-mode.md
-- [x] {any other files this session produced}
-```
-
-## Anti-patterns
-
-- **Inlining 2 KB of diagnostic as a "seed prompt" in the routing message.** The user shouldn't have to copy-paste a wall of text. Persist it.
-- **Persisting trivial routings.** A user who asks "what does `/aioson:agent:setup` do" doesn't need a `plans/` file written. Apply the table above.
-- **Persisting code archaeology.** Code lives in code; reading recommendations live in the artifact only when they would otherwise be lost across `/clear`.
-- **Forgetting to mention the file.** If you wrote `plans/{slug}.md` but the handoff message doesn't reference it, the user won't know to read it (or to let the next agent read it).
+---
+description: "Persist context to plans/{slug}.md before suggesting /clear in a cross-session handoff — preserves the diagnostic so the next agent works from an artifact, not from chat memory."
+task_types: [handoff]
+triggers: [handoff, session persistence, last handoff]
+---
+
+# Handoff Persistence
+
+Load this when you are about to issue a routing recommendation that involves `/clear`, a fresh terminal, or any other context boundary that drops the current conversation. Same-session handoffs (the next agent inherits the same chat) do not need this — skip the doc.
+
+## The problem
+
+A routing agent (`@neo`, `@deyvin`) ends a session by suggesting:
+1. `/agent` — activate the next agent
+2. `/clear` — fresh context window before continuing
+
+If the recommendation depends on diagnostic work done in this session (file reads, line numbers, decisions made, options weighed), and the user runs `/clear` first, **all of that context is lost**. The next agent reads only the seed prompt the user types — which can never capture the nuance of the actual diagnostic.
+
+A seed prompt is a memory of a conversation. An artifact is a memory of work.
+
+## The rule
+
+Before suggesting `/clear` to the user, persist the actionable diagnostic to `plans/{slug}.md` at the project root. Then the recommendation becomes:
+
+```
+1. Activate /briefing (or /product / /architect / …)
+2. /clear is safe — the next agent reads plans/{slug}.md
+```
+
+`plans/` is the canonical input directory for `/aioson:agent:briefing` (and a useful seed for `/aioson:agent:product` too). The directory may not exist yet — create it.
+
+## When to apply
+
+| Situation | Persist? |
+|---|---|
+| Handoff routes to an agent that takes raw plans (`/aioson:agent:briefing` first and foremost, sometimes `/aioson:agent:product`) | Yes |
+| Handoff routes to an agent that needs a discovery pass (`/aioson:agent:analyst`, `/aioson:agent:architect`, `/aioson:agent:sheldon`) | Yes — they read context from `.aioson/context/` AND from raw plans |
+| Same-session continuation (`/aioson:agent:dev` keeps going, `/aioson:agent:qa` reviews implementation just done) | No — context is in chat |
+| Handoff happens via tracked live session (`aioson live:handoff`) | No — telemetry already carries the trail |
+| Trivial routing ("you want `/aioson:agent:setup` first") with no diagnostic to preserve | No |
+
+## What to write
+
+Structure of `plans/{slug}.md` (lightweight — `/aioson:agent:briefing` will enrich it):
+
+```md
+# {Short title} — raw plan
+
+> Status: raw input for /{next-agent}. Generated {date} during a /{this-agent} session.
+
+## Why this exists
+1-2 paragraphs framing the problem in the user's terms.
+
+## Symptoms observed
+Concrete pinned facts: line numbers, file paths, command outputs. Not opinions.
+
+## What's already delivered
+If part of the work landed in this session, name the commits/files.
+
+## Proposed scope (if applicable)
+Layers / phases / options the next agent should consider. Mark recommendations.
+
+## Open decisions for the next agent to surface
+Questions that need user input but were out of scope for this session.
+
+## Pointers
+Files, commits, line numbers, related plans/. The next agent reads these directly.
+
+## Out of scope
+What you deliberately did NOT cover. Prevents the next agent from re-litigating.
+```
+
+Slug rules: kebab-case, descriptive, unique inside `plans/`. Examples: `lay-user-agent-mode.md`, `payment-integration.md`, `auth-rewrite-rfc.md`. Avoid generic names like `notes.md` or `plan.md`.
+
+## What to tell the user
+
+After persisting, end with a clear handoff block. Example:
+
+```
+## Next Up
+- Routed to: /briefing
+- Activate: /briefing
+- Context persisted: plans/lay-user-agent-mode.md
+- /clear is safe — the next agent reads from the file
+
+Session artifacts written:
+- [x] plans/lay-user-agent-mode.md
+- [x] {any other files this session produced}
+```
+
+## Anti-patterns
+
+- **Inlining 2 KB of diagnostic as a "seed prompt" in the routing message.** The user shouldn't have to copy-paste a wall of text. Persist it.
+- **Persisting trivial routings.** A user who asks "what does `/aioson:agent:setup` do" doesn't need a `plans/` file written. Apply the table above.
+- **Persisting code archaeology.** Code lives in code; reading recommendations live in the artifact only when they would otherwise be lost across `/clear`.
+- **Forgetting to mention the file.** If you wrote `plans/{slug}.md` but the handoff message doesn't reference it, the user won't know to read it (or to let the next agent read it).

package/template/.aioson/docs/pentester/app-playbooks.md

@@ -1,5 +1,8 @@
 ---
 description: "Pentester deep playbooks for app_target surfaces TS-A01..A07 — IDOR/BOLA, secrets/crypto, injection/XSS, race/insecure design, auth/rate-limit. Load when review_contract.target_mode = app_target."
+agents: [pentester]
+task_types: [security, pentest]
+triggers: [pentest, app target, security review]
 ---
 
 # Pentester — App Target Playbooks