docs: name the issue that carries the pre-seed import

#188 decided to import the objects and recorded why. The operation itself is a
permanent append to the production WAL and is tracked as #256, so the two places
that said "tracked separately" now say where.

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.

Changed files

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

Diff

2 files changed, +4 -4

production log, its failure mode is the fleet-wide rebuild step 3 has never

exercised live, and both belong to an attended operation rather than to a

read-only rehearsal. #188 records the decision — import the objects, keep the

push record starting at the seed — and

`docs/forge-operator-independence.md` carries the reasoning.

push record starting at the seed — `docs/forge-operator-independence.md`

carries the reasoning, and #256 carries the operation.

## 4. Key rotation

if a node fails to materialize the new entry `OpenAgents.Forge.Sync` falls back

to a full rebuild from sequence zero, which rehearsal 3 records as never having

been run against the live projection. That is an attended operation on a forge

people are pushing to, not an unattended one, and it is tracked separately

rather than being described here as done.

people are pushing to, not an unattended one, and #256 carries it rather than

this document describing it as done.

## Exit