every single hardcoded issue ref (ex `ward#123`) is wrong when you are on the wrong git remote

coilysiren commented

2026-07-01 21:56:44 +00:00

Owner

This is a problem all over the place. In every repo, not just ward. it needs a linter + a hard thorough scrub.

coilyco-ops referenced this issue

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

polish batch, run 16: jargon-audit (internal hostnames, cross-repo bare refs, unlinked insider tools) #449

coilyco-ops commented

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

Member

+1 — independently hit via github-only-dev/jargon-audit, run 16. The cross-repo variant (aos#310, cli-guard#178 — no host context at all) is called out in #449.
Filed by Claude Code during a cold-read release pressure test (run 16).

+1 — independently hit via github-only-dev/jargon-audit, run 16. The cross-repo variant (aos#310, cli-guard#178 — no host context at all) is called out in #449. Filed by Claude Code during a cold-read release pressure test (run 16).

coilyco-ops referenced this issue

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

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

coilyco-ops referenced this issue

2026-07-01 22:47:28 +00:00

Publish the full release binary matrix to GitHub releases, checksummed and CI-built from the same tags #454

coilyco-ops commented

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

Member

+1 — independently hit via drive-by-critic/docs-ia, run 36: every single doc read this session (README, FEATURES, agent*, container*, doctor) cites bare ward#NNN refs as load-bearing explanation; off-remote (GitHub mirror, HN thread, search snippet) none resolve.

coilyco-ops referenced this issue

2026-07-01 23:00:01 +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:47 +00:00

coilyco-ops added the

headless

P1

labels

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

coilyco-ops referenced this issue

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

documentation is inconsistent about linking to forgejo vs github #443

coilyco-ops commented

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

Member

DECISION - scrub target: every ref must resolve for a GitHub reader (full URLs, or refs valid on the GitHub mirror). Pairs with #443's rule (external copy GitHub-only). Linter + one hard scrub across ward's public surfaces gates launch; other repos are post-launch. 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

coilyco-ops referenced this issue

2026-07-02 00:20:38 +00:00

Use decode into rg pattern to keep clear of custom code #193

coilysiren referenced this issue

2026-07-02 07:10:55 +00:00

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

coilyco-ops commented

2026-07-02 07:51:54 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-446 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T07:51:52Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-ward-446` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T07:51:52Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 08:15:52 +00:00

fix(docs): scrub terse issue refs to full-URL links + add a linting gate

coilysiren closed this issue

2026-07-02 08:15:52 +00:00

coilysiren commented

2026-07-02 08:17:23 +00:00

Author

Owner

WARD-OUTCOME: done - added an issue-ref linter (ward exec lint-refs + pre-commit gate) and scrubbed terse refs to full-URL links across README, FEATURES, and every docs/*.md that fits its size cap.

The mechanical half was the easy half. Writing the detector that skips code fences, inline code (including the multi-line backtick span that tripped it once), and already-linked refs, then --fix rewriting the rest to full Forgejo URLs, went smoothly and self-tested well.

What fought back was a collision between two of ward's own rules: "every ref must resolve for a GitHub reader" (needs ~76-char Markdown links) versus the documentation-layout 4000-char cap that the deep design docs are hand-tuned to sit just under (3997-3999). You can't inline-link ~330 refs across 31 capped docs without busting the cap. I resolved it by treating those design docs as contributor-facing (terse Forgejo refs allowed per #443, same as source) and scrubbing everything that fits - README, FEATURES, and ~34 walkthrough docs. The front-page provenance refs (ward#455/#454/#356) I dropped rather than link-bloat, matching #444's "move the lore out" direction.

Confidence is high on the linter and the scrubbed surfaces (pre-commit green, build/test clean). The honest caveat is scope: the 31 exempted docs still carry terse refs, filed as #521 to trim-then-relink them once the provenance noise is cut. Also worth naming: origin/main advanced four times mid-run and each merge dragged in fresh bare refs from sibling launch work, so the linter earned its keep immediately by catching them before they landed.

WARD-OUTCOME: done - added an issue-ref linter (`ward exec lint-refs` + pre-commit gate) and scrubbed terse refs to full-URL links across README, FEATURES, and every `docs/*.md` that fits its size cap. The mechanical half was the easy half. Writing the detector that skips code fences, inline code (including the multi-line backtick span that tripped it once), and already-linked refs, then `--fix` rewriting the rest to full Forgejo URLs, went smoothly and self-tested well. What fought back was a collision between two of ward's own rules: "every ref must resolve for a GitHub reader" (needs ~76-char Markdown links) versus the documentation-layout 4000-char cap that the deep design docs are hand-tuned to sit *just* under (3997-3999). You can't inline-link ~330 refs across 31 capped docs without busting the cap. I resolved it by treating those design docs as contributor-facing (terse Forgejo refs allowed per #443, same as source) and scrubbing everything that fits - README, FEATURES, and ~34 walkthrough docs. The front-page provenance refs (ward#455/#454/#356) I dropped rather than link-bloat, matching #444's "move the lore out" direction. Confidence is high on the linter and the scrubbed surfaces (pre-commit green, build/test clean). The honest caveat is scope: the 31 exempted docs still carry terse refs, filed as #521 to trim-then-relink them once the provenance noise is cut. Also worth naming: origin/main advanced four times mid-run and each merge dragged in fresh bare refs from sibling launch work, so the linter earned its keep immediately by catching them before they landed.

Rows
Columns

every single hardcoded issue ref (ex ward#123) is wrong when you are on the wrong git remote #446

every single hardcoded issue ref (ex `ward#123`) is wrong when you are on the wrong git remote #446