githubnext/ace2Public

Ace: a collaborative coding environment on the team's own machines

Verify native development and recovery end to end in Ace

IA

iamnbutler opened ·

Ace already has native coding tools, lanes, shell/Git/gh access, diffs, durable recovery, and release commands. Qualify the complete development loop so dogfooding MVP is based on working behavior rather than a feature checklist.

## Acceptance

- Complete a representative Ace change from issue and lane through edits, required real checks, Ace Diff review, PR/CI, and signed canary delivery using Ace's surfaces and native harness. - Verify the UI change with channel-owned browser and native tools; preserve the evidence. Follow up on any failing CI or review feedback inside Ace. - Continue existing work through compaction, worker/helper restart, and a development failure without lost history, unintended side-effect replay, or duplicate lane writers. - Keep a working installed Ace separate from the source build under development. Validate any stored-format change against an existing-channel backup; never reset the store. - Record the channel/lane, revision, build/model, outcomes, and any remaining external-tool escape. File observed defects as issues.

This validates existing mechanisms; it does not request another release platform. Shell `git`, `gh`, builds, and existing release commands inside Ace count. Human OS/login handoffs are legitimate. #39 owns published-upgrade qualification on another Mac; external-harness continuation (#9), host migration (#49), and mobile are separate promises.

Dogfooding MVP: #5. Depends on the required native/browser verification paths. [Review evidence](https://github.com/githubnext/ace2/issues/5#issuecomment-5986485157).

  1. iamnbutlerparent-issue-addedlast month on GitHub

  2. iamnbutlerreferenced this in [Meta] Dogfood Ace end to end #5last month on GitHub

  3. iamnbutlerreferenced this in Finish development-run isolation: helper conflict diagnostics, loopback test hosts, and reload #97last month on GitHub

  4. iamnbutlerreferenced this in feat(app): add reasoning effort to the composer #148last month on GitHub

  5. IA
    iamnbutler
    Author

    Development-loop observation from #148: a React crash left Ace-dev blank. Cmd+R delivered but did not reload (the app has no native reload action); background Cmd+Q was refused as unverifiable by desktop_key. Stopping the exact source dev runner via its SIGTERM lifecycle and restarting it recovered the app, without touching Canary or other dev instances.

  6. iamnbutlerreferenced this in Expose native patch drift and cache recovery in desktop dev builds #173last month on GitHub

  7. iamnbutlerreferenced this in [Meta] Complete native computer use in Ace #8last month on GitHub