feat(demo): public disposable demo repo with recorded release lifecycle (v1.1.0 target) #360

New issue

Closed

opened 2026-07-03 23:42:49 +02:00 by bosun · 1 comment

bosun commented

2026-07-03 23:42:49 +02:00

Owner

Empirical finding (external cold-read round 2)

External reviewer named as "single biggest missing proof point":

A public, disposable demo repository with a complete recorded release lifecycle:

empty/fresh repo setup

exact config files added

push to main

release-prep PR created

changelog/version files updated

PR merged

tag created

Forgejo release created

manifest updated

rerun shown to be safe

Codeberg behavior shown separately if Codeberg is claimed

A real Forgejo Actions log plus final repo state would do more than ten pages of docs.

Backlog rationale (v1.1.0 target, not v1.0.0 blocker)

Real work: setup + fresh-repo bootstrap (blocked on #TBD-N1) + record Forgejo Actions runs + host as adopter-facing demo. Multi-day effort.

For v1.0.0: ship with honest disclosure that demo-repo is v1.1.0 target + name the constraint in README (adopters can inspect our own self-hosting substrate as proof-of-life until then).

Operator observation (2026-07-03 23:40): could naturally land when tmux-tell publishes to Codeberg — but current tmux-tell is GitHub-hosted, and mirroring to Codeberg would create release-mechanic conflicts (same recursive-bootstrap-lag class we've fought). Cleaner shape: a NEW demo project, not migrated tmux-tell.

Fix path (v1.1.0 or later)

New Forgejo/Codeberg repo (name TBD — 'release-toolkit-demo' or similar)
Minimal config using current release-toolkit
Recorded first-release lifecycle
Optionally: recorded upgrade scenarios (v0.x.0 to v0.y.0 config migration)
README linked from main release-toolkit README

v1.0.0 relationship

POST-v1.0.0 backlog with public commitment in v1.0.0 release notes: 'Demo repo target v1.1.0. In the interim, adopters can inspect our own self-hosting configuration as proof-of-life.'
Deferred with operator ratification 2026-07-03 23:35

Anchor

External outside-model cold-read round 2 (fresh ChatGPT session, 2026-07-03 late) returned new findings after Pilot Cold-Read delta had cleared. External verdict: 'promising but not yet trustworthy.' Operator ratified delta plan 2026-07-03 23:35. This tracker addresses one of the round-2 findings. Success criterion: subsequent external cold-read returns no further objections of this class.

## Empirical finding (external cold-read round 2) External reviewer named as "single biggest missing proof point": > A public, disposable demo repository with a complete recorded release lifecycle: > 1. empty/fresh repo setup > 2. exact config files added > 3. push to main > 4. release-prep PR created > 5. changelog/version files updated > 6. PR merged > 7. tag created > 8. Forgejo release created > 9. manifest updated > 10. rerun shown to be safe > 11. Codeberg behavior shown separately if Codeberg is claimed > > A real Forgejo Actions log plus final repo state would do more than ten pages of docs. ## Backlog rationale (v1.1.0 target, not v1.0.0 blocker) Real work: setup + fresh-repo bootstrap (blocked on #TBD-N1) + record Forgejo Actions runs + host as adopter-facing demo. Multi-day effort. For v1.0.0: ship with honest disclosure that demo-repo is v1.1.0 target + name the constraint in README (adopters can inspect our own self-hosting substrate as proof-of-life until then). Operator observation (2026-07-03 23:40): could naturally land when tmux-tell publishes to Codeberg — but current tmux-tell is GitHub-hosted, and mirroring to Codeberg would create release-mechanic conflicts (same recursive-bootstrap-lag class we've fought). Cleaner shape: a NEW demo project, not migrated tmux-tell. ## Fix path (v1.1.0 or later) - New Forgejo/Codeberg repo (name TBD — 'release-toolkit-demo' or similar) - Minimal config using current release-toolkit - Recorded first-release lifecycle - Optionally: recorded upgrade scenarios (v0.x.0 to v0.y.0 config migration) - README linked from main release-toolkit README ## v1.0.0 relationship - POST-v1.0.0 backlog with public commitment in v1.0.0 release notes: 'Demo repo target v1.1.0. In the interim, adopters can inspect our own self-hosting configuration as proof-of-life.' - Deferred with operator ratification 2026-07-03 23:35 ## Anchor External outside-model cold-read round 2 (fresh ChatGPT session, 2026-07-03 late) returned new findings after Pilot Cold-Read delta had cleared. External verdict: 'promising but not yet trustworthy.' Operator ratified delta plan 2026-07-03 23:35. This tracker addresses one of the round-2 findings. Success criterion: subsequent external cold-read returns no further objections of this class.

bosun added the

priority/medium

size/XL

kind/feature

labels

2026-07-03 23:42:49 +02:00

bosun commented

2026-07-05 11:26:28 +02:00

Author

Owner

Superseded by #382 (Codeberg-primary tic-tac-toe demo repo — v1.0.0 escalated), which took over this scope with concrete venue + operator-ratified 2026-07-04 escalation from v1.1.0-backlog to v1.0.0-must-fix.

Closing per operator 2026-07-05.

bosun closed this issue

2026-07-05 11:26:28 +02:00