# Nightly MainClava self-improvement retro — 2026-09-23

Review window: 2026-09-22 in America/Los_Angeles (2026-09-22 00:00–23:59 PT; UTC 07:00–2026-09-23 07:00).

## Reviewed

- `MEMORY.md`, dated memory files for the review window, `docs/post-change-reviewer.md`, and `docs/self-improvement/REVIEW_RULES.md`.
- Candidate MainClava session JSONL files discovered by mtime and inspected for in-window operational outputs. No dated memory files were present for Sep 22.
- Financial Club, Luma, Gmail/NJFSC, official-news, daily-brief, release-check, exposure-check, and keepalive outputs.

## Findings

1. The official-news watcher repeatedly received an OpenAI News 403. On one run it nevertheless emitted a purported xAI high-signal item whose summary contained image/srcset/path-fragment text and no reliable date. This is a recurring parser/publication-boundary failure, not a clean source-health result.
2. The NJFSC Gmail monitor used unsupported `gws messages`, so its negative reply conclusion was not backed by a successful authenticated query in that run. Existing rules require a checked-in command-shape repair; that repair was not evidenced.
3. Financial Club and Luma refreshes reported new events/members and successful calendar integrity checks, with no new UI/runtime, blank-screen, clipping, stale-asset, or deploy failure established in the reviewed outputs. The Financial Club publication-level duplicate/fetch-failure risks from the prior retro were not proven remediated by this review.
4. Exposure probes were externally closed/timeout while the watchboard and local evidence remained separate; this is not treated as proof that all exposure/audit risk is resolved. Supabase keepalive also failed DNS and correctly surfaced a failed result.

## Rules changed

- Advanced the nightly date marker.
- Added rule 25a: the cron/wrapper must reject malformed official-news candidates at the publication boundary, even when `new_high_signal` is non-empty, and quarantine delivery until a scheduled-style regression passes.
- No wording change is counted as remediation for the recurring Financial Club or unsupported-GWS failures.

## Unresolved risks

- Repair and fixture-test the official-news parser and wrapper; rerun it in scheduled mode with the 403 source present and verify no malformed candidate can alert.
- Repair the NJFSC monitor to use the supported GWS command shape, then perform an authenticated checkpoint/readback before claiming “no new reply.”
- Repair the Financial Club publication duplicate-key gate and per-event failure reporting; keep the result partial until a live readback proves both.
- Reconcile exposure/audit findings and the installed OpenClaw version against the release check through the approved, backed-up path.

Status: PARTIAL — artifacts were reviewed, but recurring source/parser and monitor command-shape risks remain unresolved.