memory: pushed v1.0.0b1, and a 'PUSHED' row that was stale when written

main and the annotated v1.0.0b1 tag are on origin; ahead 0, behind 0.

The push carried SIX commits, not the five this session produced: 2f85692 from
the previous session was still unpushed while the memory row above it said
PUSHED. A push is a point in time and this file is not, so the row now says to
run git rev-list rather than to believe it — the same class of error as
promoting a postbox send note into durable memory, twice in one day.
This commit is contained in:
vh
2026-09-22 21:58:46 -07:00
parent 2f6a0ee821
commit c47b3dba7e
+14 -2
View File
@@ -21,6 +21,10 @@ _As of 2026-09-22:_
- **U6 SHIPPED (`v0.6.0`) with a late fix (`v0.6.1`). PUSHED.** `main` and both - **U6 SHIPPED (`v0.6.0`) with a late fix (`v0.6.1`). PUSHED.** `main` and both
tags are on `origin` as of 2026-09-22 — the tree is no longer single-copy. tags are on `origin` as of 2026-09-22 — the tree is no longer single-copy.
⚠ **That "PUSHED" was already stale when written**: `2f85692` (the
no-announcements ruling) landed after it and sat unpushed until 2026-09-22
night. **Do not trust a "pushed" row — run `git rev-list --count
origin/main..HEAD`.** A push is a point in time; this file is not.
→ `persistent-memory.d/2026-09-22-u6-benches-released.md` → `persistent-memory.d/2026-09-22-u6-benches-released.md`
- **THE OPERATOR RULED ON EVERYTHING OUTSTANDING (2026-09-22, "accept all - **THE OPERATOR RULED ON EVERYTHING OUTSTANDING (2026-09-22, "accept all
recs").** Four of five settled and executed; one blocked by the permission recs").** Four of five settled and executed; one blocked by the permission
@@ -32,7 +36,8 @@ _As of 2026-09-22:_
→ `persistent-memory.d/2026-09-22-u7-landed-and-a-table-that-did-not-reproduce.md` → `persistent-memory.d/2026-09-22-u7-landed-and-a-table-that-did-not-reproduce.md`
- ✅ **RELEASED `v1.0.0b1` — the first 1.x release, staged as a BETA** (operator, - ✅ **RELEASED `v1.0.0b1` — the first 1.x release, staged as a BETA** (operator,
2026-09-22: "cut 1.0 beta 1"). Feature-complete, no new features, remaining 2026-09-22: "cut 1.0 beta 1"). Feature-complete, no new features, remaining
work is bugs. `1.0.0` final is cut when the beta survives. **NOT PUSHED.** work is bugs. `1.0.0` final is cut when the beta survives.
**PUSHED — `main` and the annotated tag are on `origin`; ahead 0, behind 0.**
→ `persistent-memory.d/2026-09-22-v1-staged-as-a-beta-and-a-second-copy-of-the-version.md` → `persistent-memory.d/2026-09-22-v1-staged-as-a-beta-and-a-second-copy-of-the-version.md`
- ⚠ **`booth/__init__.py` IS A FOURTH STDLIB-ONLY MODULE** and nothing said so - ⚠ **`booth/__init__.py` IS A FOURTH STDLIB-ONLY MODULE** and nothing said so
until now — `scripts/booth` executes it before every one of the documented until now — `scripts/booth` executes it before every one of the documented
@@ -56,8 +61,15 @@ _As of 2026-09-22:_
- ⚠ **A MUTATION HARNESS NEEDS A GREEN BASELINE AND CACHE DEFEAT**, or it - ⚠ **A MUTATION HARNESS NEEDS A GREEN BASELINE AND CACHE DEFEAT**, or it
certifies falsifiers without running them. Both defects bit in one session. certifies falsifiers without running them. Both defects bit in one session.
→ `persistent-memory.d/2026-09-22-a-mutation-harness-that-certified-a-broken-test.md` → `persistent-memory.d/2026-09-22-a-mutation-harness-that-certified-a-broken-test.md`
- **639 tests green; 12/12 new falsifiers mutation-proved. Deployed; 21/21 - **648 tests green; 12/12 U7 falsifiers mutation-proved. Deployed; 21/21
booths 200.** ⚠ The set churned again mid-session (19 → 21). booths 200.** ⚠ The set churned again mid-session (19 → 21).
- ✅ **THE MUTATION HARNESS IS NOW `scripts/mutation_check.py`** (operator,
2026-09-22: "keep the harness"). Tables in `tests/mutations/*.toml`, one per
unit — **add a unit by adding a file, never by editing the script.** It has
its own positive and negative controls in `tests/test_mutation_check.py`,
including a known-vacuous falsifier it must catch. **When you write a
`*Falsifiable:*` line, add its row and run it** — a falsifier nobody has run
is a claim, not a test.
- 🔶 **A bug-hunt panel is IN FLIGHT** — heid thread `01M368G2Y0JMTJ2T7M3JMTXV5Z`, - 🔶 **A bug-hunt panel is IN FLIGHT** — heid thread `01M368G2Y0JMTJ2T7M3JMTXV5Z`,
dispatched 2026-09-22 21:31 PDT over the U7-groups diff. If its reply has not dispatched 2026-09-22 21:31 PDT over the U7-groups diff. If its reply has not
been consumed, drain `/althing:inbox` and triage before treating U7 as closed. been consumed, drain `/althing:inbox` and triage before treating U7 as closed.