docs(positioning): release-toolkit README cross-link to tic-tac-toe demo + Codeberg-primary test-state update #412

Closed
opened 2026-07-05 20:28:47 +02:00 by bosun · 0 comments
Owner

Empirical finding

#382 demo repo at codeberg.org/FrankenBit/tic-tac-toe has demonstrated release-toolkit end-to-end on Codeberg-primary:

  • Fresh-repo bootstrap via v0.26.0's #368 virtual-anchor path fired correctly (first-in-the-wild empirical proof of the round-2 N1 finding closure)
  • Full release cycle end-to-end: rolling PR (release-prep/rolling) → merge → cut fires → draft release created → manifest committed
  • Both operational paths demonstrated in the release history:
    • v0.1.0: graceful no-token flow (manifest bookkeeping PR#2 required manual merge, draft release awaited operator Publish click)
    • v0.1.1+ (in flight): elevated-token flow via RELEASE_TOOLKIT_TOKEN (manifest direct-committed, cleaner history)
  • Runner label: codeberg-small-lazy from Codeberg's shared runner pool (cold-start ~1-2 min, otherwise clean)
  • Codeberg unit toggles required: has_actions + has_releases both default OFF for new repos, adopter enables both

Scope

Step 1 — Update release-toolkit README Positioning section:

  • Codeberg-primary axis: flip from ⚠️ UNTESTED to ✓ demonstrated at codeberg.org/FrankenBit/tic-tac-toe
  • Add brief companion-demo line naming the tic-tac-toe repo as adopter-inspectable reference

Step 2 — Sweep for Codeberg-untested/unknown notes across docs:

  • Grep docs/ + README.md + AGENTS.md for phrases like 'untested', 'not tested on Codeberg', 'Codeberg support unknown', 'requires verification' scoped to Codeberg positioning
  • Update each to reflect empirical Codeberg-primary demonstration
  • Include Codeberg-specific adopter notes if useful: unit-enablement requirement, runner labels, no-token graceful degradation

Step 3 — Cross-link from tic-tac-toe repo to release-toolkit (Bosun-side):

  • Tic-tac-toe README already references release-toolkit
  • No additional edit needed there unless a stronger 'companion demo of' framing helps

Verification AC

  • Reader visiting release-toolkit README arrives at 'Codeberg-primary ✓ demonstrated at codeberg.org/FrankenBit/tic-tac-toe' as the answer, not a matrix with an UNTESTED asterisk
  • Grep for 'untested'/'unknown' Codeberg positioning strings returns zero adopter-facing hits
  • External cold-read round 5 finds no positioning-tested-state ambiguity
  • Closes #382's cross-link AC ('release-toolkit README Positioning section flips Codeberg-primary from ⚠️ UNTESTED to ✓ demonstrated at demo URL')
  • Sibling to #397 (Codeberg-primary positioning declared) — this closes the empirical-evidence loop that positioning promised
  • Sibling to #407 (adopter wiring @ref drift, closed via PR#410) — same adopter-doc-coherence class
  • Related to #409 (per-project config override docs) — Herald can bundle both docs surfaces if scope allows

Anchor

Operator ratified filing 2026-07-05 during #382 demo empirical validation. Herald docs territory (prose-craft + fresh-lens discipline as PR#387/#393/#410). Standing approval merge on Surveyor stamp.

## Empirical finding #382 demo repo at [codeberg.org/FrankenBit/tic-tac-toe](https://codeberg.org/FrankenBit/tic-tac-toe) has demonstrated release-toolkit end-to-end on **Codeberg-primary**: - Fresh-repo bootstrap via v0.26.0's #368 virtual-anchor path fired correctly (first-in-the-wild empirical proof of the round-2 N1 finding closure) - Full release cycle end-to-end: rolling PR (release-prep/rolling) → merge → cut fires → draft release created → manifest committed - Both operational paths demonstrated in the release history: - **v0.1.0**: graceful no-token flow (manifest bookkeeping PR#2 required manual merge, draft release awaited operator Publish click) - **v0.1.1+ (in flight)**: elevated-token flow via `RELEASE_TOOLKIT_TOKEN` (manifest direct-committed, cleaner history) - Runner label: `codeberg-small-lazy` from Codeberg's shared runner pool (cold-start ~1-2 min, otherwise clean) - Codeberg unit toggles required: `has_actions` + `has_releases` both default OFF for new repos, adopter enables both ## Scope **Step 1 — Update release-toolkit README Positioning section**: - Codeberg-primary axis: flip from ⚠️ UNTESTED to ✓ demonstrated at [codeberg.org/FrankenBit/tic-tac-toe](https://codeberg.org/FrankenBit/tic-tac-toe) - Add brief companion-demo line naming the tic-tac-toe repo as adopter-inspectable reference **Step 2 — Sweep for Codeberg-untested/unknown notes across docs**: - Grep docs/ + README.md + AGENTS.md for phrases like 'untested', 'not tested on Codeberg', 'Codeberg support unknown', 'requires verification' scoped to Codeberg positioning - Update each to reflect empirical Codeberg-primary demonstration - Include Codeberg-specific adopter notes if useful: unit-enablement requirement, runner labels, no-token graceful degradation **Step 3 — Cross-link from tic-tac-toe repo to release-toolkit** (Bosun-side): - Tic-tac-toe README already references release-toolkit - No additional edit needed there unless a stronger 'companion demo of' framing helps ## Verification AC - Reader visiting release-toolkit README arrives at 'Codeberg-primary ✓ demonstrated at codeberg.org/FrankenBit/tic-tac-toe' as the answer, not a matrix with an UNTESTED asterisk - Grep for 'untested'/'unknown' Codeberg positioning strings returns zero adopter-facing hits - External cold-read round 5 finds no positioning-tested-state ambiguity ## Related - Closes #382's cross-link AC ('release-toolkit README Positioning section flips Codeberg-primary from ⚠️ UNTESTED to ✓ demonstrated at demo URL') - Sibling to #397 (Codeberg-primary positioning declared) — this closes the empirical-evidence loop that positioning promised - Sibling to #407 (adopter wiring @ref drift, closed via PR#410) — same adopter-doc-coherence class - Related to #409 (per-project config override docs) — Herald can bundle both docs surfaces if scope allows ## Anchor Operator ratified filing 2026-07-05 during #382 demo empirical validation. Herald docs territory (prose-craft + fresh-lens discipline as PR#387/#393/#410). Standing approval merge on Surveyor stamp.
herald self-assigned this 2026-07-05 20:30:03 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
frankenbit/release-toolkit#412
No description provided.