fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(agents): the formats-pin tag count is 7, and the disk figures have moved

Browse Source 
Re-checked against the server rather than the page. `Sylpheed` has 7 tags and
all 7 are `formats-pin-*`. The eighth this page counts, `formats-pin-2026-08-29`
without a letter suffix, is in `Syplheed-Reborn` — a repo a Sylpheed rewrite
would not touch, and one Phase 5 archives read-only regardless.

The pin itself is exactly as claimed: `formats-pin-2026-09-01` resolves to
`1cd5b8b1`, and the in-container build fetches that git dependency over the
network for real, so the blocker is live rather than theoretical.

Also updates the disk figures the "don't rewrite" recommendation rests on: 90%
used and 96 GB free, not 83% and 154 GB, with `target/` at 34 GB. The
recommendation is unchanged and the argument is now stronger — reclaiming
118 MB by rewriting history while 34 GB of rebuildable output sits beside it is
the wrong lever.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Fabian Hamm
2026-09-14 21:25:53 +02:00
parent 5f5851273d
commit 83b49ee0c1
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/agents/CONSOLIDATION.md
View File

@@ -435,12 +435,23 @@ blocker:
sylpheed-formats = { git = "…/Sylpheed.git", tag = "formats-pin-2026-09-01" }
```
**The build depends on this repo by tag**, pinned in `Cargo.lock` to `#1cd5b8b1`.
A rewrite invalidates all 8 `formats-pin-*` tags, every commit SHA, PR #23's
**The build depends on this repo by tag**, pinned in `Cargo.lock` to `#1cd5b8b1`
— re-checked 2026-09-14, and the pin is exactly right: `formats-pin-2026-09-01`
→ `1cd5b8b1`, and the in-container build fetches it over the network for real.
A rewrite invalidates every `formats-pin-*` tag, every commit SHA, PR #23's
merge, both agents' clones, and needs a force-push through branch protection.
* **Don't rewrite** (recommended): 118 MB on a host with 154 GB free, where
`Sylpheed/target` alone is 32 GB. The cost is not worth the blast radius.
📌 **The tag count is 7, not 8** — server and local agree, and all 7 tags in
`Sylpheed` are `formats-pin-*`. The eighth, `formats-pin-2026-08-29` (no letter
suffix), lives in **`Syplheed-Reborn`**, which a Sylpheed rewrite would not
touch and which Phase 5 archives read-only anyway. It does not change the
decision; it is one fewer thing to re-cut.
* **Don't rewrite** (recommended): 118 MB — and the disk argument has moved.
The host is now at **90 %, 96 GB free** (this page said 83 % / 154 GB), and
`Sylpheed/target` alone is **34 GB**. Reclaiming 118 MB by rewriting history,
while 34 GB of rebuildable build output sits beside it, is still the wrong
lever.
* **Do rewrite:** then it happens **here, in Phase 5** — while tags are being
re-cut and agents re-cloned anyway, so the disruption is paid once instead of
twice. Re-point the `formats-pin` dependency **first**.