f5968cfab5
Brings the framework CRS repo up to date with all content that was living in agent-runtimes (local-dev fallback) but hadn't been promoted. New composites: feature-delivery-loop, integration-direct, scaffolding-repo, sonnet-impl-narrow, sonnet-manager, test-writing-repo New contexts: integration/v1, scaffolding/v1, sonnet-manager/v1, z-ai/v1, airouter/v1/bin (anthropic-compat-wrapper.sh), cp-harness/v1/init.sh New task-templates: sonnet-integrator.yaml, workflow/* (17 typed workflow task templates for the Epic 1 pipeline) Updated: agent-repo/v1/finalize.sh — adds AR-38/F97 empty-deliverable audit (SKIP_BRANCH_PUSH support, boilerplate-path filtering, ci_metadata.json flag) Also adds MEMORY.md index and memory/ topic files for the framework repo.
1.3 KiB
Process Lessons
When verifying PR state via the Gitea API, dump the full JSON
Do not assert on a single key like state. Dump the response (json.dumps(..., indent=2)) and read state, merged, merged_at, and merge_commit_sha together. PRs that look "closed" may have been merged; PRs that look "open" may have a stale head SHA pointing at a deleted branch.
Fork-cleanup workflows must live on the fork, not the parent
When the goal is "clean up branches on a fork", commit the workflow to the fork's .gitea/workflows/. The parent repo's Actions runner does not see fork branches. Verify Gitea Actions is enabled on the fork (has_actions: true in the fork's repo metadata).
Use fetch-depth: 0 in cleanup jobs that inspect commit dates
Shallow clones omit the timestamps needed to decide "this branch has been inactive for 7 days". The cleanup job itself must use fetch-depth: 0 even if every other clone in the workflow is shallow.
Test the wrong-path detection by writing to the wrong path on purpose
When adding output validation + correction prompt, do a smoke test that deliberately writes the expected content to the wrong path. Confirm the sentinel .correction-prompt.txt is written and the entrypoint re-invokes the agent. Don't rely on accidental coverage.