diff --git a/pm/JOURNAL.md b/pm/JOURNAL.md index cece665..011d58f 100644 --- a/pm/JOURNAL.md +++ b/pm/JOURNAL.md @@ -13,6 +13,24 @@ file carries the reasoning and the pointers. --- +## 2026-09-30 · repo · moved out of Nextcloud; code syncs only through Gitea + +**Why:** Nextcloud was syncing this repo's `.git`, which risks conflict copies inside +it and stalls the client's cold scan across dozens of repos. Nothing untracked is +data, so nothing is linked (`--no-data`); the move changed no test result (1,101 +pass, 2 skip before and after). +**Obligates:** #73, #74 +**Refs:** 4bedf85 (ci/apt-https pushed to clear the move's preflight), 63b421a + +## 2026-09-09 · ci · Linux R-CMD-check legs unblocked (recorded 2026-09-30) + +**Why:** GitHub's ubuntu-latest image carries a google-chrome apt source that +intermittently fails its own hash check, and setup-r's `apt-get update` died on it for +every R version; the source is now found by URL and removed, and the step fails +loudly if it survives. +**Obligates:** (none) +**Refs:** d83301b, d1165a5 + ## 2026-09-09 · model · #36 coverage counter finished, two bugs caught before merge **Why:** the drafted n_units_collected fix (uncommitted) derived its candidate diff --git a/pm/STATUS.md b/pm/STATUS.md index 860dd68..cc5141f 100644 --- a/pm/STATUS.md +++ b/pm/STATUS.md @@ -7,29 +7,30 @@ ## Where this stands -Three pieces of work landed and merged this session: the #33/#34 split (a pure -decomposition and a behavior fix, now independently tested and reviewed), and -#36 (the second `n_units_collected` coverage counter), which turned up two -real bugs -- a scoping leak and a hardcoded view name -- before either -shipped. All three issues are closed, CI is green on `main`, and a roborev -review pass on the intermediate commits caught one more small documentation -drop, now restored. One new issue (#72) tracks a coverage vignette that -neither existing walkthrough covers. +uscogdata's code now lives only in Gitea; the old Nextcloud folder keeps just build +output and working files. The move changed no test result: 1,101 pass and the two +opt-in live-corpus tests skip, before and after. It turned up one defect, #73: the +fixture's reference docs have never been in git, because a `.gitignore` rule matches +too broadly. Next in line are #73 and #72 (a vignette for the coverage counters), with +#52 (data-correction intake) and #74 (the stale state section in `CLAUDE.md`) waiting +on a decision. ## Ready to work on next +- **#73** The fixture corpus's docs/ never reaches git: .gitignore's docs/ rule is unanchored · `ws/corpus` — nothing is blocking it; something is currently wrong - **#72** docs: add a vignette explaining provenance$coverage counters · `ws/docs` — nothing is blocking it; owed work from an earlier change - **#2** Extend population data to be households as an alternate spending denominator · `ws/corpus` — nothing is blocking it - **#64** Partition-level caching: R/cache.R is still a stub, and the remote path pays for it every session · `ws/corpus` — nothing is blocking it +- **#74** CLAUDE.md's Current State section is frozen at 2026-08-03 · `ws/docs` — waiting on a person, not on other work - **#52** Release 11/11: design the data-correction intake (deferred; gates the API announcement) · `ws/corpus` — waiting on a person, not on other work ## Workstreams | Stream | Commits since | Open | Debt | Owes docs | |---|---|---|---|---| -| Query verbs and results | 5 | 0 | 0 | no | -| Corpus, mirror, provenance | 1 | 3 | 0 | **yes** | -| Vignettes and guides | 1 | 1 | 1 | **yes** | +| Query verbs and results | 0 | 0 | 0 | no | +| Corpus, mirror, provenance | 0 | 4 | 0 | no | +| Vignettes and guides | 0 | 2 | 2 | no | ## CI @@ -41,9 +42,9 @@ neither existing walkthrough covers. _Nothing blocks anything else, so there is no graph to draw._ -- Marker: `1ec20174` (2026-08-23) -- Commits since: 7 -- Open issues: 4 +- Marker: `9adb9211` (2026-09-09) +- Commits since: 3 +- Open issues: 6