4 Commits

Include renames

Author	SHA1	Message	Date
ffaerber	eeae1fdaaa	fix: deterministic dedup of agent double-posts (self-post + framework reply) (#109)	2026-07-08 09:35:19 +02:00
Felix FaerberandClaude Opus 4.8	e9df9d6bdd	agents: review round 2 — split-PR flow, thread recency, mention boundaries, learnings cap, pm model ... - publish.sh: resolve_prs matches ai/issue-N AND ai/issue-N-<slug> split branches (exact-only silently stalled DELEGATE:@qa and autopilot MERGE_PR on slugged work); qa hand-off lists all open PRs; autopilot refuses to merge multi-PR issues (drops the label, hands to the human) — merging one of several open PRs is half a change deployed. Retro's state=all resolve matches slugs too. - fetch-thread.sh: paginate and keep the NEWEST 100 comments — a bare limit=100 kept the OLDEST page and dropped recent decisions on long threads. - route.sh: word-boundary mention matching ("@internal" no longer routes to @intern); a comment with no real agent mention now SKIPS gracefully (mode=skip outputs + step guards in agent.yml) instead of a red run. - run-agent.sh: LEARNINGS.md cap is line-aware and keeps the NEWEST entries (retros append at the bottom; the old head -c cut the latest lessons first). - agents.json/README: @pm gemma4 -> minimax-m3 — the retro rule demands an investigating PM, and gemma4 posted 0 tool calls on every run; minimax is the model @qa demonstrably uses tools with. - agent.yml: document the PR-thread concurrency-group caveat. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-06 20:11:45 +03:00
Felix FaerberandClaude Opus 4.8	9b9e1e945d	agents: fix review findings — thread attribution, races, rescue stall, docs, CI ... Fixes from a full repo review: - fetch-thread.sh: attribute every comment to its REAL author (@pm/@qa/… — agents post as their own users now); the old "🤖 @name line at the top" hint pointed at headers we removed, leaving every teammate comment anonymous. Also strip the hidden loop-prevention marker from bodies (prompt noise). - agent.yml: per-issue concurrency group (queued, no cancel) — two quick comments on one issue no longer race the same ai/issue-N branch. - rescue-pr.sh: after opening a rescue PR, hand it back into the flow with an unmarked @pm trigger (the pm→qa choreography previously stalled silently on any rescued run); drop the old "🤖 **@name**" header style; add ops to the token case; mark the status note with the hidden marker. - README: token table said "@qa merges / TOKEN_QA needs write:repository" — inverted since the PM-orchestrated flow (@pm merges, autopilot only; @qa is read-only). Updated the agent table (descs, node1-ssh moved to homelab) and added a "How a task flows" section. - agents.json: pm/qa descs now describe the orchestrator/reviewer roles (these feed the roster prompt agents route by). - NEW ci.yml: bash -n + shellcheck(-S error) on every script, YAML-parse on every workflow, agents.json schema check — the ${x:-{}} brace bug would have been caught here before it shipped. - install-opencode.sh: pin opencode (default 1.17.13, override via OPENCODE_VERSION) — a breaking release no longer takes down every agent. - build-activity-log.sh: ollama/ollama-cloud models are subscription-billed (no $/token exists) — label the footer "subscription" instead of a misleading $0.0000; metered (anthropic) models keep the real dollar cost. - route.sh: document that mention-priority is list-order and load-bearing for the flow's trigger comments. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-06 09:47:34 +03:00
lead	36ba91cdd8	@lead: externalize agent.yml inline scripts into .gitea/workflows/scripts/*.sh ... Rebased onto the per-agent skill-scoping change so PR #25 carries both: - route.sh keeps the registry 'skills' allow-list and emits skills as a step output - install-opencode.sh writes the permission.skill block (deny-all + allow listed) Pure refactor otherwise: each step's shell moves to its own file, called via bash "$SCRIPTS/<name>.sh". The two extracted SKILL.md bodies are byte-identical to main; routing/config/publish behavior is unchanged. Because this is a reusable workflow (workflow_call) the runtime checkout is the caller's repo, so agent.yml now checks THIS repo out into .agents-workflow/ (pinned @main) and points $SCRIPTS there.	2026-07-04 05:54:27 +00:00