docs: mark F11 accepted and log manager decision

This commit is contained in:
Rawman Grey 2026-10-30 10:22:34 +03:00
parent 871182d6d5
commit 3d9ed8de51
2 changed files with 10 additions and 2 deletions

View file

@ -216,7 +216,7 @@
"Journal compaction under the run lock retains unresolved rows plus the last 1,000 recovered rows, so the file cannot grow without bound.",
"Targeted unit tests cover journal append/replay/idempotency, backoff schedule, max-attempt exhaustion, due-retry selection, and the failure endpoint response shape."
],
"passes": false,
"passes": true,
"blocked_by": [
"F08"
],
@ -224,7 +224,8 @@
"Root cause: `/ops` is an in-memory 200-entry ring buffer per PM2 worker; after a long run the 17 failure details were unrecoverable.",
"Do not reuse `/ops` for persistence; keep it as the live view. Journal is append-only for cluster safety; compact only under `run.lock`.",
"Retry policy starts with constants; expose settings only if tuning is needed after the first real run.",
"No user-facing notifications; logs and the read-only API/module table are the observability surface."
"No user-facing notifications; logs and the read-only API/module table are the observability surface.",
"Accepted 2026-10-30 on code + test evidence (79/79, tsc clean, build OK) after three review rounds; browser module render and live PM2 scheduler/retry tick were waived by the user and remain unverified."
]
},
{