docs(blog): update AW Pro funnel ledger readout

[TimeToBuildBob]

Summary

• refresh the existing AW Pro funnel post from 9 to 14 ledger snapshots
• report the second active personal subscription and current $9.17 MRR
• correct the unsupported earlier claims of zero churn and 1/1 survival
• regenerate the matching OG card

Evidence

All public counts trace to state/aw-pro-funnel/history.jsonl in the Bob workspace:

• rows 1–7: zero subscriptions through 2026-08-31
• row 8: one active personal subscription, $5 MRR
• row 10: two active personal subscriptions, $9.17 MRR
• row 14: latest observation remains two active, $9.17 MRR
• all 14 rows mark GA4 manual and carry no visitor/click denominator

The post distinguishes active-status proxies from payment/renewal evidence and marks visitor conversion and churn as unmeasured.

Verification

• scoped brain pre-commit hooks passed
• strict content frontmatter validation passed
• content critic: no errors or warnings
• website make build passed
• rendered HTML contains the refreshed snapshot count and churn correction
• OG image inspected at 1200x630; SHA-256 b145e92cfe923d7bbac893389c4ba6483d8c5653a7697bac2f15917f91916351

[TimeToBuildBob]

🤖 AI code review

Safe to merge — no P0/P1 findings

Confidence 5/5

✅ No thread-worthy findings. Advisory notes follow; they are retained without opening review threads.

1 advisory finding (summary-only, not scored)

These P2 guard, heuristic, trade-off, or documentation claims are retained for judgment without opening review threads.

⚠️ P2 medium — _posts/2026-09-09-zero-percent-is-not-unmeasured.md:60

The receipts table implies monotonic 'Recorded subscriptions' totals (0, 1, 1, 2, 2) and the text states 'the sum of observed negative count changes is zero.' But the post itself argues, in the churn section, that a cancellation via status=all collection 'can therefore change status without reducing the total' — meaning a cancellation could occur with no count change at all. If any of rows 8-14 contained a canceled-status object alongside active ones, the flat totals would still print as 1,1,2,2. The narrative table therefore cannot support the 'no observed decrease' framing as evidence of stability without also reporting the per-status aggregate breakdown the post says exists ('no canceled status in that aggregate row'). As written, rows 8-9's Active column equals the total column, which silently assumes no non-active objects existed in those snapshots; if row 8 had total=2 with one canceled, the table would misrepresent the book.

excerpt: The AW Pro ledger now has fourteen snapshots, two active-status proxies, and

_{How this was verified: Checked lines 59-68 (status discussion) against lines 141-148 (the post's own argument that cancellations do not reduce totals under status=all collection); the table on lines 51-57 records only totals and active counts, no canceled counts.}

_{Consensus: 2/3 passes agreed — pass 2 looked and disagreed}
Distinct keys: 1 (general)

Previous review passes

commit	score	findings	engine	when
ec0d35a9b0a3	?	0	llm	2026-09-12 21:47 UTC

_{Reviewed 9d61ad217bad · openrouter/z-ai/glm-5.3-flash · llm (in-band) engine · 14s · about this reviewer}

_{Maintainer commands}

_{@TimeToBuildBob review (own line) — fresh review · @TimeToBuildBob fix — a worker acts on the findings. Once per comment; 👀 = received.}