@ancleto/spec 0.6.24 → 0.6.25

package/agents/coder.md

@@ -151,6 +151,8 @@ After implementation, return a short structured summary including:
 - whether escalation was required due to broader-than-approved impact
 - blockers, conflicts, or escalations if any
 
+**Output cap**: summary max 12 lines. At most 5 risky edges or test scenarios; offer the rest on request. Reference code as `file:line` instead of pasting code or logs.
+
 ## Important
 
 - Do NOT add features not defined in the approved request or aspec change

package/agents/context-resolver.md

@@ -93,6 +93,8 @@ Return the card as structured context for the orchestrator:
 
 The command already replaces HTML markup with whitespace and unwraps long lines; if any markup survives, replace it with whitespace rather than dropping it.
 
+**Output cap**: 3 lines plus the card payload — the description and acceptance criteria are the only unbounded fields and must stay complete; no commentary, analysis, or implementation advice.
+
 ## Failure handling
 
 - If no work item reference was provided, report "no work item to resolve" and fetch nothing.

package/agents/documenter.md

@@ -147,6 +147,8 @@ After completing the finalization step, return a short structured summary includ
 - whether the original active change directory was fully removed (`Change Archive` mode)
 - any blockers or missing inputs
 
+**Output cap**: summary max 10 lines; spec, archive, and artifact lists as paths only — never restate spec content.
+
 ## Important
 
 - Do not invent additional documentation requirements

package/agents/memory-keeper.md

@@ -139,6 +139,8 @@ Whoever recalls this in six months has no session to attach it to, so it reads a
 - User-Approved Record: the tool used, `memory_key`, the exact approved `content` as stored, and whether it superseded a previous entry
 - Any failure of the memory engine, reported plainly so `@orchestrator` can continue without memory
 
+**Output cap**: max 6 lines; the stored entry is the only unbounded field — everything else is one line.
+
 ## Important
 
 - You never modify code, specs, or repository state.

package/agents/orchestrator.md

@@ -291,6 +291,17 @@ Before advancing to the next stage, verify that each subagent returned a usable
 
 For each validation command in the tester result, including format check and lint, preserve a Validation Ledger entry with: command, outcome (`passed`, `task-regression`, `pre-existing-unrelated`, or `inconclusive`), and related files when it failed. Pass it unchanged to `@reviewer`. A confirmed `pre-existing-unrelated` result is reported once in the final status as a non-blocking residual limitation; do not stop, re-run it, or request a correction unless a later relevant change invalidates that classification.
 
+### Handling subagent returns
+
+A subagent return is a payload to distill, not a message to forward. Before the next stage:
+
+- Extract only the fields the next stage needs: `task-owned files`, Validation Ledger entries, flags (`SPEC UPDATE RECOMMENDED`, `SEED_ACTION_REQUIRED`), verdicts, blockers, and card context when relevant.
+- Never copy a subagent's raw return — prose, logs, diffs, or command output — into the next delegation or the final report; pass distilled fields only.
+- The caps declared in each agent's output section bound its return. If a return exceeds them, summarize it and keep the detail only for the current stage; offer the full detail only if the user asks.
+- Evidence survives as fields, not as text: `file:line` for code, ledger entries for commands, flags for decisions.
+
+**Output cap**: the final report to the user max 15 lines — status, changed paths, validation result, blockers; never paste subagent returns, logs, or diffs.
+
 ### Expected output from `@context-resolver`
 
 - The resolved card: id, title, work item type, and project

package/agents/reviewer.md

@@ -165,6 +165,8 @@ Return a short structured report with:
 - missing or inconclusive command evidence that requires focused verification by `@tester`, or "none"
 - overall review verdict
 
+**Output cap**: at most 5 findings per severity (`CRITICAL`, `WARNING`, `SUGGESTION`); if more exist, keep the 5 highest-impact and state the count of the rest, offering detail on request. `Summary` max 5 lines. Cite `file:line`; never paste diffs or code.
+
 Use this format:
 
 ```md

package/agents/spec-writer.md

@@ -96,6 +96,8 @@ After writing the artifacts, respond with a short structured summary including:
 - short scope summary
 - open questions, assumptions, or risks
 
+**Output cap**: summary max 10 lines; at most 5 open questions, assumptions, or risks combined (offer the rest on request); paths only — never restate artifact content.
+
 ## Important
 
 - Prefer the smallest correct aspec change that captures the intended behavior

package/agents/technical-discovery.md

@@ -132,3 +132,5 @@ When you were delegated, do not address the developer as if they had called you:
   include the required `SEED_ACTION_REQUIRED` marker.
 - When mentioning credentials, name the variable, key, or file and **never** reproduce its value.
 - Be concise: orientation the caller can act on, not an inventory.
+
+**Output cap**: prose max 15 lines; required state or check reports are payload and stay complete; cite paths instead of pasting content.

package/agents/technical-seed-writer.md

@@ -49,8 +49,13 @@ action was explicitly requested, run `ancleto discovery --check` once and read i
    `config.outputDir`, including `units/_map.md`. Use the same pack for any optional dossier.
 4. Run `ancleto discovery --check` once to validate the written seed. This is state-only: do
    not generate another pack after it.
-5. Return the output directory, files created or updated, the single pack path, final state,
-   and any evidence limitations recorded in `unknowns.md`.
+5. Return the result as specified in `## Output`.
 
 If the pack fails, writing fails, or the final state is not usable, report the exact blocker;
 do not claim the seed was generated.
+
+## Output
+
+- The output directory, the files created or updated, the single pack path, the final state, and any evidence limitations recorded in `unknowns.md`.
+
+**Output cap**: max 8 lines — paths only; never paste file contents or the pack.

package/agents/tester.md

@@ -167,6 +167,8 @@ After validation, return a short structured summary including:
 - failed verification items, if any
 - untested gaps or assumptions, if any
 
+**Output cap**: Validation Ledger entries are one line each — never paste command output; collapse repeated `passed` runs of the same command into one line with a count; keep at most 15 lines, preserving every failure and every task-owned test result. Summary max 10 lines; offer full detail on request.
+
 ## Important
 
 - Prefer the smallest useful test change that validates the approved behavior

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ancleto/spec",
-  "version": "0.6.24",
+  "version": "0.6.25",
   "description": "Orquestador SDD liviano con subagentes optimizados para costo/tokens",
   "type": "module",
   "bin": {