fix(jobs): run agents with unattended permissions

[owainlewis]

What changed

• run Codex jobs with danger-full-access and approval policy never
• run Claude jobs with bypassPermissions
• preserve configured backend permissions for chats and keep evaluators restricted
• reject non-zero Claude exits even when the JSON envelope says is_error: false
• document the unattended job security boundary
• prepare patch release v0.8.1

Root cause

Scheduled and manual jobs reused the normal chat runner, which delegated to backend permission defaults. In a headless run, required approval or sandbox access could not be granted. Claude output parsing also trusted a non-error JSON envelope without first enforcing the process exit status.

Impact

Codex and Claude jobs can now complete without an interactive operator. Chats retain their existing permission behavior. Job definitions execute with the OS permissions of the Push service user.

Verification

• cargo fmt --all --check
• cargo clippy --locked --all-targets -- -D warnings
• cargo build --locked
• cargo test --locked
• bash tests/install.sh
• bash tests/release-version.sh
• bash scripts/check-release-version.sh v0.8.1
• mkdocs build --strict
• independent subagent review: approved

[owainlewis]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 88da1e49d6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[owainlewis]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: 958a0ef9da

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".