2 Commits

Include renames

Author	SHA1	Message	Date
Garry Tanandcapy-ai[bot]	ef99eb5a55	feat: retire /investigate after a no-gain eval (GST-1717) (#4110) ... * feat: retire /investigate after a no-gain eval (GST-1717) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(skill-start): core routing offer drops every non-core rule line (GST-1717) The retired /investigate rule became 'Bugs/errors → fix them directly', which no longer matches '→ invoke /', so proactive=core leaked it into the offered section. Match any '- … → ' rule line. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * revert(review): keep review/checklist.md at its no-loss-pinned bytes (GST-1717) The pin names replay GSTA-224 H1; a reviewer checklist edit merges only after a passing no-loss replay (crew rule 15). The /investigate flake line stays until a replayed repin. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: repair free-suite fallout from retiring /investigate (GST-1717) CI run 42340956269 at 83a8a9a: drop fixtures, ledger rows, allowlist entries and counts for the retired skill and its deleted paid files; record the harness change as non-behavioral; the test-of-test detector accepts path.join(ROOT, 'bin'); uncovered-prompt fixtures use a tracked prompt, since an untracked path now reads as a deleted one. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(relink): back up a retired skill's real SKILL.md before cleaning it (GST-1717) With the skill's source gone, the customized-file check never ran, so a banner-carrying local copy of investigate/SKILL.md was deleted instead of moved to the backup root (red-team review, pass 1). Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(qm): restore the review checklist's flake-line rewrite (GST-1717) review/checklist.md keeps its pinned /investigate line, so the QM edition needs its replaceText rule back; qm/ stays fresh against the generator. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(changelog): name the setup flag break, the relink backup and the pinned checklist line (GST-1717) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(setup,relink): back up a retired skill's real SKILL.md instead of deleting it (GST-1717) Scoped fix round under grant a-360dd62bd46a (outside-voice blocking finding and adversarial #1, #4). setup's prune compares a copied host entry with the render before removing that render, and backs up a copy that differs or whose render is gone; relink no longer takes the marker's rm -rf for a skill whose source is gone, so a real SKILL.md is backed up and the user's files stay. setup reports a failed remove-source of the retired gate hooks on stderr. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(pr-profile): a changed prompt counts as deleted only when it is gone from disk (GST-1717) An untracked prompt file on disk still needs prompt validation (targeted review finding); harness change recorded as non-behavioral. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(changelog): exact backup wording, the hook-removal warning and GST-1744 (GST-1717) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(setup): one backup folder per host for a retired skill's copies (GST-1717) Under grant a-c95576b8b1f9 (fix-check#1): every copy host moved its gstack-investigate/SKILL.md to the same backup path, so a later host's copy overwrote an earlier host's edits. A sandboxed ./setup --host factory run showed gen-skill-docs removes the retired render before the prune, so every real copy is backed up; each host now gets its own folder. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(changelog): say exactly what setup backs up for a retired skill (GST-1717) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(changelog): end the two colon sentences prose-lint flagged (GST-1717) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test(retired-skills): name plan-eng-review once behind a pregate-literal waiver (GST-1717) pregate's literals check read the GSTACK_RETIRED_SKILLS change as an old value still in the tests. plan-eng-review is still retired; investigate was appended. The fixture names it once, with the waiver. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>	2026-11-07 06:52:04 +00:00
Garry Tanandcapy-ai[bot]	ab9a854be2	v1.91.246.0 docs(readme): cut the README to the first ten minutes; move everything else to docs/ pages verbatim (GSTA-99) (#3428) ... * docs(readme): cut the README to the first ten minutes; move everything else to docs/ pages verbatim (GSTA-99) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: pre-landing review fixes Restore the /setup-gbrain code block the README split left open: README.md kept the ```bash opener and docs/gbrain-quick-tour.md got only the closing fence, so both pages rendered their body as one code block. Drop the self-referential 'Full reference' link in docs/domain-skills.md and make the troubleshooting quick-answer link an in-page anchor. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: describe the proactive core-set default in why-gstack The moved 'Proactive skill suggestions' paragraph now documents the four-skill core set, gstack-config set proactive core|all|off and the docs/proactive.md page that #3432 (gsta-99-proactive-core) adds; the CHANGELOG names it as the one non-verbatim paragraph of the move. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: pre-landing review fixes (round 2) Promote docs/uninstall.md's moved sections from ### to ## so the page outline matches the other pages the README split created; no inbound link targets those anchors. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: documentation audit fixes The README Docs table no longer claims docs/standalone-binaries.md covers every gstack-* CLI (it documents the standalone ones), and docs/ADDING_A_HOST.md step 6 points at the README host-matrix row and docs/hosts.md, where the per-host notes now live. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: disclose the update check fully and list every setup hook The README privacy summary now names both GitHub requests the update check makes and the version/OS report it adds with telemetry on, as the full text it replaced did. docs/install.md's hooks section lists the team-mode SessionStart hook and the AskUserQuestion PreToolUse/PostToolUse hooks beside the timeline Stop hook. * docs: name the update check's conditional compare-API request bin/gstack-update-check also GETs api.github.com's compare endpoint when the remote VERSION equals the local one but main has moved; the README privacy summary and docs/privacy.md now list it beside the ls-remote and VERSION fetch (documentation audit). * fix: pre-landing review fixes (merge resolution) docs/install.md:21 carried main's stable-channel sentence twice after the merge, the second copy with its backticked spans stripped; the paragraph again matches README.md:41 verbatim with the relative link. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: say outside reviews are on by default in the README privacy summary The one-paragraph summary dropped the default-on disclosure the full text kept; mirror docs/privacy.md's parenthetical so the top-level page says which path sends code off-machine without an opt-in. * v1.91.246.0 stamp Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>	2026-10-26 13:22:30 +00:00