focus-flow/archive/Archived plans/V1_BLOCK_01_Project_Foundation.md

3.8 KiB

V1 Block 01 — Project Foundation

Status: Completed

Purpose: Establish a clean Dart package foundation, repository conventions, and starter test loop. This block should leave the repository easy for Codex to modify safely.

Chunk 1.1 — Verify project scaffold

Recommended Codex level: low

Status: Completed with environment blocker noted

Tasks:

  • Inspect pubspec.yaml, analysis_options.yaml, README.md, and .gitignore.
  • Confirm the repo is a pure Dart package, not a Flutter app yet.
  • Confirm lib/scheduler_core.dart exports only stable public entry points.
  • Confirm lib/src/ contains implementation files.
  • Confirm test/ contains at least one starter test.

Acceptance criteria:

  • dart pub get succeeds, or any dependency issue is documented.
  • dart analyze succeeds, or initial scaffold issues are fixed.
  • dart test succeeds, or the failure is fixed.

Execution notes:

  • Verified pubspec.yaml, analysis_options.yaml, README.md, and .gitignore.
  • Confirmed the repository is currently structured as a pure Dart package, not a Flutter app.
  • Confirmed lib/scheduler_core.dart exports the starter public entry points from lib/src/.
  • Confirmed lib/src/ contains implementation files and test/ contains a starter scheduling engine test.
  • Could not run dart pub get, dart analyze, or dart test because neither dart nor flutter is installed on PATH in this environment.
  • Commit was deferred until the repository was initialized and repaired.

Commit suggestion:

chore(project): verify starter dart scaffold

Chunk 1.2 — Stabilize public API boundaries

Recommended Codex level: medium

Status: Completed with environment blocker noted

Tasks:

  • Keep public exports in lib/scheduler_core.dart minimal.
  • Ensure internal helpers remain under lib/src/.
  • Add comments that identify which APIs are starter placeholders.
  • Do not add Flutter UI code in this block.

Acceptance criteria:

  • Public API is small and understandable.
  • Internal implementation is not accidentally exported beyond current needs.
  • Analyzer and tests pass.

Execution notes:

  • Kept lib/scheduler_core.dart exports limited to the existing starter model, scheduling engine, and statistics surfaces.
  • Confirmed implementation remains under lib/src/.
  • Added public documentation comments that identify the starter placeholder APIs without changing scheduling behavior.
  • Did not add Flutter UI code.
  • Could not run dart analyze or dart test because neither dart nor flutter is installed on PATH in this environment.
  • Commit was deferred until the repository was initialized and repaired.

BREAKPOINT: Stop here if the next requested chunk changes Codex level.

Chunk 1.3 — Document local development commands

Recommended Codex level: low

Status: Completed with environment blocker noted

Tasks:

  • Update README.md with setup, analyze, test, and project layout notes if missing.
  • Do not duplicate the full product spec in README.
  • Keep human/product detail in Human Documentation/.
  • Keep execution detail in Codex Documentation/.

Acceptance criteria:

  • README tells a new contributor how to run checks.
  • README points Codex/humans to the correct documentation folders.

Execution notes:

  • Updated README.md with the Dart SDK prerequisite, local setup/check commands, and when to run them.
  • Added documentation boundary notes for Human Documentation/, Codex Documentation/Current Software Plan/, and Codex Documentation/Archived plans/.
  • Did not duplicate the full product spec in README.md.
  • Could not run dart analyze or dart test because neither dart nor flutter is installed on PATH in this environment.
  • Commit was deferred until the repository was initialized and repaired.

Commit suggestion:

docs(project): document starter development workflow