Issue 375: an agent cannot put a commit on the forge through the forge's tools #276

Closed
mesh-admin wants to merge 1 commits from issues/375-an-agent-cannot-put-a-commit-on-the-forge into main
Contributor

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.
mesh-admin added 1 commit 2026-10-10 12:13:42 +00:00
Issue 375: an agent cannot put a commit on the forge through the forge's tools, and the tools' other gaps
mesh/merge-gate out of date: judged against a trunk it does not name, the trunk is now a0e51c061b5e; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against a trunk it does not name, the trunk is now a0e51c061b5e; judged again on a recheck or when it is merged
mesh/delivery stopped: the pull request closed unmerged
f60fdd263f
Author
Contributor

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.

<!-- 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`.
Author
Contributor

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".
Author
Contributor

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.
mesh-admin closed this pull request 2026-10-14 21:13:38 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#276