Skip to content

docs: weekly backlog re-verification and MODULE_AUDIT refresh (September 6, 2026) - #308

Merged
kyleve merged 5 commits into
mainfrom
cursor/todo-triage-weekly-pass-1863
Sep 6, 2026
Merged

docs: weekly backlog re-verification and MODULE_AUDIT refresh (September 6, 2026)#308
kyleve merged 5 commits into
mainfrom
cursor/todo-triage-weekly-pass-1863

Conversation

@cursor

@cursor cursor Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Posted by an AI agent on kve's behalf.

Summary

Why

The weekly todo-triage pass keeps the backlog honest: it closes what shipped, corrects citations the week's diffs moved, files what the new surface shows, and regenerates the derived audit so the report never carries claims the tree contradicts. This week's lead finding is about the audit itself — five published counts were wrong at publication, all undercounts or stale carries in figures whose text claimed freshness — so the affected items now record their derivation procedure, not just the number.

Review focus

  • The four-screens rewrite of the Settings SnapshotProviding item in Where/TODOs.md (including the WhereFlyoverView nuance: it is image-pinned by a suite that hosts it directly, without a conformance).
  • The 37 → 39 correction in Shared/SnapshotKitTesting/TODOs.md — the Ranking Animation Lab's settledAtLeast(1.0) × 2 configurations predates the August 30 audit, so both prior "re-derived and unchanged" claims were wrong.
  • The three new P2s in Where/TODOs.md, each verified against source before filing.
  • The self-correction table at the bottom of MODULE_AUDIT.md ("as published / as corrected" column).

⚠️ Breaking changes

None. Documentation and backlog files only; no production code changed.

Compatibility

Not applicable — no code, build, or CI changes.

