README's only bug-report link points to a GitHub repo that doesn't exist

coilyco-ops commented

2026-07-01 21:38:02 +00:00

Owner

Why

Persona: forgejo-selfhoster (angle: yaml-config, but hit on first-screen read of the README before reaching the config work). The README's "Support" section reads:

Bug or feature request: [create a new issue][new-issue]

[new-issue] resolves to https://github.com/coilyco-flight-deck/ward/issues/new/choose. That URL 302s to https://github.com/login?return_to=... - GitHub's sign-in wall, which is what unauthenticated visitors get when the target repo does not exist (or is private) on github.com. This repo lives on forgejo.coilysiren.me/coilyco-flight-deck/ward and has no GitHub mirror. Every visitor who wants to report a bug or ask a question - the single support path the README offers - hits a dead end pointing at the wrong forge, with no visible signal that anything is wrong (no 404, just a login prompt that looks routine).

This is the exact "hard-paired to Forgejo" class of miss the pressure-test effort is calibrated against: a claim/link that is silently false unless you already know to distrust it.

Deliverable

Point [new-issue] in README.md at the real Forgejo issue tracker (https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/new/choose or equivalent), or, if a GitHub mirror is planned, gate the link behind its existence.

Done condition

The "create a new issue" link in README.md resolves (anonymously, no login) to a working issue-creation page on the platform that actually hosts ward.

Severity: adoption-fatal · persona: forgejo-selfhoster · angle: yaml-config
Filed by Claude Code during a cold-read release pressure test (run 3). Related: ward#414 (github equivalents) - this is a sharper, independently dispatchable sub-finding: the existing link is actively broken, not just missing an equivalent.

## Why Persona: `forgejo-selfhoster` (angle: `yaml-config`, but hit on first-screen read of the README before reaching the config work). The README's "Support" section reads: > Bug or feature request: [create a new issue][new-issue] `[new-issue]` resolves to `https://github.com/coilyco-flight-deck/ward/issues/new/choose`. That URL 302s to `https://github.com/login?return_to=...` - GitHub's sign-in wall, which is what unauthenticated visitors get when the target repo does not exist (or is private) on github.com. This repo lives on `forgejo.coilysiren.me/coilyco-flight-deck/ward` and has no GitHub mirror. Every visitor who wants to report a bug or ask a question - the single support path the README offers - hits a dead end pointing at the wrong forge, with no visible signal that anything is wrong (no 404, just a login prompt that looks routine). This is the exact "hard-paired to Forgejo" class of miss the pressure-test effort is calibrated against: a claim/link that is silently false unless you already know to distrust it. ## Deliverable Point `[new-issue]` in `README.md` at the real Forgejo issue tracker (`https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/new/choose` or equivalent), or, if a GitHub mirror is planned, gate the link behind its existence. ## Done condition The "create a new issue" link in `README.md` resolves (anonymously, no login) to a working issue-creation page on the platform that actually hosts `ward`. --- **Severity: adoption-fatal** · persona: forgejo-selfhoster · angle: yaml-config Filed by Claude Code during a cold-read release pressure test (run 3). Related: ward#414 (github equivalents) - this is a sharper, independently dispatchable sub-finding: the *existing* link is actively broken, not just missing an equivalent.

coilyco-ops added the

pressure-test

label

2026-07-01 21:38:02 +00:00

coilyco-ops referenced this issue

2026-07-01 21:39:05 +00:00

meta: release pressure-test run log (cold-read usability sweeps) #428

coilyco-ops commented

2026-07-01 21:51:35 +00:00

Author

Owner

+1 — independently hit via forgejo-selfhoster/front-page, run 8.

coilyco-ops referenced this issue

2026-07-01 21:51:59 +00:00

meta: release pressure-test run log (cold-read usability sweeps) #428

coilyco-ops commented

2026-07-01 21:55:39 +00:00

Author

Owner

Correction with evidence: the GitHub repo does exist. https://github.com/coilyco-flight-deck/ward returns HTTP 200; the GitHub API reports full_name coilyco-flight-deck/ward, has_issues=true (0 open), last updated 2026-07-01T14:52Z. What an anonymous checker sees as broken is the README's deep link (/issues/new/choose), which 302-redirects to GitHub login for logged-out users. The underlying real problem — canonical-vs-mirror support-channel confusion — is tracked in #438; suggest folding this issue into that one so the burndown doesn't carry a 'repo doesn't exist' claim that would misdirect the fix.
Filed by Claude Code during a cold-read release pressure test (run 12 dedup pass).

Correction with evidence: the GitHub repo does exist. https://github.com/coilyco-flight-deck/ward returns HTTP 200; the GitHub API reports full_name coilyco-flight-deck/ward, has_issues=true (0 open), last updated 2026-07-01T14:52Z. What an anonymous checker sees as broken is the README's deep link (/issues/new/choose), which 302-redirects to GitHub login for logged-out users. The underlying real problem — canonical-vs-mirror support-channel confusion — is tracked in #438; suggest folding this issue into that one so the burndown doesn't carry a 'repo doesn't exist' claim that would misdirect the fix. Filed by Claude Code during a cold-read release pressure test (run 12 dedup pass).

coilyco-ops referenced this issue

2026-07-01 21:55:39 +00:00

meta: release pressure-test run log (cold-read usability sweeps) #428

coilyco-ops added this to the ward launch milestone

2026-07-01 23:29:43 +00:00

coilyco-ops added the

labels

2026-07-01 23:30:43 +00:00

coilyco-ops referenced this issue

2026-07-01 23:56:36 +00:00

GitHub mirror repo hygiene: issue templates, topics/description parity, front-door signals #490

coilyco-ops added

and removed

labels

2026-07-01 23:57:30 +00:00

coilyco-ops commented

2026-07-01 23:58:20 +00:00

Author

Owner

DECISION - per the GitHub-front-door call (#438), the fix is to make the GitHub tracker real and pointed-at: #490 ensures issues + templates exist on the mirror; this ticket verifies/updates the README [new-issue] link to a URL that resolves unauthenticated. Closes with or right after #490. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

coilyco-ops referenced this issue

2026-07-02 00:01:42 +00:00

meta: jul 1st evening sprint - launch burndown session 1 #492

coilysiren commented

2026-07-02 02:57:47 +00:00

Owner

Verification close from the ward#492 burndown director: github.com/coilyco-flight-deck/ward exists, loads, and has Issues enabled (verified live 2026-07-02 ~02:57Z) - the README's [new-issue] link target resolves, so the dead-repo claim no longer reproduces. Template-chooser richness at /issues/new/choose rides ward#490 (issue templates land there). Closing via the issue API. Recorded by Claude Code (Fable) during the ward#492 burndown session.

coilysiren closed this issue

2026-07-02 02:57:47 +00:00

Rows
Columns

README's only bug-report link points to a GitHub repo that doesn't exist #433

Why

Deliverable

Done condition