Fix the module name two forge runbooks spell as GitHttp

Fix the module name two forge runbooks spell as GitHttp

The module is `OpenAgents.Forge.GitHTTP`. Two documents name it
`OpenAgents.Forge.GitHttp`, and
`test/openagents/forge/exit_rehearsal_runbook_test.exs` reads the runbooks and
resolves every module they name, so the misspelling fails the suite on `main`.
Unrelated to the change that found it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoZMfWRSGnf6FZX2Ar9rQ2

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoZMfWRSGnf6FZX2Ar9rQ2

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

modified docs/forge-exit-rehearsals.md
modified docs/forge-operator-independence.md

Diff

2 files changed, +2 -2

projection is node-local while the log is shared (#251): two nodes applied the
entry immediately and the third sat at 425 with its boundaries still open for
several minutes, converging only when `Sync.ensure_fresh/2` ran. That is the
call `OpenAgents.Forge.GitHttp` makes before serving any git request, so a
call `OpenAgents.Forge.GitHTTP` makes before serving any git request, so a
clone routed to a lagging node converges it before being answered rather than
receiving a grafted history. And the failure mode that made this attended — a
fleet-wide rebuild from sequence zero — was not reached on any node, so it

is node-local while the log is shared (#251), so a node applies a new entry on
its own schedule: two nodes had applied 426 immediately, and the third sat at
425 for several minutes with its boundaries still open. It converged when
`Sync.ensure_fresh/2` ran, which is what `OpenAgents.Forge.GitHttp` calls
`Sync.ensure_fresh/2` ran, which is what `OpenAgents.Forge.GitHTTP` calls
before serving any git request — so a clone routed to a lagging node converges
it before it is answered rather than being served a grafted history. The
fallback that made this an attended operation, a rebuild from sequence zero,

439	439		`projection is node-local while the log is shared (#251): two nodes applied the`
440	440		`entry immediately and the third sat at 425 with its boundaries still open for`
441	441		several minutes, converging only when `Sync.ensure_fresh/2` ran. That is the
442		-	call `OpenAgents.Forge.GitHttp` makes before serving any git request, so a
	442	+	call `OpenAgents.Forge.GitHTTP` makes before serving any git request, so a
443	443		`clone routed to a lagging node converges it before being answered rather than`
444	444		`receiving a grafted history. And the failure mode that made this attended — a`
445	445		`fleet-wide rebuild from sequence zero — was not reached on any node, so it`

381	381		`is node-local while the log is shared (#251), so a node applies a new entry on`
382	382		`its own schedule: two nodes had applied 426 immediately, and the third sat at`
383	383		`425 for several minutes with its boundaries still open. It converged when`
384		-	`Sync.ensure_fresh/2` ran, which is what `OpenAgents.Forge.GitHttp` calls
	384	+	`Sync.ensure_fresh/2` ran, which is what `OpenAgents.Forge.GitHTTP` calls
385	385		`before serving any git request — so a clone routed to a lagging node converges`
386	386		`it before it is answered rather than being served a grafted history. The`
387	387		`fallback that made this an attended operation, a rebuild from sequence zero,`