GIT1, GIT2, GIT3, GIT10: the forge module serves the seat git's verbs and says its events, retires its acting tools, follows the catalog half

The four share files (index.ts, module.json, guard.test.ts), so they land as one commit.
GIT1: seat.ts serves pull, open-pulls, tags, trees, file, contains, statuses, status, comment, view, note, merge-pull
as tools on the seat, each answering the contract's shape and an error of kind refused, not-found or failed; a comment,
view or note whose act id is held is answered held (note matched by id). merge-pull merges the head the caller names
(its from-G judgements are GIT6, GIT7, GIT9).
GIT2: seatevents.ts says pull-updated, pull-merged, pull-closed, forge-pull, forge-status, forge-delete and repo-writable on
mesh.seat.git.event.<event>; the module's emits drop them.
GIT3: merge.ts, check.ts, the acting tools, the owed watch, the gate's source read and check-gates-merge are gone.
GIT10: catalog.ts follows the seat mesh-catalog (revision, catalog-revision); no write is granted before the first view.

Builds: design 47 G §310, §311, §312, §313, §314, §163, §317, §278, §321, §196

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

modules/gitea/cmd/forge/commit.go

@@ -16,8 +16,7 @@ import (
 // gitea_commit (novox/hq issue 375): one commit on a branch of its own, so an agent follows the branch / pull
 // request / approval rule without anyone pushing by hand. By the rule gitea_api already enforces for a file
 // written (novox/hq ADR 0266): never the repository's default branch, never a branch a protection rule names.
-// Nothing about merging changes — that still needs a review at the head and both required checks green
-// (gitea_merge_pull_request).
+// Nothing about merging changes — a merge is the seat git's merge-pull, at the head the operator's Approve names.
 
 // FileChange is one file of a commit: its new content, as text or base64, or its deletion.
 type FileChange struct {