focus-flow/Codex Documentation/Current Software Plan/Task Pushing 01 - Past Task Push Controls/TASK_PUSHING_01_EXECUTION_ORDER.md

2.1 KiB

Task Pushing 01 Execution Order

Status: Planned.

Run these files in order. All chunks are intended for XHIGH execution unless a chunk explicitly says otherwise.

  1. TASK_PUSHING_01_BLOCK_01_SCOPE_AND_DOMAIN_SEMANTICS.md

    • Confirm Date Selection 01 and persistence prerequisites.
    • Verify flexible-task-only scope or explicitly expand backend support.
    • Lock current-time and destination semantics.
  2. TASK_PUSHING_01_BLOCK_02_PAST_TASK_READ_MODEL.md

    • Add past/incomplete push state to read/presentation models.
    • Keep detection out of leaf widgets.
    • Add mapper tests for today, previous day, future day, completed, and unsupported task types.
  3. TASK_PUSHING_01_BLOCK_03_PUSH_BUTTON_CARD_UI.md

    • Add the full right-side Push button.
    • Place it beside reward/difficulty icons with higher z priority than time text.
    • Suppress hover quick actions while visible.
  4. TASK_PUSHING_01_BLOCK_04_PUSH_MENU_DESTINATIONS.md

    • Add the destination menu.
    • Wire menu selection to controller callbacks.
    • Preserve keyboard and click-away behavior.
  5. TASK_PUSHING_01_BLOCK_05_COMMAND_WIRING_AND_PERSISTENCE.md

    • Add Flutter command-controller push methods.
    • Call application use cases through the selected-date/runtime context.
    • Validate close/reopen persistence after each destination.
  6. TASK_PUSHING_01_BLOCK_06_DESTINATION_SCHEDULING_RULES.md

    • Verify or adjust core command behavior for next/tomorrow placement.
    • Ensure no-overlap and no-before-now behavior.
    • Add backend tests before relying on UI tests.
  7. TASK_PUSHING_01_BLOCK_07_BACKLOG_FRESHNESS_RESET.md

    • Add or verify a separate backlog freshness anchor.
    • Reset it when pushing to Backlog.
    • Preserve original task creation time for history/reporting.
  8. TASK_PUSHING_01_BLOCK_08_VALIDATION_HANDOFF.md

    • Add end-to-end widget/controller/lifecycle tests.
    • Run validation gates.
    • Update minimal status docs.

Do not implement broad task editing, drag/drop, Shield, or week/month planning in this plan.