[ThomasK33]

Why

Dependabot cannot update aube-lock.yaml. Its PRs (for example #173) change only package.json, and then every CI job fails at aube ci because the lockfile is out of date. This PR moves the repo from aube to pnpm, so dependency bots work again and contributors use one standard package manager.

What changed

1. Lockfile. aube-lock.yaml → pnpm-lock.yaml. aube already writes pnpm's lockfile v9 format, so I copied main's file and ran pnpm install. No resolved version changed: each of the 314 packages in main's aube lock is in the pnpm lock at the same version. The 62 new entries are platform variants of optional native bindings (esbuild, oxlint, oxfmt, rolldown, lightningcss) and the wasm fallback's deps (@emnapi/*, @napi-rs/wasm-runtime, @tybys/wasm-util). supportedArchitectures still limits which ones get installed.
2. package.json. packageManager: pnpm@10.34.5. The top-level overrides moved to pnpm.overrides (the same 11 pins as main). pnpm.allowBuilds became pnpm.onlyBuiltDependencies (the same 6 packages).
3. pnpm-workspace.yaml. Keeps supportedArchitectures and trustPolicyExclude. Adds minimumReleaseAge: 1440 and trustPolicy: no-downgrade, so we keep the supply-chain checks that aube ran by default.
4. mise. "npm:pnpm" = "10.34.5" replaces aube. npm.package_manager = "npm" makes mise install it with npm. Tasks: bootstrap = pnpm install && pnpm exec playwright install chromium, bootstrap-ci = pnpm install --frozen-lockfile, audit = pnpm audit --audit-level high. In mise.lock, the aube block became an npm:pnpm entry. I edited it by hand, because mise lock deletes the task-level ffmpeg conda entries.
5. Workflows. ci.yml (edited by hand): the jobs that list their mise tools (lifecycle-model, checks-macos, test-integration-macos) install npm:pnpm in place of aube. The other jobs install every tool with --locked. release.yml has a comment fix only.
6. New .github/dependabot.yml for npm (pnpm) and github-actions, weekly, with a 7-day cooldown. 7 days is zizmor's minimum, and it is longer than minimumReleaseAge.
7. verify-agent-tty skill. start-run.sh runs pnpm install --frozen-lockfile. The old script ran aube ci when node_modules/.bin/tsc was missing. pnpm's frozen install repairs a missing node_modules/.bin by itself (I deleted .bin and the install restored it), so one command covers both cases.
8. Docs. AGENTS.md, docs/CONTRIBUTING.md, docs/INSTALL.md, ADR 0009, .mux/init and the verify-agent-tty SKILL.md. I left CHANGELOG.md and the archived plans/ as they are, because they record history.

Design choices

• pnpm 10, not 11 or 12. GitHub's Dependabot docs list pnpm v7 to v10 as supported. pnpm v11 support was closed as done only on 2026-09-15 (dependabot-core#14794), and follow-up bugs are still open.
• npm build of pnpm, not the standalone binary. node-pty 1.1.0 has no Linux prebuilds, so its install script runs node-gyp rebuild. The npm build of pnpm bundles node-gyp. mise's standalone aqua:pnpm/pnpm binary does not, so the install fails with node-gyp: not found.

Validation

Local runs on a shared host with load average 40 to 90:

• Clean frozen install: rm -rf node_modules && mise run bootstrap-ci passed, and node-pty compiled.
• mise run --force of format-check, workflow-lint, lint, audit (0 high or critical, 6 moderate), typecheck, build, test-unit, install-smoke and validate-bundles: all exit 0.
• test-integration: 406 passed, 2 failed. test-e2e: 33 passed, 2 failed. All four are timing limits: list under 2000 ms in non-reaping-init.test.ts, a 5 s Chromium boot in backend-selection.test.ts, the color-grid idle wait in export-fixtures.test.ts, and the 30 s hello-prompt flow. A side-by-side run of those four files with --retry=0 on a main worktree installed with aube ci failed the same tests on this host (main: 8 of 19 failed, this branch: 9 of 19). This PR changes no file under src/. CI on GitHub runners is the gate for these.
• start-run.sh dependency step: with node_modules/.bin deleted, pnpm install --frozen-lockfile restored node_modules/.bin/tsc (exit 0).

Risks

• Release pipeline not run. release.yml, release-please.yml and npm publish run only on tags or dispatch. They use the same mise run bootstrap-ci and mise run ci paths tested here, and publishing still uses npm publish <tarball>.
• The mise.lock entry for npm:pnpm pins the version with no checksum. The mise npm backend records no checksum. The aqua backend does, but it cannot build node-pty.
• Dependabot is untested until it runs on main. Security updates skip the cooldown, so a fix published less than a day earlier can hit minimumReleaseAge. minimumReleaseAgeExclude is the escape hatch. pnpm.* settings in package.json work in pnpm 10. pnpm 11+ ignores them, so they must move to pnpm-workspace.yaml when we upgrade.
• Harmless npm warn Unknown env config lines during install. pnpm exports npm_config_* variables, and prepare calls npm run build, which warns about them.

---

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

[ThomasK33]

@codex review

[ThomasK33]

@codex security review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-05T18:20:43.822988Z	0a9ba97	Manual request
🔒 Security Review	🔄 Running since 2026-11-05T18:16:40.654840Z	0a9ba97	Manual request

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 0a9ba974a7

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