STATUS + CONTEXT + DRILL record: conversion, kept data, D3; 09 decision 39; R-655 measured

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

documentation/architecture/09-update-architecture.md

@@ -441,6 +441,15 @@ R-636's louder repeated alarm.
     when they hold no table; `CREATE ROLE <x>;` skipped only for a role that exists — its `ALTER ROLE … PASSWORD`
     still runs), so ANY other error stops the load and the undo runs. Proven live: an extension 18 lacks
     (`adminpack`) stopped the load and the box undid it. `audits/night-2026-09-26/A/README.md` A2.
+39. **docmost's own memory limit rises 384M → 512M with its PostgreSQL 18 step** — *decided by CC unattended
+    2026-09-25 — operator may reverse.* *One sentence:* the bench marked the step `memory_tight` (the docmost app, not
+    the engine) — raise the limit, or leave docmost unmoved? **Options:** (a) keep 384M — the move gate refuses a tight
+    step whose limit does not move, so docmost stays on 16; (b) raise to 512M in the same commit (the gate's own
+    remedy, the RomM precedent). **Costs:** (a) the conversion that was built and proven tonight never reaches a box;
+    (b) +128 MB of reservation per docmost box (`mem_limit` 768M → 896M), and the mark stays (80.4 % at 512M): measured
+    twice, Node sizes its heap from the limit — 349 MB at 384M, 431 MB at 512M, 0 kills and 0 restarts in both 10-minute
+    watches (~12 000 requests each). **Why (b):** 91 % of the old limit is too close for a household box, the gate's
+    rule is followed rather than bypassed, and the mark's weakness for such apps is filed (R-693). Reversible.
 
 ---