@gtrabanco/pi-agentic-workflow 0.15.0 → 0.15.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gtrabanco/pi-agentic-workflow",
-  "version": "0.15.0",
+  "version": "0.15.2",
   "description": "Pi package: canonical agentic-workflow skills, friendly slash commands, and per-command model routing.",
   "keywords": [
     "pi-package",
@@ -57,11 +57,11 @@
   },
   "dependencies": {
     "@earendil-works/pi-tui": "0.87.0",
-    "@gtrabanco/agentic-workflow": "file:../agentic-workflow",
+    "@gtrabanco/agentic-workflow": "0.1.1",
     "@gtrabanco/agentic-workflow-schema": "4.5.0"
   },
   "devDependencies": {
     "@types/node": "24.13.3",
-    "typescript": "6"
+    "typescript": "6.0.3"
   }
 }

package/skills/workflow-status/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: workflow-status
 user-invocable: true
-version: 3.8.1
+version: 3.9.0
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
-argument-hint: "[--json-only] [--last-envelope <json|path>]"
+argument-hint: "[--json-only] [--last-envelope <json|path>] [--compact]"
 description: >
   Read-only workflow sensor: run the deterministic script, read the fixed
   machine envelope, interpret the recommendation. Never edits. Triggers:
@@ -25,9 +25,9 @@ report — it never assembles the envelope by hand.
 
 ```
 ✓ The script was RUN — `bun scripts/workflow-status.mjs [--json-only]
-  [--last-envelope <json|path>]` (node is the fallback when bun is absent, per
-  the repository's runtime convention); the envelope is the script's stdout, never
-  assembled by the model
+  [--last-envelope <json|path>] [--compact]` (node is the fallback when bun is
+  absent, per the repository's runtime convention); the envelope is the script's
+  stdout, never assembled by the model
 ✓ Nothing was edited, committed, pushed, or created — read-only, always
 ✓ `next.recommended` is non-bare (carries the unit's slug/NN, never a bare
   `/plan-feature`) AND the script computed it from the unit's resolved status
@@ -51,6 +51,12 @@ report — it never assembles the envelope by hand.
 
 With `--json-only`, skip the human-readable summary: print the envelope alone.
 
+## Compact mode — `--compact`
+
+`--compact` emits the same envelope with repository history dropped (~half the
+bytes on a mature repo); the exact keep/drop set is in
+[envelope fields](references/ENVELOPE_FIELDS.md).
+
 ## When to use
 
 - Between orchestration steps: an external driver runs it to decide the next

package/skills/workflow-status/references/ENVELOPE_FIELDS.md

@@ -88,3 +88,38 @@ fully in `features`/`fixes` — an `idea` unit appears ONLY in
 it has no deps-met check to pass (design precedes dependency startability).
 `05-auth` above illustrates `defined` (not yet `planned`): startable, next
 `/plan-feature`, phase fields null (no planning artifacts yet).
+
+## The `--compact` projection
+
+The envelope above is the complete one. `--compact` emits the **same shape and the
+same decisions** with repository history dropped, because a poll loop pays for
+that history in context on every read while no consumer of "what can I do now"
+reads it. On this repository it is roughly half the bytes.
+
+Exactly two fields change:
+
+- `detail.features` / `detail.fixes`: a `done` row is dropped **only on positive
+  proof its linked PR merged** (the merge resolver). An unmerged `done` row is
+  still at the merge gate and stays; every row in `idea`/`defined`/`planned`/
+  `in-progress` stays in both modes, so `detail.startable_now` and
+  `detail.blocked_units` keep naming every unit either way.
+- `findings.fix_now[].route`: the reviewer's multi-paragraph evidence memo becomes
+  `...(N char evidence, see the unit review-findings.md)`, keeping the original
+  length visible. `id`, `file`, `axis`, `severity`, `class` and `suggested_tier`
+  are untouched, and the memo is on disk in the unit's `review-findings.md`, which
+  is where the fold reads it.
+
+`detail.workflow_observations` is **not** reduced in either mode. Every note the
+sensor writes is a signal — an unmapped roadmap status, a slug that refused its
+files, a ledger severity outside the published enum, git and forge state, the
+`--last-envelope` guard's divergence note — and they total about a kilobyte, so
+trimming them would trade a real signal for no measurable win. The size comes from
+`features` and the route memos, which are an order of magnitude larger and pure
+history.
+
+Everything else is byte-identical: `state`, `summary`, `unit`, `phase`, `pr`,
+`gates`, `blockers`, `dependencies`, `recommendations`, `needs_input`, all of
+`next` (`recommended`, `alternatives`, `tier`, `reason`, `candidate_count`,
+`suggested`, `continuation`), `detail.repository_state`, `design_candidates`,
+`pre_execution`, `review_loop_cycles`, `crash_recovery` and `urgent`. A consumer
+may therefore switch modes per read without changing how it parses.