@sentropic/track 0.19.2 → 0.19.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -32,7 +32,7 @@ Two *medium* triggers (moderate cost, partial reversibility, one repo but a shar
|
|
|
32
32
|
|
|
33
33
|
## Step 2 — Gather inputs (full-dossier path)
|
|
34
34
|
|
|
35
|
-
1. **Local context first.** User request; repo entrypoints (`AGENTS.md`, then the host-specific pointer); applicable repo rules; existing track state when `.track/` exists; and **`track report`** (default table: fait / à-faire %·WP / attendus) when track is available. Use your code-search tool to ground claims in the actual code, not memory.
|
|
35
|
+
1. **Local context first.** User request; repo entrypoints (`AGENTS.md`, then the host-specific pointer); applicable repo rules; existing track state when `.track/` exists; and **`track report`** (default table: fait / à-faire %·WP / attendus) when track is available. When showing that report to the human, preserve the table verbatim in a fenced code block. Use your code-search tool to ground claims in the actual code, not memory.
|
|
36
36
|
2. **The double-instruction (standing rule).** For a complex *design* decision, get **independent Codex + Opus passes** via your second-opinion tool before recommending. **Synthesize — do not blend away disagreements.** If a hard-trigger decision lacks the second pass, mark the dossier **Incomplete** and ask whether to wait or proceed provisionally; only reversible prep may continue meanwhile.
|
|
37
37
|
3. **Owner criteria.** Seed from `assets/owner-criteria.template.md`; source the live criteria from the request, repo rules, prior owner decisions, existing track decisions/dossiers, and the `track report` attendus.
|
|
38
38
|
|
|
@@ -28,7 +28,8 @@ items.
|
|
|
28
28
|
|
|
29
29
|
- **`track report --format text`** first for the human-readable default table. Since track 0.19.1 it shows
|
|
30
30
|
the conductor view (FAIT / À-FAIRE %·WP / ATTENDUS) when WPs exist, and falls back to flat buckets in an
|
|
31
|
-
unstructured repo.
|
|
31
|
+
unstructured repo. If presenting this report to the human, paste the raw output verbatim in a fenced code
|
|
32
|
+
block; never rewrite the report table as bullets or prose.
|
|
32
33
|
- **`track report --format json`** for data. It carries the flat `buckets`; when WPs exist/default table is
|
|
33
34
|
active it also carries `wpTree` and `wpTotals`. Each bucket row carries `id`, `title`, `kind`, `bucket`,
|
|
34
35
|
and (when set) `accountable`, `engagementRef`, `role`.
|
|
@@ -65,7 +65,8 @@ Report track results from the verified state, not from memory:
|
|
|
65
65
|
|
|
66
66
|
- Use `track report --format text` for human status. Since track 0.19.1 this prefers the WP/table
|
|
67
67
|
conductor view (FAIT / À-FAIRE %·WP / ATTENDUS) when workpackages exist, and falls back to flat buckets
|
|
68
|
-
in unstructured repos.
|
|
68
|
+
in unstructured repos. **When the user asks for a report/status, paste the raw command output verbatim in
|
|
69
|
+
a fenced code block; do not summarize it, do not convert it to bullets, and do not drop the table layout.**
|
|
69
70
|
- Use `track report --wp` only to force the conductor table explicitly. Use legacy `track report --flat`
|
|
70
71
|
only when the user asks for flat buckets or a downstream script still needs them; treat `--flat` as
|
|
71
72
|
deprecated for human reporting.
|