This is a point-in-time record of the week of 2026-05-04 to 2026-05-10. It was written from the repository's history for that week and is not revised afterwards, so later pages may supersede what it says.

Week of 2026-05-04 to 2026-05-10

Window: 2026-05-04 00:00:00 to 2026-05-10 23:59:59, local author time Recapped: 2026-08-28 Commits in window: 32 (23 non-merge, 9 merges)

This is a backfill written 110 days after the window closed. Work was concentrated on May 4, May 5, May 6 and May 8. A scan performed on 2026-08-28 found no commits in the maintainer's other five public GitHub repositories during the week; all visible public-repository activity was here.

What shipped

The week opened with bug chasing across the writer, parsers, dbt and DuckDB. c3d0a13 made float prices safe for the silver writer, addressed dbt/DuckDB locking, and updated planning records. 8246f5c corrected pipeline-health Grafana metrics and their Prometheus/StatsD inputs. Four small follow-ups repaired observability and dbt test definitions (61063df, 19c5625, 2a729c2, 099db48).

The May 5 cleanup added defensive guards across Airflow, scraper, processing, ops and shared database code (3298855), then standardized service logging through shared JSON formatting (d88a41e). It consolidated SQL loading and expanded router, parser and service coverage (cdbb1e1), added broad dbt schema and unit-test coverage (93a94f6), removed redundant and deprecated schema-test syntax (1f6b48b), and dropped staging tests that could not exercise MinIO directly (167b3a5). Two .gitignore adjustments accompanied the cleanup (26086a3, 81818ae).

Deployment and operations work corrected deploy-intent handling and the redeploy script (73899b4), repaired its integration test (44f5ec1), and added more useful /info error observability (33cfc6e). af39855 then addressed scraper writes and dbt-related operational behavior while adding a Grafana alert and revising scraper tests.

The May 8 sequence made pipeline failures diagnosable. 14899d1 ensured a dbt 500 response was pushed to Airflow XCom before raise_for_status() so the notification task retained stdout and stderr. 5460ebe, c92bd97 and 9bb1995 carried that detail through dbt-runner logs, Airflow notifications and Grafana alerts. 4a10682 removed obsolete raw-volume mounts.

None of those commits names a plan in its subject or body. The planning documents explain the state changes below, but they are not used to attribute the implementation commits.

What moved between states

The planning index had two revisions in the window:

What is still owed

The week created documents for Plan 105, Plan 106 and Plan 107, but none had a table row by the window's end. Plan 105 aimed to move production onto an Oracle free-tier VM; Plans 106 and 107 captured targeted code-review cleanup and a broader quality drive. That missing-index defect was real at the time.

As of 2026-08-28, the filing gap is repaired: Plan 105 is in the completed-plan archive, and Plans 106, 107 and 108 are all in backlog with explicit triggers. No planning-state action is owed from this recap.

Unattributed commits

None of the 23 non-merge commits names a plan in its subject or body:

Merges

Deferred to the next recap

651 commits sit after this window's end as of 2026-08-28.

git rev-list --count --all --since='2026-05-10 23:59:59'   # 651

That raw tail includes every following week through the current partial week. The complete weeks ending May 17, May 24, May 31, June 7, June 14, June 21, June 28, July 5, July 12, July 19, July 26, August 2, August 9, August 16 and August 23 are already covered. No following complete week is genuinely uncovered; the week ending August 30 is still in progress and is not yet recappable.