Make everything Micro creates discoverable from the conversation and Inbox

Current status — 18 September 2026

Saved and Scheduled discovery shipped in #1802/#1803; the opening progress paragraph above predates those changes. Keep the issue open for stable persisted output references and deterministic rendering, robust file/download exposure, rename/delete lifecycle and actual app-building validation. Merged UI work alone does not complete the creation contract.

Users cannot reliably find or manage what Micro creates across services. Events exposed the problem, but it also affects notes, documents, files and apps. Keep the sparse prompt-first UI and avoid a navigation item for every service.

Proposed product structure: Inbox remains the conversation record, with secondary Saved and Scheduled destinations. Saved is a private view over existing notes, documents, files and apps, not a second storage system. Scheduled shows the caller's reminders and agent instructions. Exclude internal memories and implementation files from user-facing creations unless explicitly requested. Existing service pages remain the destination for opening/managing an item.

Required creation contract:

• Every explicit creation returns stable identity, type, title, state and an actionable URL or download; use opaque IDs for private items.
• Persist the reference alongside the originating conversation and show it deterministically, without relying on the model to repeat a URL.
• Clearly distinguish saved output, queued/building work, ready output, failure and scheduled execution. An app is not finished until it is runnable and validated against the user's request.
• Show what a schedule will do, when and in which timezone, whether it repeats, how the outcome arrives, and how to edit/cancel it. Calendar copies are not the execution schedule.
• Browsing, opening, downloading and mutation must recheck ownership; links must not make an item public. Explicit sharing only.
• Account switches, restarts, failed builds, deleted items and old creations must be handled.
• Use the existing shared CSS/JS; compact mobile rows, readable titles, timestamps and separated actions.

First improvement is PR #1800: Micro sender names, explicit event action, event URLs and note/document save URLs. Apps already return build-status/run URLs. Still needed: files/download exposure, persisted creation references and renderer, Saved/Scheduled discovery, migration/backfill approach, and end-to-end app coding validation. Live browser verification is currently blocked; do not equate a successful build with verified UI or app-builder functionality.

Review PR #1800 and the existing service pages plus shared CSS/JS to map how creation results are currently exposed. Trace the remaining work for persisted references, Saved and Scheduled discovery, file/download handling, lifecycle changes, and app-building validation. Done means stable actionable references, correct ownership checks and states, deterministic rendering, and validated end-to-end app behavior.