ci: publish commit-addressed build artifacts

[christso]

Summary

CI now publishes a short-lived build bundle tied to the exact source commit and runner platform after the normal bun run build succeeds. Future workers can use that bundle as a reuse input only when the manifest proves the commit SHA, bun.lock hash, platform, Bun version expectation, and output paths all match.

The agent instructions now make the reuse boundary explicit: research workers should avoid installs/builds/tests/evals unless justified, implementation workers must rebuild packages they changed, and dependency/cache directories are not part of the build artifact contract.

Bead

av-3ae

Changed Files

• .github/workflows/ci.yml
• AGENTS.md
• .agents/workflow.md
• .agents/verification.md

Verification

• Parsed .github/workflows/ci.yml with PyYAML and asserted the build artifact steps, artifact name, retention, and expression balance.
• Ran bash -n against the extracted Stage build artifact script.
• Ran the embedded Bun manifest writer against a temp manifest and asserted the required fields.
• Ran git diff --check.
• Manually inspected the workflow diff for indentation, expression syntax, and artifact contents.
• Dedicated ce-code-review sub-agent review was skipped because the available sub-agent tool only permits spawning when the user explicitly asks for delegation; manual diff scan found no issues.

Not run: bun install, bun run build, full tests, or evals. This PR only changes GitHub Actions and repo instructions, and GitHub Actions remains the authoritative merge gate.

Post-Deploy Monitoring & Validation

Watch the next CI runs on this branch and after merge, focusing on the Build job steps named Stage build artifact and Upload build artifact.

Healthy signals: the Build job passes, the artifact named agentv-build-<os>-<arch>-<sha> is attached, and manifest.json includes the expected commit, lockfile hash, runner OS/arch, Bun version fields, timestamp, and four dist path globs.

Failure signals: missing expected dist paths, forbidden dependency/cache/tsbuildinfo path errors, upload failures, or an artifact missing the manifest. Rollback is reverting the workflow upload/staging change or temporarily removing the upload step if CI is blocked. Validation window: first three CI runs after merge, owned by AgentV maintainers.

---

[cloudflare-workers-and-pages]

Deploying agentv with    Cloudflare Pages

Latest commit:	e23f2e7
Status:	✅  Deploy successful!
Preview URL:	https://9fdb6adf.agentv.pages.dev
Branch Preview URL:	https://ci-av-3ae-build-artifact.agentv.pages.dev

View logs