skynet/claude-foundations
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: end-session — log, gac token correction in CLAUDE.md, FUTURE offload targets

Browse Source 
Claude-Session: https://claude.ai/code/session_01Ku87DDWwbJkTx6SuV3sQDc
This commit is contained in:
Paul O'Reilly
2026-09-11 13:56:44 +12:00
parent df243cd953
commit b6c976a00b
3 changed files with 35 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CLAUDE.md
View File

@@ -65,7 +65,7 @@ Then proceed directly to step 2. Otherwise:
## Gitea CI visibility
When working with Gitea (watching Actions runs, checking whether a release/container built, diagnosing failing CI), use `gitea-agent-companion` — alias `gac`, installed in `~/sbin`, source at `projects/gitea-agent-companion`. Run `gitea-agent-companion --help` first: the help text is the full reference (verbs, flags, token discovery, exit codes). Canonical post-push pattern: `gac tail <owner/repo> --until run-complete --timeout 600`; on failure, `gac inspect <owner/repo> --run <N> --logs`.
When working with Gitea (watching Actions runs, checking whether a release/container built, diagnosing failing CI), use `gitea-agent-companion` — alias `gac`, installed in `~/sbin`, source at `projects/gitea-agent-companion`. Run `gitea-agent-companion --help` first: the help text is the full reference (verbs, flags, token discovery, exit codes). Canonical post-push pattern: `gac tail <owner/repo> --until run-complete --timeout 600`; on failure, `gac inspect <owner/repo> --run <N> --logs` — or `/ci-triage-minimax owner/repo <N>` to triage a long failure log in MiniMax instead of in-session. Note: gac does NOT auto-discover the secrets-path token (as of v0.0.2.10) — set `GITEA_TOKEN_FILE=~/dev/claude/secrets/gitea/ai_admin/token` (the `token` file, not the directory); `ci-triage-minimax-run` defaults this itself.
## Subagent coding tasks — use `mm-worktree-task`