Adds the Sepo agent backend to this repository so @sepo-agent can answer, implement, review, and fix work on GitHub. This PR adds agent infrastructure only — no application source, secrets, or branch protection are changed.
Installed from the latest stable Sepo release v0.5.0 (self-evolving/repo).
.github/ — agent workflows (28), composite actions, prompts, issue templates, and assets, merged into the existing .github/.
.gitignore — appended .agent/dist/ and .agent/node_modules/.
Preserved / skipped
All target-owned .github/ files preserved; the conflict audit found no source path that collides with an existing target path.
Root README.md, AGENTS.md, and .skills/ were not copied (install defaults).
No application source changed.
Validation
npm ci, npm run build, and npm test pass on the source at v0.5.0 (run once against the identical payload).
git diff --cached --check is clean.
Conflict audit: no source .github path collides with an existing target path.
Skipped checks
Per-repo .agent build/test not rerun; the payload is byte-identical to the validated source revision.
This PR was created by an AI agent (OpenHands) on behalf of @ashcoft.
This change is
Summary by cubic
Installs the Sepo agent backend (.agent/) and merges the Sepo workflows, actions, and prompts into .github/ from self-evolving/repo v0.5.0, so @sepo-agent can answer, implement, review, and fix work in this repository. No application source, secrets, or branch protection change; target-owned .github/ files are preserved, and .gitignore now excludes .agent/dist/ and .agent/node_modules/.
Required setup after merge
Install the Sepo GitHub App on this repository and add at least one model-provider secret (OPENAI_API_KEY, ANTHROPIC_API_KEY, or CLAUDE_CODE_OAUTH_TOKEN).
Run the Agent/Onboarding/Check Setup workflow and complete anything its setup-check issue reports.
Run Agent/Memory/Initialization if agent/memory is missing; rubrics initialization is optional.
Confirm Issues and GitHub Actions are enabled.
Confidence Score: 2/5
Fix fork PR requests, concurrent memory publishing, and failed-push handoffs before merging.
### Issue 1
.github/workflows/agent-entrypoint.yml:12-17
Requests in fork PR bodies or inline reviews run without repository secrets. On GitHub-hosted runners, the router therefore cannot use the configured model credentials. Even an owner requesting a review this way gets a failed workflow instead.
Use a trusted default-branch entry path for these requests, while keeping fork code out of steps that receive credentials.
### Issue 2
.github/actions/run-agent-task/action.yml:549-559
Each task clones `agent/memory`, then `commit_memory` makes one plain push. If another task pushes first, Git rejects the second push. This step only warns and never retries, so the losing task's notes disappear with its temporary checkout.
Fetch and reconcile the newer branch before retrying the push.
### Issue 3
.github/workflows/agent-fix-pr.yml:330
After a rejected push, the status comment correctly becomes `failed`, but `SOURCE_CONCLUSION` still uses the earlier successful result. Because the handoff runs with `always()`, the orchestrator can launch a review of the unchanged remote PR.
Include the commit and push outcomes in the handoff result too.
### Issue 4
.agent/scripts/post-agent-verify.sh:18-24
`hasChanges` includes staged edits, and the commit helper publishes them. But `git diff --check` and `git diff --name-only` here inspect only unstaged changes. If the agent stages a runtime or workflow edit, that file can bypass the build or YAML check.
Include `git diff --cached` in both checks and the changed-file list.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Summary
Adds the Sepo runtime, GitHub workflows, shared actions, prompts, documentation, and tests.
GitHub requests can now be routed to the Sepo agent.
Sepo can now implement requests, review changes, and fix pull requests.
Sepo can use separate branches for repository memory and rubrics.
Repository workflows can now set up the Sepo runtime and its credentials.
Diagram
%%{init: {'theme': 'neutral'}}%%
flowchart LR
A[Mention or label] --> B[Router checks access]
B --> C[Answer or dispatch task]
C --> D[Run agent]
D --> E[Save memory]
D --> F[Verify edits]
F --> G[Push changes]
G --> H[Report result]
H --> I[Optional next task]