> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase38-session04-dream-scheduling-and-setup/tasks.md).

# Task Checklist

**Session ID**: `phase38-session04-dream-scheduling-and-setup` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-06-29

***

Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID.

***

## Setup (3 tasks)

* [x] T001 \[S3804] Verify upstream 1.3/1.4 scheduler and setup hunk behavior against current AI OS runner ownership (`scripts/install-dream-cron.ts`)
* [x] T002 \[S3804] Characterize current macOS launchd, Linux fallback, setup install copy, and Dream scheduler status copy before edits (`scripts/setup.ts`, `scripts/lib/scheduler/operator-status.ts`)
* [x] T003 \[S3804] Create the implementation evidence file and record selected AI OS runner command sequence (`.spec_system/specs/phase38-session04-dream-scheduling-and-setup/implementation-notes.md`)

***

## Progress Summary

| Metric              | Value   |
| ------------------- | ------- |
| Tasks Completed     | 20 / 20 |
| Estimated Remaining | 0 hours |
| Blockers            | 0       |

***

## Foundation (5 tasks)

* [x] T004 \[S3804] Create a testable Dream install helper for platform flags, safe quoting, wrapper rendering, scheduled-task argv, and recovery copy (`scripts/lib/scheduler/dream-install.ts`)
* [x] T005 \[S3804] \[P] Add readiness-warning logic that recognizes Claude setup-token evidence and configured provider readiness without exposing credentials (`scripts/lib/scheduler/dream-install.ts`)
* [x] T006 \[S3804] \[P] Add Dream install unit tests for Windows paths, quoted commands, macOS plist command, Linux fallback copy, and readiness states (`scripts/lib/__tests__/dream-install.test.ts`)
* [x] T007 \[S3804] \[P] Preserve shared platform helper expectations for executable names and Windows candidate directories used by scheduled tasks (`scripts/lib/__tests__/platform.test.ts`)
* [x] T008 \[S3804] Wire `install-dream-cron.ts` to the Dream install helper while preserving strict argument parsing and exit codes (`scripts/install-dream-cron.ts`)

***

## Implementation (7 tasks)

* [x] T009 \[S3804] Implement Windows `.cmd` wrapper generation and Task Scheduler install/replace behavior with idempotent reinstall and explicit error mapping (`scripts/install-dream-cron.ts`)
* [x] T010 \[S3804] Implement Windows query, run, and uninstall actions with platform-correct success/failure messaging and duplicate-trigger prevention while commands are in-flight (`scripts/install-dream-cron.ts`)
* [x] T011 \[S3804] Update macOS plist command construction to run aggregate first and then AI OS Dream runner paths while preserving launchctl load/unload behavior (`scripts/install-dream-cron.ts`)
* [x] T012 \[S3804] Correct Linux fallback guidance to use AI OS aggregate/Dream ordering and remove stale manual-Windows copy (`scripts/install-dream-cron.ts`)
* [x] T013 \[S3804] Update setup auto-install behavior and setup copy for macOS launchd, Windows Task Scheduler, and Linux manual cron guidance (`scripts/setup.ts`)
* [x] T014 \[S3804] Add readiness-based headless-auth setup guidance with explicit missing-auth, ready-provider, and setup-token cases (`scripts/setup.ts`)
* [x] T015 \[S3804] Align Dream scheduler operator status and script documentation with Windows install support and AI OS runner commands (`scripts/lib/scheduler/operator-status.ts`, `scripts/README_scripts.md`)

***

## Testing (5 tasks)

* [x] T016 \[S3804] \[P] Assert Dream install helper coverage for Windows install/query/run/uninstall argv, wrapper content, missing-tool failures, and safe path quoting (`scripts/lib/__tests__/dream-install.test.ts`)
* [x] T017 \[S3804] \[P] Assert scheduler setup copy remains command-only, browser-safe, and accurate for Dream install support (`scripts/lib/__tests__/scheduler-operator-status.test.ts`)
* [x] T018 \[S3804] Run targeted Dream install and scheduler status tests (`bun run test -- scripts/lib/__tests__/dream-install.test.ts scripts/lib/__tests__/scheduler-operator-status.test.ts`)
* [x] T019 \[S3804] Run scheduler/Dream regressions and script typecheck (`bun run test -- scripts/lib/__tests__/scheduler-runner.test.ts scripts/lib/__tests__/dream-execution.test.ts`, `bun run typecheck:scripts`)
* [x] T020 \[S3804] Validate ASCII/LF requirements and record Windows harness, macOS, Linux, and setup-readiness verification evidence (`.spec_system/specs/phase38-session04-dream-scheduling-and-setup/implementation-notes.md`)

***

## Completion Checklist

* [x] All tasks marked `[x]`
* [x] All tests and checks passing
* [x] All files ASCII-encoded with LF line endings
* [x] `implementation-notes.md` updated
* [x] Ready for `creview` to start the creview -> validate sequence

***

## Next Steps

Run the `creview` workflow step.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase38-session04-dream-scheduling-and-setup/tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.