Verify native development and recovery end to end in Ace
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, shell, typescript
Research direction
Start from the review-evidence comment on issue #5 and the acceptance list here; the entry points are Ace's lanes, Diff view, shell/git/gh access, and the existing release/canary commands. Pick one representative change and drive it end to end, then exercise compaction, worker/helper restart, and a development failure against a separately installed Ace plus an existing-channel backup. Done means a recorded run (channel/lane, revision, build/model, outcomes, external-tool escapes) and any observed defects filed as issues.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
githubnext/ace2#487 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
Similar issues
-
area:plugins enhancement platform:vscode
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
anthropics/claude-code#103166 ·
Maintainers usually reply within 1 day
-
check:failed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 90/100
iptv-org/iptv#55744 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
jitsi/jitsi-meet#18021 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
spec: discovery input example can contain multiple aliases for one parameter, with no canonical oneOpen
Difficulty 1/5 Under an hour Newbie friendliness 95/100
x402-foundation/x402#3841 ·
Maintainers usually reply within 1 day