Registers issue 375 (status: open), numbered by issue-tracker.open.
Symptom (2026-10-09, the laptop): an agent's checked hq commit could not reach the forge. The clone's push URL was DISABLED; the forge module has no push, commit or patch verb; gitea_api refused POST …/diffpatch; its only file write takes the whole file as base64 (about 121 KB for a 90 KB design document), which an agent cannot reproduce reliably.
2026-10-10: the push URL is restored, so git push works again with the operator's key. Who disabled it and who restored it is not recorded. The forge's 35 tools are unchanged.
Other gaps, found by listing the forge module's tools: no commit history or compare (the raw call is about 100 lines of JSON per commit), no reading of a pull request's reviews or line comments, no branch creation, no issue editing, no directory listing, no code search. The report marks which ones were tried against the raw API.
Open: a forge key per agent (as on the control node, ADR 0266) or a forge verb that writes a patch under the agent's account. Either one needs a decision record.
Checks: sh merge-check.sh (records, index, cycle, words with the catalogue's list) passes on this head, which is on main's head.
Registers issue 375 (status: open), numbered by `issue-tracker.open`.
- **Symptom (2026-10-09, the laptop):** an agent's checked hq commit could not reach the forge. The clone's push URL was `DISABLED`; the forge module has no push, commit or patch verb; `gitea_api` refused `POST …/diffpatch`; its only file write takes the whole file as base64 (about 121 KB for a 90 KB design document), which an agent cannot reproduce reliably.
- **2026-10-10:** the push URL is restored, so `git push` works again with the operator's key. Who disabled it and who restored it is not recorded. The forge's 35 tools are unchanged.
- **Other gaps, found by listing the forge module's tools:** no commit history or compare (the raw call is about 100 lines of JSON per commit), no reading of a pull request's reviews or line comments, no branch creation, no issue editing, no directory listing, no code search. The report marks which ones were tried against the raw API.
- **Open:** a forge key per agent (as on the control node, ADR 0266) or a forge verb that writes a patch under the agent's account. Either one needs a decision record.
Checks: `sh merge-check.sh` (records, index, cycle, words with the catalogue's list) passes on this head, which is on main's head.
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@f60fdd263f14` — **stopped** since 2026-10-14T21:14:03Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 12:14 (new) → proposed (announced): novox/hq#276's head announced
- 2026-10-10 12:14 proposed → checked (checked): the verdict names this commit
- 2026-10-10 12:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-14 21:14 ready → stopped (closed): the pull request closed unmerged
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Rework needed before merge (triage, 2026-10-11): the narrative is wanted (issue 375's tracker record points at this folder), but cut the frontmatter to opened: only — cycle.py now refuses status, located-in, fixed-by and amended-design (ADR 0291) — and replace the two 02-DECISIONS links (ADR 0266, ADR 0245) with plain "ADR NNNN".
Rework needed before merge (triage, 2026-10-11): the narrative is wanted (issue 375's tracker record points at this folder), but cut the frontmatter to `opened:` only — cycle.py now refuses status, located-in, fixed-by and amended-design (ADR 0291) — and replace the two 02-DECISIONS links (ADR 0266, ADR 0245) with plain "ADR NNNN".
Closed as obsolete (independent review, 2026-10-14): issue 375 is a tool gap of the forge module, fixed by mesh-catalog#233 and resolved in the issue tracker with its proof, so playbook 03 keeps it in the tracker alone, not as an hq folder. The report also carries status keys cycle.py refuses (status: open contradicts the tracker) and links two 02-DECISIONS files that no longer exist; merge-check.sh fails on them against main. The branch is kept.
Closed as obsolete (independent review, 2026-10-14): issue 375 is a tool gap of the forge module, fixed by mesh-catalog#233 and resolved in the issue tracker with its proof, so playbook 03 keeps it in the tracker alone, not as an hq folder. The report also carries status keys cycle.py refuses (status: open contradicts the tracker) and links two 02-DECISIONS files that no longer exist; merge-check.sh fails on them against main. The branch is kept.
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.
Registers issue 375 (status: open), numbered by
issue-tracker.open.DISABLED; the forge module has no push, commit or patch verb;gitea_apirefusedPOST …/diffpatch; its only file write takes the whole file as base64 (about 121 KB for a 90 KB design document), which an agent cannot reproduce reliably.git pushworks again with the operator's key. Who disabled it and who restored it is not recorded. The forge's 35 tools are unchanged.Checks:
sh merge-check.sh(records, index, cycle, words with the catalogue's list) passes on this head, which is on main's head.Delivery
novox/hq@f60fdd263f14— stopped since 2026-10-14T21:14:03ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Rework needed before merge (triage, 2026-10-11): the narrative is wanted (issue 375's tracker record points at this folder), but cut the frontmatter to
opened:only — cycle.py now refuses status, located-in, fixed-by and amended-design (ADR 0291) — and replace the two 02-DECISIONS links (ADR 0266, ADR 0245) with plain "ADR NNNN".Closed as obsolete (independent review, 2026-10-14): issue 375 is a tool gap of the forge module, fixed by mesh-catalog#233 and resolved in the issue tracker with its proof, so playbook 03 keeps it in the tracker alone, not as an hq folder. The report also carries status keys cycle.py refuses (status: open contradicts the tracker) and links two 02-DECISIONS files that no longer exist; merge-check.sh fails on them against main. The branch is kept.
Pull request closed