diff --git a/docs/development/build_execution_tracker.md b/docs/development/build_execution_tracker.md index 4f54a8b..387cec8 100644 --- a/docs/development/build_execution_tracker.md +++ b/docs/development/build_execution_tracker.md @@ -2,9 +2,9 @@ ## Current status -- main baseline updated through: design-system-shared-widgets (Stage 4A complete) -- main baseline commit: merge of `feat/design-system-shared-widgets` (2026-05-22) -- next branch: feat/shared-composition-pattern +- main baseline updated through: flutter-cicd (Stage 4C complete) +- main baseline commit: merge of `feat/flutter-cicd` (2026-05-22) +- next branch: feat/test-coverage-visibility (Stage 4D) - current stage: Stage 4 — Platform foundations and cross-platform readiness ## Slice tracker @@ -111,3 +111,33 @@ - tests: passed (41/41 design_system, 294/294 feature_wordpress, 24/24 kell_web) - analyze: passed (dart analyze — no issues found in design_system and kell_web) - brief updated: yes + +### feat/shared-composition-pattern + +- status: merged to main +- date: 2026-05-22 +- inspection: complete +- implementation: complete +- files changed: + - `core/lib/src/app/` — extracted shared composition abstractions (KcAppConfig, KcAppEnvironment, KcAppServices, KcServiceFactory, KcBootstrap, KcAppScope) + - `core/lib/core.dart` — expanded barrel exports for app composition + - `core/test/core_test.dart` — added 20 tests for shared composition abstractions + - `kell_web/` — updated to use core composition abstractions +- tests: passed (20/20 core, 41/41 design_system, 294/294 feature_wordpress, 24/24 kell_web) +- analyze: passed +- brief updated: yes + +### feat/flutter-cicd + +- status: merged to main +- date: 2026-05-22 +- inspection: complete +- implementation: complete +- files changed: + - `.forgejo/workflows/flutter-analyze.yml` — new Forgejo Actions workflow for dart analyze on all 8 packages/apps + - `.forgejo/workflows/flutter-test.yml` — new Forgejo Actions workflow for flutter test per package with aggregate pass/fail summary + - `kell_creations_apps/tools/run_all_tests.sh` — new local CI helper script with optional --analyze flag + - `kell_creations_apps/tools/README.md` — documents scripts and CI workflow inventory +- tests: passed (20/20 core, 41/41 design_system, 294/294 feature_wordpress, 24/24 kell_web — 379 total) +- analyze: passed (dart analyze — no issues found across all 8 packages/apps) +- brief updated: yes diff --git a/docs/development/master_development_brief.md b/docs/development/master_development_brief.md index 5577ae9..339abd6 100644 --- a/docs/development/master_development_brief.md +++ b/docs/development/master_development_brief.md @@ -61,7 +61,7 @@ Rules: - `feature_finance` — financial analysis feature (stub only) - `feature_mrp` — craft manufacturing/MRP feature (stub only) - `feature_social` — social media management feature (stub only) -- `tools/` directory exists but is empty. +- `tools/` directory contains CI helper scripts (`run_all_tests.sh`, `README.md`). - App shell, routing, dashboard, reusable shell widgets, `AppServices`, and `AppScope` are implemented. - Dashboard uses app-composed repository data. - Vertical slices exist for Inventory, Products/Publishing, Orders, and Policy/Governance. @@ -94,6 +94,7 @@ Rules: - ✅ List efficiency improvements landed (Stage 3B complete — merged `feat/list-efficiency-improvements` → `main`, 2026-05-22). Stage 3 complete. - ✅ Design system expansion and shared widget migration landed (Stage 4A complete — merged `feat/design-system-shared-widgets` → `main`, 2026-05-22). - ✅ Cross-platform shell composition strategy landed (Stage 4B complete — merged `feat/shared-composition-pattern` → `main`, 2026-05-22). +- ✅ Flutter CI/CD pipeline landed (Stage 4C complete — merged `feat/flutter-cicd` → `main`, 2026-05-22). ### Current narrow edit capabilities on `main` @@ -114,12 +115,12 @@ Rules: - latest reported count for `design_system`: `41/41 passed` - latest reported count for `feature_wordpress`: `294/294 passed` - latest reported count for `kell_web`: `24/24 passed` -- baseline commit: merge of `feat/shared-composition-pattern` (2026-05-22) +- baseline commit: merge of `feat/flutter-cicd` (2026-05-22) ### Next recommended branch -**`feat/flutter-cicd`** — Stage 4C: Flutter CI/CD pipeline. -Branch from latest `main`. Stage 4B (cross-platform shell composition) is complete. +**`feat/test-coverage-visibility`** — Stage 4D: Test coverage visibility. +Branch from latest `main`. Stage 4C (Flutter CI/CD pipeline) is complete. --- @@ -254,26 +255,10 @@ Extract or document a shared app composition pattern so `kell_mobile` can mirror - `kell_web` still works identically - analyze clean, existing tests passing -#### Stage 4C — Flutter CI/CD pipeline +#### ~~Stage 4C — Flutter CI/CD pipeline~~ ✅ COMPLETE -##### Goal - -Establish automated validation for Flutter applications in Forgejo Actions. - -##### Requirements - -- add Forgejo Actions workflow for `dart analyze` on PRs -- add Forgejo Actions workflow for `flutter test` execution on PRs (per package) -- add basic test result reporting (pass/fail count per package) -- ensure workflows work for both web and Android targets -- populate `tools/` directory with any CI helper scripts if needed - -##### Definition of done - -- PRs trigger automated analyze and test runs -- test counts are reported in workflow output -- workflow files committed under `.forgejo/workflows/` -- `tools/` directory populated or removed if not needed +> Merged `feat/flutter-cicd` → `main` (2026-05-22). +> Added Forgejo Actions workflows: `flutter-analyze.yml` (runs `dart analyze --fatal-infos` on all 8 packages/apps) and `flutter-test.yml` (runs `flutter test` per package with per-package pass/fail count and aggregate summary table). Workflows trigger on PRs to main and all non-main branch pushes using `ghcr.io/cirruslabs/flutter:stable` container. Populated `tools/` directory with `run_all_tests.sh` (local test runner with optional `--analyze` flag) and `README.md` documenting scripts and CI workflow inventory. All existing tests passing (20 core, 41 design_system, 294 feature_wordpress, 24 kell_web — 379 total). Analyze clean. #### Stage 4D — Test coverage visibility @@ -514,11 +499,9 @@ No monitoring, error tracking, or analytics strategy exists for the Flutter appl **Recommendation:** Add lightweight error reporting and observability as a future stage, particularly important before any production WP-mode deployment beyond a single operator. -### 9. Empty tools directory +### 9. ~~Empty tools directory~~ ✅ RESOLVED -The `tools/` directory under `kell_creations_apps` exists but contains nothing. - -**Recommendation:** Either populate with development tooling (code generation scripts, analysis helpers, CI scripts) or remove to avoid confusion. If CI/CD scripts are planned, this is a natural home. +> Now populated with `run_all_tests.sh` and `README.md` as part of Stage 4C (Flutter CI/CD pipeline). ### 10. Missing feature parity documentation