The production castle now has five guarded corridors. Quotes, Channel Activity, Factoids, Playful and Short Content are all persistent, enabled and authoritative on #i/o. Each has passed its own observe-first gate, each has survived restart, and the failure ledger remains empty.

MB784 does not open a sixth door. It records the five doors that are already open.

The trail through the castle

The production journey was deliberately incremental. MB773 reconstructed the two postures lost before updater preservation was repaired. MB774 and MB775 promoted Quotes and Channel Activity. MB776 observed Factoids before MB777 promoted it. MB779 observed Playful before MB780 promoted it, with quiet_magic still asleep.

Short Content took the same guarded route. MB782 proved that observe remained silent and repository-write-free. Its temporary authoritative request returned one bounded HTTPS value, then the repository and policy were restored exactly. MB783 repeated the silent gate, returned MB783-mediabot_v3 through the core HTTP facade and retained one deliberate, bounded repository revision.

After the final restart, all five packages returned enabled/on with complete permissions and zero failures. Quote and factoid rows were unchanged, the four established ledger entries stayed byte-for-byte equivalent, and only the verified Short Content revision remained.

Evidence becomes contract

Operational success is valuable, but it becomes durable only when the source tree knows what was accepted. MB784 advances the machine-readable API contract, adds one production portfolio record and binds it to an executable regression test.

The contract now names both Short Content production gates, the exact final mode, the one accepted response, the bounded repository mutation and the restart result. It also records the complete five-package ordering and keeps MB772 updater preservation inside the trust boundary.

The new production portfolio runbook preserves the full sequence from MB773 to MB783, the final health checks and the package-scoped rollback order:

.plugins policy <package> #i/o off
.plugins disable <package>
.plugins unload <package>

The first command closes authority immediately. Disable stops the instance without forgetting configuration. Unload removes the runtime and next-boot entry. Restart remains a persistence proof, never a rollback mechanism.

A source-only spell

MB784 contacts no production service and performs no Partyline mutation. It starts from exact MB781 source and verifies the four accepted development packages on #test. Before changing a source file, it fingerprints the entire development plugin-data tree.

The targeted contracts, fast lane and one final full suite then run under the usual cadence. The state fingerprint must remain identical before commit and after commit. If a test or hidden side effect touches the ledger or a bounded plugin repository, the spell stops.

This matters because documentation should never become an excuse to move authority. MB784 turns production evidence into reviewable source truth while leaving both castles exactly where they stood. The five wards remain active; the quill merely records their names. 🦉✨