Development record
The remedy of iss-2610171626398856 (the v0.15.1 release review) asks for iss-2610161639025702 and iss-2610161756384596 to be resolved, as if the two-preflight work had delivered them. Neither ask has shipped. Deriving the preflight count from the machine's resources is still named a later step in internal/core/implement/load_slots.go:37-39 and in the brief (04-surfaces/27-implement.md:373-374). iss-2610161639025702 asks for more than the trial, including merge batching and test stages that run only the packages a change can affect. Following that remedy as written would close two open asks.
issueopenminoriss-2610241549396753
The remedy of iss-2610171626398856 (the v0.15.1 release review) asks for iss-2610161639025702 and iss-2610161756384596 to be resolved, as if the two-preflight work had delivered them. Neither ask has shipped. Deriving the preflight count from the machine's resources is still named a later step in internal/core/implement/load_slots.go:37-39 and in the brief (04-surfaces/27-implement.md:373-374). iss-2610161639025702 asks for more than the trial, including merge batching and test stages that run only the packages a change can affect. Following that remedy as written would close two open asks.
Frontmatter
| id | iss-2610241549396753 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610241549396753-the-remedy-of-iss-2610171626398856-the.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-2610161639025702Preflight throughput sets the pace of all work on this machine, and nothing keeps it in bounds. On 2026-10-16 the load gate admitted one make preflight at a time, each took about 40 minutes, and about 20 waiters were queued across seven sessions. Every reviewed branch had its own preflight, so a seven-step feature needed seven full runs, and records-only branches paid the same full cost as code. Sessions waited hours, and the queue's ordering after the reboot starved late waiters (fixed separately on fix/load-queue-start-order). No rule tells sessions to batch work, and no part of preflight scales its cost to what a change touches.
- iss-2610161756384596abcd's load gate admits a fixed number of preflights, one, whatever the machine can carry. The product thinker asked on 2026-10-16 that abcd know how many concurrent preflights, race runs and sub-agents are feasible from the resources it actually has, instead of a number a person sets and re-sets by hand (the machine-wide cap moved six times in two weeks: six, eight, ten, twelve, ten, fourteen).
- iss-2610171626398856The v0.15.1 release review found at CHANGELOG.md:19-72: INCOMPLETE (judgement call). The 0.15.1 section has no Added line for user-facing surfaces that are new since v0.15.0 and present in this binary. (1) `abcd status`, a top-level verb in `abcd --help` with a user-invocable commands/status.md (block: people); commands/status.md does not exist at v0.15.0. (2) `abcd announce` (commands/announce.md). Both come from the planned itd-2609151838312703 and its open spc-2610150728396006. (3) `abcd implement load --race-gate` and the `load.preflights` / ABCD_LOAD_PREFLIGHTS setting (internal/core/implement/load_slot…