mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-01 06:24:41 +01:00
Garry Tanandcapy-ai[bot]
c1900088d5
* feat(skills): absorb pstack's blast radius, transcript recall, vet-the-number and design-twice as lazy sections
/investigate gains sections/blast-radius.md (the one safety fact, the five-rung
evidence ladder, look where grep stops, confirmed and cleared risks apart) with a
Phase 4 pointer, and the shared-premise red flag before the 3-strike rule.
/context-restore is carved for the first time: on NO_CHECKPOINTS, sections/transcripts.md
mines this workspace's own transcripts (host stores declared in hosts/*.ts and rendered
by TRANSCRIPT_SOURCES / TRANSCRIPT_DISCOVERY), a fixed 7-day window, never another
project's folder, subagents return only findings, redaction before anything leaves,
git and gh verify every artifact, a status-tagged brief. /benchmark is carved for the
first time: sections/vet-the-number.md asks the seven questions before Phase 5 reports
a comparison. /plan-eng-review gains sections/design-twice.md (a second structurally
distinct shape compared on interface depth, the eight design red flags), bound by the
autoplan methodology snapshot alongside review-sections.md.
Ideas from pstack (Lauren Tan, MIT), rewritten in gstack's words; NOTICE.md. Garry,
2026-10-26: "Do it, send". Guards: carve-guards entries and measured lines, eleven
plan-eng-review pins re-measured, periodic carve-section-loading cases for the two new
carves, free tests with a fixture transcript.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix(pstack-c1): fold design-twice into Section 1 of the eng review section, per-host transcript table, fixture and slice-cap repairs
The remote free run reported nine failures in seven files, all from this
branch: four tests encode plan-eng-review's one companion section
(eng-scope-entry-ap, autoplan-methodology-names, plan-review-cases,
review-checklists), so the design-twice pass now lives inside Section 1 of
sections/review-sections.md with the skeleton, manifest and
bin/gstack-autoplan-snapshot.ts back at main; the Codex render of
context-restore named ~/.claude/ through the all-hosts transcript table, so
{{TRANSCRIPT_SOURCES}} renders this host's row only; the transcript fixture
is declared in FREE_FIXTURES; and the two new periodic cases took the census
to 39 slices, so evals-periodic.yml's eval-slices max-parallel goes 38 -> 40.
Pins: 11 plan-eng-review re-pins at +2,896; maxSizeRatio 1.2400 (measured
1.2389); Codex gpt-5.4 overlay 159,588 bytes.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix: pre-landing review fixes
The discovery block takes the none branch from hosts/*.ts's transcripts
declaration instead of a host-name fallthrough, and the resolver header says
where each half lives; the T2 subagent brief frames the transcript as data,
not instructions; the test asserts table/block agreement per host, imports
CAPY_NO_TRANSCRIPTS, and drops the fixture-shape case nothing reads.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* docs: ADDING_A_HOST.md lists the optional transcripts HostConfig field
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
35 lines
1.7 KiB
Cheetah
35 lines
1.7 KiB
Cheetah
## Checklist (runner profile)
|
||
|
||
Eng phase steps and required outputs for `bin/gstack-autoplan` (unattended or
|
||
`light` runs); interactive runs read `sections/review-sections.md` in full.
|
||
|
||
### Steps
|
||
1. Scope Challenge (A assess, B selectors, C findings) with the decision
|
||
procedure; every prior-phase consensus is in the prompt before review.
|
||
A ends with the reality rows: one `REALITY:` line per applicable row
|
||
(`gstack-plan-reality rows --phase eng`), each with a file:line receipt.
|
||
2. Sections 1–4 in order: architecture (with the design-twice pass when the
|
||
plan adds a module or boundary), code quality, test, performance
|
||
(`perf` scope). Continue after the outside voice.
|
||
3. Final planning decisions, then the finish sequence below in order.
|
||
|
||
### Required outputs → producing section
|
||
|
||
| Output | Produced by | Scope |
|
||
|---|---|---|
|
||
| Review body | Output reference — review body | always |
|
||
| Reality rows (`REALITY:` lines, `PLAN_REALITY` check) | Reality rows (why each exists) | always |
|
||
| NOT in scope | "NOT in scope" section | always |
|
||
| What already exists | "What already exists" section | always |
|
||
| Two shapes and red flags (new module or boundary only) | Two shapes before one (design-twice) | always |
|
||
| Diagrams | Diagrams | always |
|
||
| Failure modes | Failure modes | always |
|
||
| Worktree parallelization strategy | Worktree parallelization strategy | always |
|
||
| Test Plan | 3. Test review | always |
|
||
| Performance findings | 4. Performance review | perf |
|
||
| Unresolved decisions | Unresolved decisions | always |
|
||
| Completion summary | Completion summary | always |
|
||
| Review log row | Review Log | always |
|
||
| Next-skill handoff | Next Steps — Review Chaining | always |
|
||
| Learnings | Learning hooks | always |
|