Upgrade Jared task-manager visibility orchestration and operator UX

Cancelled (2026-03-25). This umbrella task is obsolete. The operator UX direction it was exploring has already been resolved by the completed tasks server rollout and follow-on simplification work, especially Add tasks serve CLI and local server with heartbeat or task-manager status UI, Add just tasks serve composing heartbeat loop and plans server, Make tasks server the primary master plans doc surface deprecating MkDocs, Rename master_plans directory to tasks and align CLI paths, and Harden worker continuity and remove tmux manager surface.

Problem

This was filed while the orchestration layer was still being framed as Jared and while several operator UX questions were genuinely open: heartbeat vs manager, live status vs MkDocs, and whether a continuous Claude/tmux surface should remain part of the default workflow.

Those questions have since been answered in implementation:

• Live operator visibility moved to tasks serve.
• The docs flow moved toward tasks server first, not MkDocs-first.
• The repo standardized on tasks naming.
• The tmux/Jared operator surface was later removed as a default path.

So this umbrella should be archived as cancelled / superseded, not left as a still-open exploration task.

Context

• The execution chain referenced here is no longer hypothetical; the core child tasks are completed.
• The remaining ambiguity about a standing manager/tmux flow was resolved later by harden-worker-continuity-and-remove-tmux-manager-surface, which explicitly removed the Jared/tmux path from the preferred operator model.
• That means this task no longer points to future work. It mostly records an exploration phase that has already been overtaken by concrete implementation and cleanup.

Possible Solutions

• A — Leave this open as a historical umbrella: rejected; it implies unresolved work when the real decisions are already shipped.
• B — Recommended: cancel it as obsolete and link to the completed implementation chain: keeps the history while making the backlog accurate.
• C — Re-scope it into a new active task: unnecessary unless a fresh operator-UX problem appears that is not already covered by a concrete task.

Plan

1. Mark the task cancelled.
2. Record that its exploratory scope was resolved by shipped tasks server, docs, rename, and tmux-removal work.
3. Point future readers at the concrete completed tasks instead of leaving this as an active umbrella.

Implementation Progress

• 2026-03-25: Cancelled as obsolete/superseded.
• add-tasks-serve-command-and-plans-server delivered the live status/browse surface this task was exploring.
• add-just-tasks-serve-compose delivered the one-command operator flow.
• migrate-master-plans-docs-primary-to-tasks-server made tasks server the primary local docs/operator surface.
• rename-master-plans-tree-to-tasks completed the naming/path consolidation.
• harden-worker-continuity-and-remove-tmux-manager-surface resolved the remaining “continuous manager vs heartbeat-first” question by removing the tmux/Jared path from the main operator workflow.

QA Exploration

• [x] QA exploration completed (or N/A for non-UI tasks)

N/A — cancelled infrastructure/task-metadata cleanup.

Review Feedback

• [ ] Review cleared