Expose anchors on scheduler page (codex)

[numnx]

🧩 Task: Expose anchors on scheduler page

Automated task PR opened by Code UX for T02.

📋 Summary

Sprint: Sprint 145 · Micro Improvements · Task: T02

Deliver SPR-145 micro improvements: Jira import In Work transitions, relative sprint scheduling from scheduler/composer/quicksprints, onboarding menu ordering, task-card quick actions, and sticky settings context controls.

📝 Full Task Prompt

## Objective
Update the Scheduler page form so operators can choose either an absolute date/time or “after another sprint ends” for sprint and quicksprint schedule entries.

## Scope
- `dashboard/src/v2/SchedulerPage.tsx`
- `dashboard/src/v2/lib/scheduler-api.ts`
- `dashboard/src/v2/types.ts` if scheduler type re-exports need adjustment
- Add or update scheduler dashboard tests under `tests/dashboard/v2/` or `dashboard/src/v2/**/__tests__/`
- `docs/dashboard/scheduler.md`

## Implementation Requirements
1. Consume the scheduler anchor contract from T01 and add a schedule timing control with two modes: absolute date/time and after sprint end.
2. For after-sprint-end mode, render a sprint selector populated from project sprints and an optional offset-minutes numeric input; disable or explain invalid choices such as completed-only targets if the backend rejects them.
3. Serialize create and edit payloads with the correct anchor fields, preserving the existing `scheduledFor`, timezone, target-specific payloads, and recurrence behavior for absolute schedules.
4. Hydrate edit mode for anchored entries so the form restores the timing mode, source sprint, offset, target type, and target-specific fields.
5. Update visible summaries/cards so anchored entries read as relative schedules instead of misleading fixed times, while preserving accessible status text and cached refresh behavior.
6. Add focused tests for creating and editing an anchored sprint or quicksprint entry from the scheduler page.
7. Update scheduler docs to describe the dashboard controls.

## Constraints
- Depends on T01’s scheduler contract; do not invent a second dashboard-only payload shape.
- Do not alter chat or memory-remediation scheduling UX beyond keeping it compatible with the shared form.
- Keep keyboard navigation and aria status behavior for the existing Calendar / 24 Hours tabs intact.
- Keep absolute scheduling and recurrence UI behavior unchanged.

## Verification
- Run the focused scheduler dashboard test file added or updated for this task.
- Run `pnpm run test:dashboard` if the focused test command is not obvious.
- Run `pnpm run lint`.
- Success means users can create/edit after-sprint-end sprint and quicksprint entries from `/scheduler`, and absolute scheduler flows still work.

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-06 22:06:12 UTC
Finished	2026-07-06 22:12:38 UTC
Duration	6m 26s

📊 Token Usage

Metric	Value
Input tokens	99,828
Cached input tokens	2,439,936
Output tokens	13,509
Total tokens	2,553,273
Invocations	1
Tool calls	54
Active time	5m 54s

Included usage estimate (subscription/local login): $2.12

🌿 Branch Info

Base: feature/CODUX-145-micro-improvements
Head: task/feature-codux-145-micro-improvements-t02-codex-mr9rrs25

---

🤖 Generated by Code UX