Project #3: one status per piece of work #122

Owner: Irzhy (@irzhywau). Part of #93.

Goal: Project #3 shows the work as issues, each with one status, so everyone takes the next issue in order.

Done on 2 October: 83 PR cards removed from the board, the 17 missing open issues added, and statuses corrected (#44-#47 and #98 back to Backlog; issues whose PR is ready are in QA / Review). PRs on retired bases were triaged; #63 and #64 are closed.
Done on 7 October: the last 7 PR cards removed (#123, #148, #203-#206, #266) and the missing open issues #260, #264 (Backlog) and #265 (In progress, per Sasha's 6 Oct comment) added.

Done means

• The project lists issues only (0 PR cards on 7 October). Each PR says "Part of #N" and shows inside its issue.
• The project's auto-add workflow adds issues only (filter is:issue is:open, set by Anders on 6 October), so PR cards do not come back. Proof: the 10 PRs opened since (release: publish only a source with complete green develop CI; one acceptance record (#89) #267-alpha.8: change notes say what alpha.8 ships (#89) #278) are not on the board; new issues update: elastos update deletes installed Home/System on a source-installed Home when its capsules map changes #270 and update: every capsule signed independently; updates replace only changed capsules #274 were added automatically.
• Docs that still name state.md or TASKS.md as the place for current work point to issues instead. Proof: a repository search finds no such instruction. Left on develop: the "Development status" link in website/elastos/index.html and the evidence links in website/elastos/claims.json point to an old state.md. Dated records in docs/audits/ and the changelog stay as they are.
• Statuses: Backlog = planned; In progress = someone works on it (at most one per person or lane); QA / Review = its PR is ready and the reviewer is requested; Done = Done means proven and closed; Abandoned = closed without landing. The 7 October closed-issue census remains historical. Browser reconciliation on 8 October: Gateway SIGTERM leaves orphan browser-vm-control-service #131 is QA / Review in the Installed product lane; LA-03: Install the Jetson engine through Runtime #97 is Backlog; Installer: clear steps, ElastOS banner and plain output for pipes #252 is assigned to Sasha. Browser mission: complete stable local and remote browsing with human and agent parity #283 and new Browser: prepare the selected local Engine during normal installation and repair #288–Browser: qualify the frozen candidate and maintain the supported role matrix #293 task cards are Backlog, each with one issue item, owner and preserved release scope. G1 Install and update: Signed update #89 remains its existing aggregate status; OMP and other lane owners retain their work. Windows: prove the installed Runtime journey under WSL2 #265's owner/view cleanup remains for its owner.
• Views: 0.7.2, 0.7.3, 0.8.0 and My items, each sorted by issue number. The other views (Backlog, Priority board, Team items, Roadmap, Focus) are removed. Anders: in the Project UI (the API cannot create or delete views).
• PRs on retired bases are settled, each with a note on where the work landed. Settled: feat(protected-content): atomic cutover to the Runtime-owned authority (ELACITY-2299) #59, feat(protected-content): installed inactive e2e proof — three custody replicas + repair after loss (ELACITY-2298) #60, feat(protected-content): 0.7.1 UI/UX, cleanup and crypto-review follow-up #62 and feat(protected-content): buy from any live offer, found by link or in Explore #70 closed on 2 October, replaced by the stack feat(protected-content): one authority, the Runtime, and no 10% disk floor (ELACITY-2299) #203 → feat(protected-content): from Creator to a readable object #204 → feat(protected-content): a mint that completes and an open that works #205 → feat(protected-content): buy from any live offer #206 on develop; Build and check the Jetson ARM64 CPU engine #73 closed, replaced by Use a pinned ARM engine recipe in normal CI #200; Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 is on develop. Left: Irzhy: close Fix/0.7.1 security #76 (in main through Release v0.7.1 (monthly developer release) #140) and decide dKMS/dDRM foundation on the ESP substrate (inspired from flint-5.0) #15 and feat(logger): port elastos-logger crate from PR #15 #25. Sasha: close feat(model-provider): offers/runs contract, openai_compat + h3_video adapters (stacked on collaboration-candidate) #17 (replaced by the model offers/runs contract in develop) and decide feat(content): gba-nonogram content capsule on 0.7-dev #26.
• Review requests are only on PRs that are ready. On 7 October no draft PR has a review request (fix(model): save hosted End before stopping admitted sends #148's was removed); requests are on Chat and People with Home: connect, approve contacts and recover (#86) #123, feat(protected-content): one authority, the Runtime, and no 10% disk floor (ELACITY-2299) #203-feat(protected-content): buy from any live offer #206, Chat and People spam limits: Discovery relay caps and Community rate limits (#139) #262 and feat(setup): one progress line per component with signed sizes #277.

Browser hierarchy and status proof — 2026-10-08

Native hierarchy: #283 → #87 → #131/#288, and #283 → #289/#290/#291/#292/#293. Project #3 contains one issue item per new task, all assigned to andersalm, with #288 in 0.8.0 and #289–#293 in After 0.8.0. #131 is the one active installed Browser task. Accepted producer milestones unblock integration; full issue acceptance stays open. This bounded update leaves the broader view/ref/board cleanup gates above with their owners.

Local AI plan reconciliation — 2026-10-08

Local AI reconciliation retains one project issue card per existing task under #84 (#94–#105), with #94–#96 Done, #97–#105 Backlog and #150 In progress. #85 is corrected from QA / Review to Backlog: its parked #148 is draft/conflicting with no reviewer request. Its exact historical proof and remaining acceptance stay in the issue. Native core/update milestone dependencies are preserved; no new issue or PR card is needed. Conditional estimates live in #84 while start/target dates remain unset.