toga-ai 1.0.7 → 1.0.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.7",
+  "version": "1.0.9",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",

package/skills/capture/SKILL.md

@@ -100,32 +100,68 @@ report success on an inconsistent knowledge base.
 
 ## Step 7 — Auto-push to share with teammates
 
-After validate + index succeed, stage and push only `knowledge/` changes directly to
-`feature/ai-harness-improvements`. CI picks up the push and publishes a new npm version
-automatically — teammates get it on their next `npx toga-ai`.
+After validate + index succeed, run through these checks in order before pushing.
+**Never skip straight to the push — the repo must be verified first.**
 
+### Pre-push checklist (run each check, stop at the first failure and fix it)
+
+**Check 1 — Is TEAM_REPO a git repository?**
+```bash
+git -C "<TEAM_REPO>" rev-parse --is-inside-work-tree
+```
+If this fails: the team repo is an npm bundle extract, not a git clone. Run:
+```bash
+git clone https://github.com/agilantsolutions/claude "<TEAM_REPO>"
+```
+Then re-run validate + index inside the freshly cloned repo before continuing.
+
+**Check 2 — Is origin set to the right remote?**
+```bash
+git -C "<TEAM_REPO>" remote get-url origin
+```
+Expected: `https://github.com/agilantsolutions/claude` (or the SSH equivalent).
+If wrong or missing: `git -C "<TEAM_REPO>" remote set-url origin https://github.com/agilantsolutions/claude`
+
+**Check 3 — Are the knowledge docs in TEAM_REPO, not just the project?**
+
+The docs you wrote in Steps 5–6 must exist inside `<TEAM_REPO>/knowledge/`, not only
+in `<project>/.claude/knowledge/`. If you wrote them to the project's `.claude/knowledge/`
+but not to `<TEAM_REPO>/knowledge/`, copy them now:
 ```bash
-# Stage only knowledge/ — never stage source code
+# Example — adjust paths to match what was written
+cp "<project>/.claude/knowledge/<path-to-doc>" "<TEAM_REPO>/knowledge/<path-to-doc>"
+```
+Then re-run `node "<TEAM_REPO>/knowledge.js" validate` to confirm they're valid there too.
+
+**Check 4 — Are there actually staged changes to push?**
+```bash
+git -C "<TEAM_REPO>" status --short knowledge/
+```
+If nothing shows: the docs were never written to TEAM_REPO. Go back to Check 3.
+
+---
+
+### Push (only after all 4 checks pass)
+
+```bash
+# Stage only knowledge/ — never stage anything else
 git -C "<TEAM_REPO>" add knowledge/
-git -C "<TEAM_REPO>" diff --cached --quiet || git -C "<TEAM_REPO>" commit -m "knowledge: <brief description of what was captured>"
+git -C "<TEAM_REPO>" diff --cached --quiet || \
+  git -C "<TEAM_REPO>" commit -m "knowledge: <brief description of what was captured>"
 
-# Push directly to the active development branch
+# Push to the active development branch
 git -C "<TEAM_REPO>" push origin HEAD:feature/ai-harness-improvements
 ```
 
-Replace `<brief description of what was captured>` with a one-line summary
-(e.g. `"knowledge: add clickup-deploy feature doc for worker2"`).
-
 **If push succeeds:** report
 > "✓ Knowledge pushed to `feature/ai-harness-improvements` — CI will publish a new npm version. Teammates get it on their next `npx toga-ai`."
 
-**If push fails** (offline, no credentials, diverged): do **NOT** error out. Report:
-> "⚠ Could not push — run `git -C <TEAM_REPO> push origin HEAD:feature/ai-harness-improvements` when ready"
-and still consider the capture session successful.
+**If push fails** — show the developer the exact git error output, then report:
+> "⚠ Push failed: `<error>`. Fix credentials or run manually:
+> `git -C <TEAM_REPO> push origin HEAD:feature/ai-harness-improvements`"
 
-Never stage anything outside `knowledge/`. If `git diff --cached` would include files
-outside `knowledge/`, abort the commit and warn: "Unexpected staged files outside
-`knowledge/` — push skipped. Review and push manually."
+Never stage anything outside `knowledge/`. If `git diff --cached` shows files outside
+`knowledge/`, abort and warn before committing.
 
 ## Step 8 — Report