Restore progressive existing-task status icons

[ericlitman]

What changed

• add one hidden, read-only onboard-stream pass that fully paginates existing tasks, reads only the newest turn, applies exact historical footer statuses first, and classifies remaining completed turns in fixed sequential Luna-medium batches
• request complete-catalog read permission once after the friendly install handoff; declining leaves every existing title unchanged and the copy never claims progress before approval
• disable every hosted classifier feature and request-input, keep shell/code-mode execution unavailable, and reject any tool-attempt/runtime event or extra assistant message
• stream strict ordered candidates to the published yielded install cell, which performs one mounted reread and at most one exact-target title write per semantic row
• render plain icons for exact evidence, quiet ✦ icons for conservative inference, and no icon or write for unknown
• make ordinary turns replace inferred prefixes with the plain current status, and make uninstall remove both plain and inferred prefixes
• update the install experience, product documentation, release smoke, contract tests, and changelog

Why

A prior rewrite removed existing-task onboarding after the earlier controller-based implementation repeatedly failed. The replacement deliberately keeps only the proven title boundary: one ephemeral read-only classifier process and the mounted Codex reader/setter as the sole writer. There is no controller task, worker fan-out, queue, retry, persisted onboarding state, repair sweep, fallback model, or alternate title path.

User impact

Installation reports success immediately and explains the one catalog-read permission request. If approved, existing sidebar tasks fill progressively over the next several minutes. A small ✦ identifies a first-read best guess and disappears after that task's next ordinary turn. Declining, unclear, inaccessible, unsafe, or drifted tasks remain unchanged.

Verification

• gofmt
• go test ./...
• go test -race ./...
• go vet ./...
• Darwin arm64 and amd64 builds
• shell syntax, experiment-registry validation, guide parity, and git diff --check
• exact-candidate isolated release smoke
• ten-minute yielded-cell survival canary across a completed outer response
• live Codex Desktop install, progressive sidebar replay, drift/no-retry case, interruption, natural rerun, next-turn sparkle removal, consented uninstall, reinstall, and post-restart persistence
• full clean-sidebar replay: 340 candidates, 295 confirmed mounted writes, 45 unknown untouched, zero drift, zero unconfirmed
• hardened live Luna classifier contract and 72-second exact-candidate helper stream with strict no-tool event validation
• review-agent and Fable completion verdicts: no findings / Ship

Closes BEAR-121

[openswebot]

Open SWE Review found 2 potential issues.

Open in Web

[ericlitman]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-17 23:22 UTC · Rule: default · triggered by @ericlitman with the @mergifyio queue command
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-08-17 23:23 UTC · at e2ae74082bf96d6646e1e2a89f5b09d57c8f1d05

This pull request spent 28 seconds in the queue, including 2 seconds running CI.

Required conditions to merge

• github-review-approved [🛡 GitHub repository ruleset rule Mergify automatic merge queue]
  • Restore progressive existing-task status icons #128
• all of [🛡 Merge Protections rule Queue ready pull requests]:
  • -draft
    • Restore progressive existing-task status icons #128
• any of [🛡 GitHub branch protection]:
  • check-success = verify
  • check-neutral = verify
  • check-skipped = verify
• any of [🛡 GitHub branch protection]:
  • check-success = Open SWE Review
  • check-neutral = Open SWE Review
  • check-skipped = Open SWE Review
• any of [🛡 GitHub repository ruleset rule Mergify automatic merge queue]:
  • check-success = @mergify/Mergify Merge Protections
  • check-neutral = @mergify/Mergify Merge Protections
  • check-skipped = @mergify/Mergify Merge Protections
• any of [🛡 GitHub repository ruleset rule Review gate]:
  • check-success = Open SWE Review
  • check-neutral = Open SWE Review
  • check-skipped = Open SWE Review