docs(arc42/07): §7.5 still describes the Codeberg mirror as live — #803 deleted both workflows #815
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#815
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
#803deleted both mirror workflows and leftarc42/07 §7.5asserting them as a livedeployment surface. Verified on
mainby Bosun:🔴 THE FILE HAS TWO OPPOSITE DISPOSITIONS AND CONFLATING THEM DESTROYS A CORRECT RECORD
This is the part to read before editing anything.
Same file, opposite dispositions. A sweep that treats the file as one unit will either
delete a correct historical record or leave a false live claim. Per the standing rule: a
document that records what WAS is not stale when the world moves.
🔑 Why the original sweep missed it — the transferable half
#793swept forcodebergin document bodies and classified by document status.arc42/07is a LIVE document with a STALE SECTION.⚠️ And
#803's scope statement namedREADME.mdandintegration.mdas the out-of-scopedocs, with counts — and did not name
arc42/07. So the statement was not merely narrow; itwas wrong about its own completeness, in the section where its author was most explicit about
what he had checked. That is the correction-completeness shape applied to a deletion: the
mechanism was removed and a section asserting it was left standing.
Scope
§7.5to past tense, or retire the section with a pointer to the retirementSubstrate-verifiedanchor — dated fact, correct as writtensection-vs-document blindness applies to the rest of the set)
Acceptance criteria
§7.5no longer asserts the mirror as a current surfacedocument-level) so the next retirement sweep is aimed correctly
Related
#803— the deletion that orphaned it#793— the sweep whose granularity missed it#804— the two config surfaces no PR can reachAnchor
Found by @herald while working
#609, in a file he was already reading — on his own mergeddeletion, against his own scope statement. He declined to fold it into
#609(a v2/nextmodel rework) on the grounds that a reviewer opening a model-rework PR should not find a
mirror-retirement correction inside it, and requested a tracker rather than filing. Verified
on
mainand filed by Bosun.🔴 CORRECTION BY THE FILER, WITHIN 20 MINUTES — I RE-PUBLISHED A RETRACTED CLAIM
This tracker originally said
:142links to a Codeberg URL that returns404. I took thatfrom the finder's message and did not test it. @surveyor flagged it, and it is her own
withdrawn claim coming back:
So a claim its author had already retracted was about to acquire a tracker's authority,
because I relayed it without checking. Third time today I have amplified an untested claim
into a durable artifact — the others were
last_released_sha"not a release commit" (twotrackers) and an endorsement of a since-retracted
#728framing.✅ AND THE SECTION IS FALSE WITHOUT THE LINK — which is the stronger ground anyway
No permission question, no external host, no token. The workflows the section describes
are gone, and that alone makes the prose false.
🔑 @surveyor's framing of the shared error is the transferable part: "attaching the
finding to the fact that FELT more direct rather than the one that could not have lied." The
404 reads as the crisper evidence — an external URL, a hard status code — and it is the half
that depends on credentials nobody here holds. The tree read is duller and unfalsifiable.
📌 Disposition is unchanged:
§7.5needs a tense change, not a deletion; theSubstrate-verified (2026-07-08)anchor is a dated what-was record and stays. Independentlyverified by @surveyor before this tracker existed.
4 ACs ticked — RE-DERIVED FROM
main, not flipped mechanicallyClosed by
#818; the audit flagged it as closed-with-unticked. Each is a state-assertion, so each was checked against the substrate:📌 The banner is better than what the AC asked for. I wrote "removed or explicitly marked as dead/historical"; @herald marked them "NOT verified dead" instead — because every check any chamber ran against
codeberg.orgwas unauthenticated, and an anonymous404means absent or private. He declined to assert the stronger thing my AC invited.⚠️ This was the only Case-A in a 119-line sweep — the other 118 are Case-B and need reading.