G's try 3 (try-1794495618073088394, step mwdogc5mc95787 on ace) lost the catalog's check answer: 264712 bytes, over the 262144 the steps state takes per value, so the checker could not preview the catalog and its manifests went unjudged. About 135 KB of it is the fetch's taken versions (fetch.packages), which no reader judges (checker, gate, builder: read and confirmed by the review).
buildstep finish now writes once more without the taken versions when an end carrying its answer is refused as too large; the step's reason says how many were left out, the refusal, and that the module's journal names each. Still too large, or no taken versions: ends failed as before. Also applies to a failed end carrying its answer (A-286's path).
Quick fix: this, so G's next try judges the catalog. Thorough fix: A-290 in G (an answer over the bound is kept as the object output.<ask> the key names).
Test: TestAnAnswerOverTheStateBoundLeavesOutItsTakenVersions (three rows), failing without the change.
Reviewed-by: mesh-code-reviewer@shanks at 22bbb9c2c0
Small fix (hq playbook 08); issue 1921 note 91; principle 3.
G's try 3 (try-1794495618073088394, step mwdogc5mc95787 on ace) lost the catalog's check answer: 264712 bytes, over the 262144 the steps state takes per value, so the checker could not preview the catalog and its manifests went unjudged. About 135 KB of it is the fetch's taken versions (`fetch.packages`), which no reader judges (checker, gate, builder: read and confirmed by the review).
buildstep finish now writes once more without the taken versions when an end carrying its answer is refused as too large; the step's reason says how many were left out, the refusal, and that the module's journal names each. Still too large, or no taken versions: ends failed as before. Also applies to a failed end carrying its answer (A-286's path).
Quick fix: this, so G's next try judges the catalog. Thorough fix: A-290 in G (an answer over the bound is kept as the object `output.<ask>` the key names).
Test: TestAnAnswerOverTheStateBoundLeavesOutItsTakenVersions (three rows), failing without the change.
Reviewed-by: mesh-code-reviewer@shanks at 22bbb9c2c09f9416df1af32ded939892f806db0f
https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
A catalog check's answer of 264712 bytes was refused by the steps state
(256 KiB per value) and its end written failed without it, so the checker
lost the biggest member's answer and could not preview it. When a passed
or failed end is refused as too large, finish writes it once more without
the fetch's taken versions (fetch.packages, which no reader judges), the
step's reason saying how many were left out, why, and that the module's
journal names each; still too large, it ends failed as before.
Quick fix for issue 1921 (note 91); the thorough fix is design 47 G A-290
(an answer over the bound kept as the object output.<ask>).
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Deliverynovox/mesh-catalog@22bbb9c2c09f — merged since 2026-11-12T15:37:56Z
Source — source.main moved to novox/mesh-catalog@8484ab0032. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-12 15:36 (new) → proposed (announced): novox/mesh-catalog#667's head announced
2026-11-12 15:36 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-12 15:37 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@22bbb9c2c09f` — **merged** since 2026-11-12T15:37:56Z
**Source** — source.main moved to novox/mesh-catalog@8484ab0032a5. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-12 15:36 (new) → proposed (announced): novox/mesh-catalog#667's head announced
- 2026-11-12 15:36 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-12 15:37 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Small fix (hq playbook 08); issue 1921 note 91; principle 3.
G's try 3 (try-1794495618073088394, step mwdogc5mc95787 on ace) lost the catalog's check answer: 264712 bytes, over the 262144 the steps state takes per value, so the checker could not preview the catalog and its manifests went unjudged. About 135 KB of it is the fetch's taken versions (
fetch.packages), which no reader judges (checker, gate, builder: read and confirmed by the review).buildstep finish now writes once more without the taken versions when an end carrying its answer is refused as too large; the step's reason says how many were left out, the refusal, and that the module's journal names each. Still too large, or no taken versions: ends failed as before. Also applies to a failed end carrying its answer (A-286's path).
Quick fix: this, so G's next try judges the catalog. Thorough fix: A-290 in G (an answer over the bound is kept as the object
output.<ask>the key names).Test: TestAnAnswerOverTheStateBoundLeavesOutItsTakenVersions (three rows), failing without the change.
Reviewed-by: mesh-code-reviewer@shanks at
22bbb9c2c0https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Delivery
novox/mesh-catalog@22bbb9c2c09f— merged since 2026-11-12T15:37:56ZSource — source.main moved to novox/mesh-catalog@8484ab0032. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.