Fold in round-2 public-readiness nice-to-haves - #84
Merged
Conversation
…able row, wording cleanup - .github/ISSUE_TEMPLATE/config.yml: add a contact_links entry pointing would-be vulnerability reporters at SECURITY.md instead of a public issue, surfaced directly in GitHub's "new issue" picker. - CLAUDE.md: add a doc-sources-of-truth row for the top-level SECURITY.md added in #82 — every other doc file was already tracked for drift. - docs/USAGE.md: drop the last unnamed "a separate local project" reference that survived #82's aside cleanup; the sentence is now self-contained without pointing at unnamed prior art. - docs/ALERTING.md: split the run-on Discord-embed-shape sentence into two, separating the shape claim from the color-mapping claim. Not included, with reasons: - docs/OVERNIGHT.md's hardcoded `/root/.local/bin` PATH export in the bin/run-overnight.sh example: this is a verbatim copy of the real, currently-deployed script (CLAUDE.md's doc-sources table requires the two to match verbatim), and the script's own extensive comment block explains the hardcoding is deliberate -- Task Scheduler's minimal-env WSL launch needs an explicit path, and depending on $HOME instead was exactly the failure mode this script was written to route around. Genericizing the doc without changing (and re-verifying) the real script would create doc/script drift against a documented invariant, and changing the real nightly-scheduled script isn't something to do blind. Left alone. - Issue #77 (gateway naming in git history): unchanged -- rewriting published history is a separate, deliberate call, not a docs PR. Also deletes 24 stale, already-merged branches (confirmed via `gh pr list --state all --head <branch>`, or by ancestor check for one with no PR record). One additional stale branch, fix/cli-repo-validation-and-dashboard-batch-progress, was left alone -- it has 3 commits not reachable from main, i.e. real unmerged work, not safe to delete without a maintainer decision.
dmccoystephenson
added a commit
that referenced
this pull request
Aug 3, 2026
…able row, wording cleanup (#84) - .github/ISSUE_TEMPLATE/config.yml: add a contact_links entry pointing would-be vulnerability reporters at SECURITY.md instead of a public issue, surfaced directly in GitHub's "new issue" picker. - CLAUDE.md: add a doc-sources-of-truth row for the top-level SECURITY.md added in #82 — every other doc file was already tracked for drift. - docs/USAGE.md: drop the last unnamed "a separate local project" reference that survived #82's aside cleanup; the sentence is now self-contained without pointing at unnamed prior art. - docs/ALERTING.md: split the run-on Discord-embed-shape sentence into two, separating the shape claim from the color-mapping claim. Not included, with reasons: - docs/OVERNIGHT.md's hardcoded `/root/.local/bin` PATH export in the bin/run-overnight.sh example: this is a verbatim copy of the real, currently-deployed script (CLAUDE.md's doc-sources table requires the two to match verbatim), and the script's own extensive comment block explains the hardcoding is deliberate -- Task Scheduler's minimal-env WSL launch needs an explicit path, and depending on $HOME instead was exactly the failure mode this script was written to route around. Genericizing the doc without changing (and re-verifying) the real script would create doc/script drift against a documented invariant, and changing the real nightly-scheduled script isn't something to do blind. Left alone. - Issue #77 (a-private-repo naming in git history): unchanged -- rewriting published history is a separate, deliberate call, not a docs PR. Also deletes 24 stale, already-merged branches (confirmed via `gh pr list --state all --head <branch>`, or by ancestor check for one with no PR record). One additional stale branch, fix/cli-repo-validation-and-dashboard-batch-progress, was left alone -- it has 3 commits not reachable from main, i.e. real unmerged work, not safe to delete without a maintainer decision.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses the remaining actionable nice-to-haves from the round-2 public-readiness re-review (post-merge of #82), plus a large stale-branch cleanup.
.github/ISSUE_TEMPLATE/config.yml: adds acontact_linksentry pointing would-be vulnerability reporters atSECURITY.mdinstead of a public issue — surfaced directly in GitHub's "new issue" picker rather than requiring a reporter to read past the bug-report template first.CLAUDE.md: adds a doc-sources-of-truth row for the top-levelSECURITY.mdadded in Add top-level SECURITY.md #82 — every other doc file was already tracked for drift, this one wasn't.docs/USAGE.md: drops the last unnamed "a separate local project" reference that survived Add top-level SECURITY.md #82's "elsewhere in this ecosystem" cleanup — the sentence is now self-contained.docs/ALERTING.md: splits a run-on sentence (embed shape + color mapping mashed into one clause) into two.Also deletes 25 stale branches — 24 confirmed
MERGEDviagh pr list --state all --head <branch>, plusfeature/transcript-visibility(no PR record, but confirmed fully merged via ancestor check — zero commits ahead ofmain). One additional stale branch,fix/cli-repo-validation-and-dashboard-batch-progress, was deliberately left alone — it has 3 commits not reachable frommain, i.e. real unmerged work, not safe to delete without your call on it.Not included, with reasons:
docs/OVERNIGHT.md's hardcoded/root/.local/binPATH export, flagged in the review as low-priority/genericizable: on closer look this is a verbatim copy of the real, currently-deployedbin/run-overnight.sh(CLAUDE.md's doc-sources table requires the two match verbatim), and that script's own comment block explains the hardcoding is deliberate — Task Scheduler's minimal-env WSL launch needs an explicit path, and depending on$HOMEwas exactly the failure mode the script was written to route around. Changing the doc without changing (and re-verifying, live) the real nightly-scheduled script would just create drift against a documented invariant, and I'm not touching production automation blind. Left as-is.Test plan
/root/.venvs/gardener/bin/python3 -m unittest discover -s tests— 553 tests pass,OK.config.ymlparses as YAML (python3 -c "import yaml; yaml.safe_load(...)").MERGED, and confirmedfeature/transcript-visibilityhas zero commits ahead ofmainbefore deleting it.fix/cli-repo-validation-and-dashboard-batch-progresshas 3 commits not inmainbefore deciding to leave it.🤖 Generated with Claude Code