Prove successful installed App Builder CLI generation

[kattsushi]

Requested outcome

Part of #131, review Unit 6A. Prove the successful App Builder path through the packed and installed public CLI executable.

Problem

The current E2E proof must exercise the packed and installed node_modules/.bin/effectify-app-builder executable. Private generation imports, private proof aliases, and fabricated workspace or test helpers do not prove the public delivery boundary.

Scope

• Drive the installed node_modules/.bin/effectify-app-builder through its JSONL generation flow.
• Generate an isolated custom workspace using operations-workspace, npm scope @acme, domain Operations, entity Task / Tasks, and entrypoint AdminConsole / admin-console.
• Prove the exact four-project Nx graph: @acme/operations-domain, @acme/operations-application, @acme/operations-infrastructure, and @acme/admin-console.
• Run the generated @acme/admin-console:test, @acme/admin-console:typecheck, and @acme/admin-console:build targets successfully.
• Exercise the generated Live runtime with a UUID-backed add, complete, and remove CRUD sequence, then prove the final persisted state is exactly empty.
• Regenerate from the same request and prove byte-identical output with zero changed paths and zero second-write paths.
• Prove success cleanup for the isolated workspace, package store, and Nx daemon, plus isolation from the repository root Nx graph.
• Remove private proof aliases, private generation wiring, and fabricated workspaceFiles() / proofTest evidence paths.

Acceptance criteria

• The named E2E test R14 and S25-S27 generate a custom workspace through the public CLI, run Nx and Live runtime, and replay cleanly passes through the installed executable with generate --events=jsonl.
• Runtime evidence records successful CLI installation, generation, dependency installation, exact Nx graph inspection, generated test/typecheck/build, Live runtime execution, and regeneration.
• The graph contains exactly the four scoped projects named above.
• Runtime evidence contains one valid UUID and the matching added, completed, and removed events, with final persisted state exactly []\n.
• Regeneration reports changedPaths: [] and secondWritePaths: [], and generated bytes remain identical.
• Cleanup reports the daemon stopped, package store removed, and isolated workspace removed; the repository root graph contains no @acme/ projects.
• The proof contains no private generation imports, private proof aliases/wiring, or fabricated workspace/test helpers.
• The delivery stays within 400 changed lines (additions + deletions).
• Rollback is limited to this installed success-path proof and restores the Unit 5 parent state.

Chain context

• Base/current parent: PR feat(app-builder): preserve Todo v1 parity #143, branch feat/app-builder-v1-parity-migration.
• Next child: Unit 6B, negative verification and interruption lifecycle proof.
• PR feat(app-builder): regenerate canonical Todo showcase #130 remains frozen.

Non-goals

• Negative verification or interruption lifecycle proof, owned by Unit 6B.
• POSIX process-tree hardening.
• Unit 7 eligibility work.
• Any mutation, regeneration, retargeting, or other change to PR feat(app-builder): regenerate canonical Todo showcase #130.

Part of #131.

[kattsushi]

Closing as not planned because Effectify App Builder has been retired in favor of contributing to lloydrichards/stack-effect. No App Builder implementation is retained on dev.