docs: FA7 closeout — Campaign FA CODE-COMPLETE

The retail four-tab social panel (Fellowship & Allegiance) is
code-complete: all six slices landed and reviewed (dual-lens Opus review
-> fix round -> narrow re-review each). Fellowship two-session flow proven
live (FA6 bot gate PASSED). Closeout bookkeeping:
- register AD count 66 -> 67 (AD-87, the deferred allegiance bot gate);
- plan status flipped to CODE-COMPLETE with the OWED connected gates +
  #384 (allegiance-swear ACE non-response) called out;
- CLAUDE.md Current-state gains the Campaign FA paragraph
  (per feedback_claude_md_staleness), pointing at the memory digest.

Owed: the user's connected gates (§FA3-§FA6 of
docs/research/2026-08-12-campaign-fa-test-script.md) and #384's
ACE-console disambiguation. Full suite 13,304/4/0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

CLAUDE.md

@@ -175,6 +175,36 @@ Gameplay-buttons half needs the re-gate with the new click logs). Tail:
 #371, #373, AP-198/199/201/202/203. START at
 `claude-memory/project_settings_options_digest.md`.
 
+**Campaign FA — the retail social panel (Fellowship & Allegiance)
+(`docs/plans/2026-08-11-fellowship-allegiance-campaign.md`) is
+CODE-COMPLETE 2026-08-12.** Retail authors ONE four-tab `gmPanelUI` social
+panel (Friends / Allegiance / Fellowship / Squelch, host slot
+`0x1000018F`, id 12; F3 = Allegiance, F4 = Fellowship, keyboard-only —
+Allegiance is the authored DEFAULT tab), mounted with the OP3 Options-panel
+recipe. The Fellowship and Allegiance pages are LIVE end-to-end: real wire
+(FA1 repaired the never-called H.2 builders + parsers — retail's FOUR
+tree-rejection rules, ELEVEN version gates, the byte-decoded `>=9` size and
+the truncated XP-share table), two session-scoped Runtime owners
+(`RuntimeFellowshipState`/`RuntimeAllegianceState`, both clear at
+generation reset — D2 corrected), and the authored panels through
+`LayoutImporter`. Friends/Squelch bind read-only to J4.1's owners.
+**The fellowship two-session flow is PROVEN over the live wire** — FA6's
+automated bot-vs-ACE gate (`testaccount`/`+Acdream` + `testaccount2`/
+`+Horan`) passed: the recruited bot's OWN `RuntimeFellowshipState` flips
+`IsInFellowship`. Six FA slices, each dual-lens Opus reviewed → fix round →
+narrow re-review; the reviews caught what tests can't (retail's 4th tree
+rule, the D2 reset-lifetime inversion, the D6 server-side invite filter,
+a seam-map entry that would have re-introduced a fixed bug). OWED: the
+user's connected gates (§FA3-§FA6 of
+`docs/research/2026-08-12-campaign-fa-test-script.md`, several
+`[TWO-CLIENT]`), and **#384** — the allegiance-swear bot gate is
+deferred/disabled because ACE returns NOTHING to the `0x001D` swear at
+0.005 m (no confirmation, no tree update, no error; needs ACE-console
+disambiguation — the swear CODE is done+reviewed, only its automated
+two-session proof is unverified; register AD-87). Tail: #383 (installed-
+DAT vs committed-fixture drift, found at FA3). START at
+`claude-memory/project_fellowship_allegiance_campaign.md`.
+
 **Placement cutover — C4 COMPLETE 2026-08-05, merged to main.** Every
 placement route now runs through the canonical residence + continuation-
 executor owner. Routes landed this session: 4b-3 remote teleport/cell-less