docs(adr): ADR-0128 Status is Accepted — the maintainer's reply of 2026-09-07 is the acceptance act (#16647)

Ruling A on this card's last outstanding record, recorded by the director seat
2026-09-07 (comment 5572010837, decision batch #1 of summon #17, maintainer's
verbatim reply 「同意」): the Status line becomes

  Accepted (2026-09-07) — accepted by the maintainer's reply of 2026-09-07
  (objectstack#15453, decision batch #1 of director summon #17)

Dated to the ruling, not to the 2026-08-28 landing: that landing PR (#12839,
commit bbf88be) was merged by the seat account os-sales, and the earlier
ruling A of 2026-09-05 (5548576472) explicitly does not cover a seat merge —
so "the merge that landed it on main" is NOT the acceptance clause here, and
the sibling records' (ADR-0130, ADR-0131) merge clause is deliberately absent.

The whole Status field is replaced, not only its state sentence, following the
ADR-0130 (#15704) and ADR-0131 (#16590) flights: the field carries the state
and the act and nothing else. The tail this drops is flagged in the PR body as
a judgment call a reviewer can reject.

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

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-musk

docs/adr/0128-producer-discriminated-aad-for-cryptocontext.md

@@ -1,6 +1,6 @@
 # ADR-0128: The AAD binding on `CryptoContext` is producer-discriminated
 
-**Status**: Proposed (2026-08-28) — awaiting the maintainer's hand-merge, which is itself the acceptance act for a governed surface (Prime Directive #14). The **direction** below was already ruled on [#12599](https://github.com/objectstack-ai/objectstack/issues/12599) (maintainer, 2026-08-27, decision-inbox batch 6, verbatim and untranslated: 「其他同意」, accepting the seat recommendation "A now, with B recorded as the intended direction in its own ADR"). ⛔ **Nothing here is implemented, and this record changes no behaviour.** The prose half of that ruling shipped separately; see [Consequences](#consequences) for what is built and what is not.
+**Status**: Accepted (2026-09-07) — accepted by the maintainer's reply of 2026-09-07 (objectstack#15453, decision batch #1 of director summon #17)
 **Deciders**: maintainer ruling, 2026-08-27, PM chat decision-inbox batch 6, on the four-axis recommendation filed against [#12599](https://github.com/objectstack-ai/objectstack/issues/12599).
 **Builds on**: [ADR-0049](./0049-no-unenforced-security-properties.md) (no unenforced security properties — a documented guard weaker than the sentence advertising it is the same defect this record is about, one layer down), [ADR-0100](./0100-credential-field-channels.md) (credential field channels — the `secret` channel whose engine path is the second of the three producers below), [ADR-0112](./0112-error-code-vocabulary-and-ledger.md) (error-code vocabulary — any refusal added by the implementation legs takes a code from that ledger).
 **Supersedes**: nothing.