vouchington-tooling 0.55.0 → 0.57.0
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/README.md +9 -0
- package/dist/gh-api-shell-quoting/logical-line.mjs +14 -74
- package/dist/input-otp-mock/index.d.mts +25 -0
- package/dist/input-otp-mock/index.mjs +34 -0
- package/dist/jsdom-stubs/index.d.mts +12 -0
- package/dist/jsdom-stubs/index.mjs +85 -0
- package/dist/mcp-server/policy-run.d.mts +2 -0
- package/dist/mcp-server/policy-run.mjs +6 -2
- package/dist/mcp-server/policy-spawn.d.mts +1 -0
- package/dist/mcp-server/policy-spawn.mjs +10 -2
- package/dist/next-navigation-mock/index.d.mts +27 -0
- package/dist/next-navigation-mock/index.mjs +58 -0
- package/dist/retrospective-transcript/codex-records.mjs +4 -0
- package/dist/retrospective-transcript/command-prefix.d.mts +1 -0
- package/dist/retrospective-transcript/command-prefix.mjs +1 -1
- package/dist/retrospective-transcript/command-segments.d.mts +1 -1
- package/dist/retrospective-transcript/command-segments.mjs +3 -48
- package/dist/retrospective-transcript/escalations.d.mts +6 -0
- package/dist/retrospective-transcript/escalations.mjs +34 -0
- package/dist/retrospective-transcript/format.mjs +13 -0
- package/dist/retrospective-transcript/index.mjs +2 -1
- package/dist/retrospective-transcript/malformed-record.d.mts +1 -0
- package/dist/retrospective-transcript/malformed-record.mjs +13 -0
- package/dist/retrospective-transcript/shared.d.mts +2 -1
- package/dist/retrospective-transcript/shared.mjs +1 -12
- package/dist/shell-parse/index.d.mts +2 -0
- package/dist/shell-parse/index.mjs +2 -0
- package/dist/shell-parse/shell-command-segments.d.mts +6 -0
- package/dist/shell-parse/shell-command-segments.mjs +26 -0
- package/dist/shell-parse/shell-tokenizer-operators.d.mts +2 -4
- package/dist/shell-parse/shell-tokenizer-operators.mjs +14 -4
- package/dist/shell-parse/shell-tokenizer.d.mts +9 -5
- package/dist/shell-parse/shell-tokenizer.mjs +5 -1
- package/dist/shell-parse/shell-walk.d.mts +8 -0
- package/dist/shell-parse/shell-walk.mjs +62 -0
- package/package.json +29 -1
- package/scripts/__pycache__/run_bounded_process.cpython-312.pyc +0 -0
- package/skills/blackboard/SKILL.md +19 -0
- package/skills/github-issue/SKILL.md +12 -0
- package/skills/manifest.json +20 -20
- package/skills/retrospective/SKILL.md +17 -1
- package/skills/retrospective/references/ci-failures.md +48 -0
- package/skills/retrospective/references/sandbox-audit.md +48 -0
- package/skills/retrospective-distill/SKILL.md +11 -3
- package/skills/retrospective-distill/references/issue-body.md +40 -0
- package/skills/stacked-prs/references/gh-stack.md +5 -1
|
@@ -31,8 +31,10 @@ Use when completed retrospectives or journals should become durable follow-up wo
|
|
|
31
31
|
treating missing records as absent. Require `manifest.schemaVersion` to be 1, `manifest.status`
|
|
32
32
|
to be `"complete"`, a nonempty `cleanupToken`, and manifest counts that exactly match the export
|
|
33
33
|
counts, including the terminal manifest record. Hand subagents only read-only partitions of the
|
|
34
|
-
verified file, never the original snapshot
|
|
35
|
-
|
|
34
|
+
verified file, never the original snapshot. Bound each partition to at most 25 contiguous
|
|
35
|
+
session groups or 1 MiB. A session's record and entries form an indivisible group, so fail the run
|
|
36
|
+
rather than split a group or weaken the bound. Only the root keeps the `cleanupToken`; never
|
|
37
|
+
delegate it. Read full records, with their storage type, repository
|
|
36
38
|
tags, source identity, coverage, and outcomes, from that file. Do not distill from
|
|
37
39
|
`journal_entries`: it reads one session at a time and has no checksum or manifest to show that
|
|
38
40
|
the read is complete. For repository-scoped work, filter sessions by
|
|
@@ -53,8 +55,14 @@ Use when completed retrospectives or journals should become durable follow-up wo
|
|
|
53
55
|
drafting. Skip work that is complete, explicitly rejected, or already covered. A first-party version
|
|
54
56
|
bump is not proof of resolution: verify the adopted change against the original finding before
|
|
55
57
|
deferring. Capture a new observation in the journal before filing it.
|
|
58
|
+
Inspect against the refreshed remote default branch, never the local one, which may sit on an
|
|
59
|
+
unmerged branch. Before filing a claim such as "direct-to-main" or "merged without CI", verify it
|
|
60
|
+
with `git branch -r --contains <sha>` and `git merge-base --is-ancestor <sha> origin/<default>`.
|
|
61
|
+
Prefer a retrospective's generated verifiable facts over its narration, and verify journal-only
|
|
62
|
+
claims the same way before they reach an issue body; an agent's in-session narration is not
|
|
63
|
+
evidence.
|
|
56
64
|
6. Draft self-contained issues with the problem, concrete proposed work, relevant areas, and
|
|
57
|
-
validation. Route every authorized creation through
|
|
65
|
+
validation, using the [issue body template](references/issue-body.md). Route every authorized creation through
|
|
58
66
|
[github-issue](../github-issue/SKILL.md), including its repository gate, label approval, and
|
|
59
67
|
denied-external tracking behavior.
|
|
60
68
|
7. Archive only verified records fully processed across every represented repository, and never
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
# Issue body template
|
|
2
|
+
|
|
3
|
+
Use this shape for a new issue and for a comment on an existing one. The body must be fully
|
|
4
|
+
self-contained: the source sessions are archived afterward, so never reference a session id, a
|
|
5
|
+
retrospective file name, or a local journal path. Embed the relevant evidence instead.
|
|
6
|
+
|
|
7
|
+
For a comment, open with a line such as "Additional context from recent retrospectives". Omit
|
|
8
|
+
`## Root cause` when the issue already documents it, or retitle it `## Additional root cause
|
|
9
|
+
context` when the comment adds new information.
|
|
10
|
+
|
|
11
|
+
```markdown
|
|
12
|
+
## Root cause
|
|
13
|
+
|
|
14
|
+
<the underlying process or tooling gap; for a recurring theme, why it keeps happening>
|
|
15
|
+
|
|
16
|
+
## Problem
|
|
17
|
+
|
|
18
|
+
<symptoms with concrete PR and commit references>
|
|
19
|
+
|
|
20
|
+
## Proposed fixes
|
|
21
|
+
|
|
22
|
+
- [ ] <each fix as a checkbox with the file path it touches>
|
|
23
|
+
|
|
24
|
+
## Files / areas
|
|
25
|
+
|
|
26
|
+
- <existing paths verified at HEAD, and proposed paths marked `New`>
|
|
27
|
+
|
|
28
|
+
## Context
|
|
29
|
+
|
|
30
|
+
<evidence lifted from the source records: the specific reflection text, root-cause notes, concrete
|
|
31
|
+
paths, and the relevant verifiable-fact figures (push and commit counts, diff scope) that motivated
|
|
32
|
+
the theme. Use only durable references: PR #N, issue #N, and the retrospective date (YYYY-MM-DD).>
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
Journal entries are unminimized notes and can carry credentials or sensitive local context. Summarize
|
|
36
|
+
a finding in your own words; never paste a command line or stderr, and strip any long opaque token,
|
|
37
|
+
`VAR=value` assignment, or credential-bearing URL. Checking a claim against the remote default branch
|
|
38
|
+
verifies its accuracy; it does not sanitize the text.
|
|
39
|
+
|
|
40
|
+
Apply the path rules of [github-issue](../../github-issue/SKILL.md) to `## Files / areas`.
|
|
@@ -27,7 +27,11 @@ Use only non-interactive forms, and run every `gh stack` command without a TTY.
|
|
|
27
27
|
create ordinary pull requests when stacks are disabled; without a TTY these fail instead, so treat
|
|
28
28
|
a failure as the exit-9 recovery above rather than answering a prompt.
|
|
29
29
|
|
|
30
|
-
- `gh stack init <branch>`, rooted on the default branch only.
|
|
30
|
+
- `gh stack init <branch>`, rooted on the default branch only. It roots the first layer at the
|
|
31
|
+
local default branch, not `origin/<default>`, and in a linked worktree `git fetch origin` does not
|
|
32
|
+
advance that ref. Fast-forward it with `git fetch origin <default>:<default>` only when no worktree
|
|
33
|
+
has the default branch checked out. Otherwise the checkout that has it fast-forwards itself with
|
|
34
|
+
`git merge --ff-only origin/<default>`; never move it from another worktree.
|
|
31
35
|
- `gh stack add <branch>`, after the layer cap check in [SKILL.md](../SKILL.md#work-bottom-up).
|
|
32
36
|
- `gh stack checkout <stack-or-pr-number>` imports an existing remote stack. See
|
|
33
37
|
[Import a stack](#import-a-stack-before-acting-on-it).
|