Spike: Facebook Page reached after the operator's Page click; scheduled post + photo created, read back byte-equal, deleted

Read phase passes (Page 1360018983863273, CREATE_CONTENT/MODERATE/ANALYZE, page token PAGE expires_at 0, three insights
metrics alive on v26.0). Write test: removal check accepts Meta's code-10 'Object does not exist' (fixed without a row,
4 tests); run 1 evidence kept. R-914 READY, R-915 narrowed to Live mode.

CONTEXT.md

@@ -22,8 +22,8 @@
 > DooPlex; the Page token is derived at run time and never stored; no third-party SDK or MCP server touches it
 > (operator ruling 2026-10-08). Posts go out **scheduled, for operator review, by default**. Ads are a separate app,
 > not built. No architecture document covers this and none should: it is a business tool, not part of the product.
-> Measured: token valid, `expires_at 0`, but `/me/accounts` empty — waits on the operator's asset click (R-915);
-> the skill is R-914.
+> Measured: token valid, `expires_at 0`; Page `1360018983863273` reached; scheduled post + photo created, read back
+> byte-equal, deleted. Public posting waits on Live mode (R-915, needs the ToS URL of R-813); the skill is R-914.
 
 > **2026-10-08 (evening) — the decision sheet D1–D10 built on main, unreleased (`09` §3 185–194).** Controller (`3f84f82`):
 > operator actions (`internal/report/opactions.go`, closed list), dashboard sessions on disk as sha256 + password