Recover presenter work after failures and cancellation

[itsjling]

Closes #11

Summary

• Build missing presenter assets once and report a clear failure if the build does not produce them.
• Keep failed agent work recoverable without starting a retry loop.
• Stop active work on cancellation, keep finished notes, and resume only queued work on restart.
• Test browser selection and launch failures across supported operating systems.
• Ship the new presenter runtime module in the npm package.

Stack

• Base: Make the presenter headless and automation-friendly #48 (issue Make the presenter headless and automation-friendly #26).
• Cross dependency: Keep review notes outside target repos #43 (issue Preserve target repos and make note provenance exact #19). This PR relies on its note provenance and target storage contract but does not include that branch.

Verification

• npm run lint
• npm test (79 tests)
• npm run docs:check
• npm run docs:build
• npx fallow audit --base codex/issue-026-headless-presenter
• npm pack --dry-run --json --ignore-scripts includes scripts/presenter-runtime.mjs

Stack

1. Make the presenter headless and automation-friendly #48
2. Recover presenter work after failures and cancellation #57 👈 current

[itsjling]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2cd467db0

ℹ️ 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".

[itsjling]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 032b4ef581

ℹ️ 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".