Testing

  • Executed on the Linux agent: ./swiftformat --lint (0/1125), ./shellcheck (silent), ./attribution --check (up to date, 12 credits), ./snapshot-shards check (plan valid: 49 suites, 13/15/18/3 — the window's two new suites on the intake shard as designed), Python tool tests (64 tests, 1 known macOS-only failure), Ruby tool tests (75 runs, the known 12+1 platform failures). The retained-tool failures match the filed root P1 exactly; no new platform assumption appeared.
  • Six read-only verification subagents re-checked every open item with file:line evidence; every changed verdict and new finding was spot-checked by hand before publishing. False alarms rejected rather than filed (recorded in the audit): the demo-mode UserDefaults latch as "a mark on the device" (it is the Inspector pattern, one-shot, DEBUG-only); DemoDataBuilder's convenience init(now:calendar:) as a Core parameter-default violation (an explicit overload on demo fixture code, not a store API); DeveloperDemoModeRow / LocationCardEstimateSticker bare #Previews as coverage debt (both pinned transitively); RegionsSettings' unlabeled .combine (its symbol is .accessibilityHidden, children read as a sentence).
  • Skipped (unavailable on the Linux VM, per root AGENTS.md): ./test, the architecture lint, ./xcstrings --lint, ./sf-symbols --lint, and any simulator or pixel verification. Documentation-only change, so no test tier applies.
Open in Web View Automation 

Note

Low Risk
Markdown and backlog edits only; no production code, build, or CI behavior changes.

Overview
Documentation-only weekly todo-triage: re-verifies open backlog items against source after four landed PRs (#301#305) and replaces MODULE_AUDIT.md for September 6, 2026 with updated repo counts (700/369 sources/tests, 484 snapshot references, 49 suites, 25 test bundles).

The backlog itself moves modestly: no items closed, but the Settings image-coverage item narrows from five to four screens (PR #305 added RegionsSettingsView snapshots) and the namesake-test item drops obsolete scrolledForYear, leaving LocationNamer. Three new Where P2s file convention/doc debt from the week (demo launch sheet fixed-frame Form snapshot, orphaned WhereFormat.locationCardEstimatedDays after the sticker redesign, stale OnboardingGate “trunk head” comment).

Across TODOs.md files and audit text, the pass corrects stale citations and counts (e.g. settle-floor 37 → 39, WhereShortcuts five → four, CreditKit generator path, Broadway Project.swift lines) and documents five wrong numbers in the prior audit edition. SnapshotKitTesting/AGENTS.md reference totals update 472 → 484.

Reviewed by Cursor Bugbot for commit a1d7246. Bugbot is set up for automated code reviews on this repo. Configure here.

cursoragent and others added 5 commits September 6, 2026 13:29
Every open item re-checked against current source after PRs #301/#302/#305.
One partial closure: PR #305 gave RegionsSettingsView SnapshotProviding and
a 10-reference suite, so the Settings coverage item drops from five screens
to four; the WhereFlyoverView half of its ten-views claim was also stale
(WhereFlyoverViewSnapshotTests pins it without a conformance). The
scrolledForYear half of the namesake-test item is obsolete — the symbol no
longer exists — so that item narrows to LocationNamer.

Three new P2s from the window's new surface: DeveloperDemoLaunchSheet
snapshots a Form at a fixed frame against the full-content rule; PR #302
orphaned WhereFormat.locationCardEstimatedDays and its catalog key; the
OnboardingGate doc comment still says the gate roots the trunk after PR
#301 prepended the demo step.

Citation drift corrected throughout (WhereLaunch/WhereLaunchSteps moved
under the demo step; LocationsView moved under the sticker redesign;
WhereFormatTests under the new format tests; the WhereIntents doc cites
pointed past the end of both rewritten files; WhereShortcuts registers
four shortcuts, stale as 'five' since PR #230).

Co-authored-by: Kyle Van Essen <k@kve.me>
All root items still open, confirmed against current source (nothing in the
window touched .bumper/, CI configs, Tools/, or the dev scripts). The
kve-stuff deletion deadline is now three days out (September 9). The
gregorian rule has now survived six audits at the same 12 implicit sites.
The LFS-caching item's 377-object figure is dated to its measurement (the
tree holds 484 references now). The ./test macOS-tier item records that
root AGENTS.md's Build-system section still states 'the only way to run
tests' while its Running-tests section carries the carve-out.

Co-authored-by: Kyle Van Essen <k@kve.me>
…, 2026

All items still open. Corrections: the SnapshotKitTesting settle-floor
split is 39 addressable configurations, not 37 — both prior enumerations
missed RankingAnimationLabView's settledAtLeast(1.0) x fullContentPhoneLightDark,
which predates the August 30 audit; reference counts refreshed to 484
(473 WhereUI). Citation drift: PeriscopeToolsSnapshotTests wiring is
Project.swift:627-633; BroadwayCatalogTests declarations moved to :660-669
and its scheme listings to :748/:771; the CreditKit generator lives at
Shared/CreditKit/Tools/, not root Tools/; Ledger's scheme is :712-717 and
its untouched streak is four windows.

Co-authored-by: Kyle Van Essen <k@kve.me>
…s of September 6, 2026

Mechanical update of the two dated bullets (472 as of 2026-08-30 -> 484 as
of 2026-09-06) after PRs #301/#305 added 12 references. ./sync-agents run
to regenerate the gitignored CLAUDE.md mirror.

Co-authored-by: Kyle Van Essen <k@kve.me>
The quietest window yet: 4 PRs (#301 demo next-launch mode, #302 visa-sticker
estimates, #303 deterministic async-capture test, #305 Settings region
editor), all effectively in WhereUI. Nothing closed outright; #305 narrowed
the Settings image-coverage item from five screens to four; three small P2s
filed from the new surface.

The lead story is the audit's own error ledger: five of the August 30
edition's published numbers were wrong at its own date (WhereUI 276/102 not
274/101, totals 695/368 not 694/368, test bundles 25 not 26, the settle-floor
split 39 not 37, and a duplicated Method sentence), plus a WhereShortcuts
count stale since PR #230. All corrected with their derivations recorded.

Executed this pass: swiftformat --lint (0/1125), shellcheck, attribution
--check (12 credits), both retained-tool suites (known platform failures
only), and snapshot-shards check — which verified the two new suites landed
on the intake shard as designed (49 suites, 13/15/18/3).

Co-authored-by: Kyle Van Essen <k@kve.me>
@kyleve
kyleve marked this pull request as ready for review September 6, 2026 20:44
@kyleve
kyleve merged commit 3daba8f into main Sep 6, 2026
8 checks passed
kyleve added a commit that referenced this pull request Sep 7, 2026
> _Posted by an AI agent on kve's behalf._

## Summary

- refresh the weekly module audit for PR #307, which landed after the
same-day audit baseline
- re-verify Timeline backlog evidence and file the missing AX5
joined-card snapshot case
- correct the onboarding-gate boundary documentation everywhere it was
repeated and archive that completed item
- refresh source and snapshot-reference counts to 704 and 490

## Why

PR #307 landed after PR #308 had already published the September 6
weekly audit. This follow-up gives the same-day audit an explicit commit
boundary and brings the derived report and durable backlog back in sync
with main.

## Review focus

- the evidence and scope of the new planned-stay AX5 coverage item
- the corrected onboarding-gate wording across source comments, tests,
and the WhereUI README
- the same-day audit boundary and refreshed counts

## ⚠️ Breaking changes

None. Documentation, comments, and backlog state only.

## Compatibility

No runtime or persisted-format changes.

## Testing

- `./swiftformat --lint` — 0 of 1,129 files require formatting
- `./shellcheck`
- `./attribution --check` — report current at 12 credits
- `mise exec -- ./sync-agents`
- `python3 -m unittest discover -s Tools/Tests -p "test_*.py"` — 64
passed
- `./snapshot-shards check` — 49 suites, assigned 13/15/18/3
- inspected representative joined, separated, and AX5 Timeline
references
- retained Ruby suite — 74 of 75 passed; one isolated-HOME harness check
saw Apple Python emit Xcode cache/FSEvents diagnostics, while direct
`./snapshot-shards --help` was clean
- `./test` not run because this change touches only Markdown and Swift
comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants