feat(demo): Codeberg-primary tic-tac-toe demo repo with auto-deploy on release (v1.0.0 escalated) #382

New issue

Closed

opened 2026-07-04 20:29:48 +02:00 by bosun · 0 comments

bosun commented

2026-07-04 20:29:48 +02:00

Owner

Empirical finding (external cold-read round 4)

Round-2 filed the demo-repo need as v1.1.0 backlog (external reviewer named it "single biggest missing proof point" then). Round-4 external re-encountered the same gap and escalated it to v1.0.0 must-fix: without a public demo repo showing complete release lifecycle, external adopter cannot form trust before committing PAT to their own repo.

Operator ratified escalation 2026-07-04. Venue: Codeberg-primary (operator directive: 'Codeberg-primary or just pure Codeberg with a dedicated PAT'). Substrate: tic-tac-toe web game with auto-deploy on release to Codeberg Pages. Observer can play the game in-browser + inspect the release-toolkit substrate from a single URL.

Blocking rationale

External review 3× (rounds 2, 3, 4) has NOT moved the trust-threshold above 'promising but not yet trustworthy.' Substrate-empirical evidence + honest docs are necessary-but-not-sufficient; adopters need an inspectable live example. The demo repo IS the trust-threshold-mover.

Scope

Codeberg repo: codeberg.org/<operator>/tic-tac-toe (name confirmed 2026-07-04)
Bootstrap: fresh repo with initial commit + working tic-tac-toe (HTML+CSS+JS single-page, no build system)
release-toolkit wiring: consumer-wrapper pattern per docs/integration.md
First cuts: v0.1.0 (initial deployable) + v0.1.1 (fix) + v0.2.0 (feat) — real events, not synthetic
Auto-deploy: on release, deploy to Codeberg Pages via pages branch
README: links back to frankenbit/release-toolkit + names the demo relationship
Bidirectional link: frankenbit/release-toolkit README Positioning section flips Codeberg-primary from ⚠️ UNTESTED to ✓ demonstrated at demo URL
Dedicated PAT (CODEBERG_DEMO_TOKEN in /srv/.secrets, scopes: write:repository + write:issue)

Verification AC

Observer visits Codeberg URL, plays tic-tac-toe in browser (works end-to-end)
Observer inspects Releases tab, sees ≥3 tagged releases with real CHANGELOG entries
Observer inspects .forgejo/workflows/ + .release-toolkit.yml + can reproduce setup from docs alone
Round-5 external cold-read: no more 'need a demo repo to trust this' finding
release-toolkit README Positioning table shows Codeberg-primary ✓ with demo URL

Anchor

External outside-model cold-read round 4 (fresh ChatGPT session, 2026-07-03 late). Verdict: 'promising but not yet trustworthy' — SAME TIER as round-3 despite round-3 delta cycle. Meta-pattern named this round: grep-sweep-missed-siblings — the sweep-pattern targeted the literal grep-target, not the semantic class, so class-axis closed PARTIALLY per round. Operator ratified filing round-4 trackers 2026-07-04. This tracker addresses one of the round-4 findings. Success criterion: subsequent external cold-read returns no further objections of this class.

BLOCKING v1.0.0 (escalated from round-2 v1.1.0 backlog per round-4 verdict + operator directive 2026-07-04).

## Empirical finding (external cold-read round 4) Round-2 filed the demo-repo need as v1.1.0 backlog (external reviewer named it "single biggest missing proof point" then). Round-4 external re-encountered the same gap and escalated it to v1.0.0 must-fix: without a public demo repo showing complete release lifecycle, external adopter cannot form trust before committing PAT to their own repo. Operator ratified escalation 2026-07-04. Venue: Codeberg-primary (operator directive: 'Codeberg-primary or just pure Codeberg with a dedicated PAT'). Substrate: tic-tac-toe web game with auto-deploy on release to Codeberg Pages. Observer can play the game in-browser + inspect the release-toolkit substrate from a single URL. ## Blocking rationale External review 3× (rounds 2, 3, 4) has NOT moved the trust-threshold above 'promising but not yet trustworthy.' Substrate-empirical evidence + honest docs are necessary-but-not-sufficient; adopters need an inspectable live example. The demo repo IS the trust-threshold-mover. ## Scope - Codeberg repo: `codeberg.org/<operator>/tic-tac-toe` (name confirmed 2026-07-04) - Bootstrap: fresh repo with initial commit + working tic-tac-toe (HTML+CSS+JS single-page, no build system) - release-toolkit wiring: consumer-wrapper pattern per docs/integration.md - First cuts: v0.1.0 (initial deployable) + v0.1.1 (fix) + v0.2.0 (feat) — real events, not synthetic - Auto-deploy: on release, deploy to Codeberg Pages via `pages` branch - README: links back to frankenbit/release-toolkit + names the demo relationship - Bidirectional link: frankenbit/release-toolkit README Positioning section flips Codeberg-primary from ⚠️ UNTESTED to ✓ demonstrated at demo URL - Dedicated PAT (`CODEBERG_DEMO_TOKEN` in /srv/.secrets, scopes: `write:repository` + `write:issue`) ## Verification AC - Observer visits Codeberg URL, plays tic-tac-toe in browser (works end-to-end) - Observer inspects Releases tab, sees ≥3 tagged releases with real CHANGELOG entries - Observer inspects `.forgejo/workflows/` + `.release-toolkit.yml` + can reproduce setup from docs alone - Round-5 external cold-read: no more 'need a demo repo to trust this' finding - release-toolkit README Positioning table shows Codeberg-primary ✓ with demo URL ## Anchor External outside-model cold-read round 4 (fresh ChatGPT session, 2026-07-03 late). Verdict: 'promising but not yet trustworthy' — SAME TIER as round-3 despite round-3 delta cycle. Meta-pattern named this round: grep-sweep-missed-siblings — the sweep-pattern targeted the literal grep-target, not the semantic class, so class-axis closed PARTIALLY per round. Operator ratified filing round-4 trackers 2026-07-04. This tracker addresses one of the round-4 findings. Success criterion: subsequent external cold-read returns no further objections of this class. BLOCKING v1.0.0 (escalated from round-2 v1.1.0 backlog per round-4 verdict + operator directive 2026-07-04).

bosun added the

priority/high

size/L

kind/feature

labels

2026-07-04 20:29:48 +02:00

bosun referenced this issue

2026-07-04 23:33:00 +02:00

docs(positioning): declare release-toolkit Codeberg-primary — close round-4 positioning ambiguity #397

bosun referenced this issue

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

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