AI-first redesign

Choice: Canon Cloud is redrawn so agents do the work and people approve it. Home is what waits for approval and what agents did. Cloud is web only. Community stays for now, and each new screen says if it is Cloud only. Old tasks, ideas and the old plan are closed, and agent-pipeline's split, safety rules and stop check stand.

• Designs first: new pages are added to .context/designs/web for review, with no route. The running app and its pages stay as they are. Nothing is deleted until the owner approves the designs.
• Order: the public site first (owner, 2026-11-02), then approvals home and gate, cited answers, Workspace, Product, Team and Space, then run detail, cost and cap.
• Gates: schema and code each need the owner's approval. Run, cost and cap screens can be drawn now, and are approved only after one real local run.
• Replaces: "no paid-site work until T040 and T043" and T048's needs:, for designs only. T040 and T043 stay open.
• Records: closed work keeps its file with a closing status, as product-model requires. Features stay as they are until the app changes, because they describe what runs. Why: the owner, 2026-11-02: "agreed, we need to discard old tasks, ideas, etc and start fresh". Canon's web app makes no model calls and has no MCP, and its screens are for people reading. There are no customers, so a large change costs little now. Rejected: a desktop app (hosted runs and browser approvals need none; canon-cli covers the local machine) · a new design set or shell · redrawing routed pages in place (it would break the tie to the running app) · a canvas and built-in marketing stages (see agent-pipeline) · deleting closed records. Revisit: a desktop app, when a paying company cannot let code or logins reach a hosted service and a dedicated instance and a local runner do not solve it, or when reviewers miss approvals and notifications do not fix that. Community, once the Cloud screens are approved. Outside demand is not proven; the 2027-01-31 stop check tests it.