popagent

Latest change dc4b371554df3a78c40c29085ead1db3de7e24f8 - Add model routing policy, companyStatus tool, Markdown channel output, compact Runtime settings by AkurAI Build

# AkurAI Build integration

Build specialist roles and the AkurAI Build client. Framework facts live in
[AGENTS_AGENT.md](AGENTS_AGENT.md); operating rules in [AGENTS_RULES.md](AGENTS_RULES.md).

## Build roles

Persisted `build-maintainer`, `build-release-manager`, and `community-steward`
profiles are governed Mastra specialists. Build Maintainer has contained
read-write workspace access and no browser access; Release Manager and
Community Steward have no workspace or browser access. They use only their
role-specific typed tools in `src/tools/akurai-build.ts` for Build operations.
Build Maintainer can inspect and maintain repositories, runs, workers, cache,
audit, pipeline validation, metrics, and community content but cannot promote
protected environments. Build Release Manager owns explicit release and
protected-promotion operations and is never eligible for autonomous scheduling.
Community Steward is limited to public repository and issue/comment operations
and has no pipeline or deployment mutation. `AgentSettingsStore` rejects Build
tools on general roles and enforces each Build role allowlist.
Each Build specialist also has one source-owned workflow skill matching its
allowlist: `build-maintenance`, `governed-release`, or `public-community`.

The AkurAI Build client uses JSON-RPC MCP at `AKURAI_BUILD_URL` (default
`https://akurai-build.olibuijr.com`) and reads its bearer only from
`AKURAI_BUILD_API_KEY`. It initializes lazily, bounds request/response bodies
and timeouts, propagates aborts, strictly parses MCP results, and reports
disabled status when credentials are absent without logging credentials.

Idle `build-maintenance` work is persisted as a distinct task/schedule source
and uses a process-local autonomous lease in addition to the database gate, so
interactive and autonomous work cannot overlap accidentally. It runs only in
the writable `AkurAI-Build` workspace, delegates to Build Maintainer plus the
independent Reviewer, queues CI for the exact reviewed branch/ref, and records
branch/run/issue/comment evidence. The contained completion policy imports only
an allowed descendant commit after immutable checkout evidence; it never
promotes or deploys production for Build maintenance. Managed deployment reuses
immutable CI verification only when the exact 40-character revision and UTC
timestamp evidence are supplied.