AOCI-CODE v0.1.0-rc23

AOCI-CODE v0.1.0-rc23 is built from 592e90c80dac137950a8c871a2030300c516353b.

The rc22 soak's one finding: a Managed Scope rule could reach a formal
Volume and leave the repository with no command that moved it. Formal assets
are now outside policy. No MCP tool name, input schema, formal-asset format,
or scope identity changes.

• A scope rule that reached a formal Volume no longer deadlocks Managed Scope
  (#158, Loren-0101). A rule could give aoci.code.txt the observe role, and
  the Baseline then carried the Volume as Observe evidence that status, the
  Guide, and a Scope Change Plan each read differently: the Guide reported it
  observed_removed, scope acknowledge answered
  observed_evidence_review_not_pending, and every scope preview answered
  observed_evidence_review_required, with no command that moved the
  repository. Formal assets are now outside policy: evaluation gives the Root
  and its declared Volumes the index role whatever rules match them (a
  git-hidden one still stops scan), the three readers strip them through one
  projection, a Volume's Baseline record carries the index role however it was
  recorded, and scope rule add or update refuses an exact file rule naming
  one as managed_scope_rule_targets_formal_asset (switching such a rule
  off is allowed). A repository already in that state is aligned again on
  upgrade, and its next Scope Change writes the role back. No identity, tool,
  schema, or format changes.
• The pre-tag audit of that fix caught two readers it had missed. The pin is
  decided by the Root marker, so it never reaches a Legacy index file: there
  aoci.txt is an ordinary rule-governed candidate whose Entry Maintain never
  plans, and pinning it left an rc22-aligned Legacy repository with a custom
  profile or a *.txt rule answering managed_scope_authoring_candidate_required
  for its own index with no command that cleared it. The post-Apply alignment
  inspector that every aoci_update_entry result reads now takes the same
  projection as status and the Guide, so a Root or Meta record a rule once
  observed no longer makes each batch report observed_removed while
  governance says aligned.

See docs/install.md and docs/supply-chain.md for asset verification.