AutoForge/prompts/STATE.md

17 KiB

AutoForge orchestration state

Current handoff

Field Value
Updated 2026-10-28
Phase Corrected single-shell foundation accepted; vehicle profile slice next
Active step Step-02 - Vehicle profiles and control module model
Assignment Step-02.md, regenerated after Step-01A acceptance
Assignment status READY FOR WORKER / AWAITING MANUAL HANDOFF
Expected worker report prompts/Step-02-Report.md - not yet created
Last accepted step Step-01A - accepted 2026-10-28
Outstanding corrections None
Step-02 status READY FOR WORKER; old unexecuted assignment explicitly superseded
Worker execution Step-01A manually completed; Step-02 not invoked
Immediate next action User manually directs the worker to execute regenerated Step-02 only
Next orchestrator action After manual return, inspect the assignment, report, implementation, tests, Git changes, documentation and recorded command evidence

Repository baseline at initialization

  • Repository: D:\_Repos\Code\GAJ3T\AutoForge.
  • Branch observed: main, tracking origin/main.
  • Initial worktree: clean.
  • Initial tracked files: root README.md and .gitignore.
  • No existing solution, projects, tests, docs, src, or prompts were present.
  • No applicable AGENTS.md was found in the repository or its ancestor locations.
  • No .github instruction files were found. In particular, .github/copilot-instructions.md was absent and must remain absent.
  • Existing README describes the product vision, not verified implemented features; Step-01 requires preserving it while making implementation status explicit.
  • Existing .gitignore already includes common Visual Studio/.NET build patterns. Worker must extend only where necessary and preserve existing entries.
  • Initial orchestrator changes were limited to prompts/ROADMAP.md, this file, and prompts/Step-01.md. Step-01 subsequently added the implementation below.

Architecture decisions in force

See ROADMAP.md for the full planned architecture and milestones.

  1. The repository has only three top-level project directories: docs, src, prompts; existing protected infrastructure is preserved. Tests are under src/tests. No root tests, root artifacts, or nested AutoForge directory.
  2. Keep the existing single src/AutoForge.slnx, Core, Application, UnitTests and IntegrationTests. Accepted target-selection code/tests remain useful.
  3. Sole initial application executable: AutoForge.Client, .NET 10 MAUI Blazor Hybrid, initially Windows. No required standalone WebAssembly/web shell or separate backend. Ordinary desktop capabilities run in-process as a modular monolith; additional hosts/processes need a concrete approved requirement.
  4. Accepted Step-01A established Client -> UI -> Components. Client is thin native startup, BlazorWebView and DI/lifecycle/platform composition. UI owns complete routes, pages, navigation/layouts and feature presentation. Components owns generic reusable controls. UI cannot reference Client; Components cannot reference UI.
  5. Application is needed now and retained. Organize use cases into cohesive feature slices, beginning with existing execution-target selection. No mediator, generic repository/manager layer, prescribed boilerplate or empty future slices. UI invokes application contracts; business logic stays outside Razor components.
  6. Reusable domain, simulation, diagnostic, calibration, telemetry and AI capability libraries remain independently testable and are added only when justified. They do not depend on Client/UI or their coordinating application slices. Hardware, inference, storage and UI implementations never own domain truth.
  7. Simulation, replay, and physical hardware targets are explicit and cannot silently substitute for one another. Selection is not connection or execution.
  8. Synthetic data is labeled; simulation is deterministic and independent of AI, and verification uses an isolated oracle unavailable to ordinary UI/AI paths.
  9. AI plans are validated runbooks; no arbitrary hardware commands or offsets. Local inference is replaceable; core operation does not require AI/cloud.
  10. Initial hardware integration is read-only. Simulated approval, physical capability discovery, and driver availability cannot authorize physical writes. Bench and vehicle programming require separate future authorization/evidence.
  11. All handoffs are manual. Orchestrator never invokes the worker, implements application changes, or executes application builds/tests.
  12. The worker does not change the roadmap, state, or assignment; it may write only the current assignment's report under prompts. No automatic commits/pushes.

Historical Step-01 acceptance review

Decision at that review: ACCEPTED, 2026-10-28, with no identified blocking defect under the then-current architecture. This acceptance and its evidence remain historical facts. The later owner decision now requires Step-01A before progression; it does not erase the accepted implementation or its reports.

Reviewed Step-01, the worker report, all seven production source files, all three test source files, four project files, solution, five root configuration files, README/ignore diffs and all four technical documents. The source enforces explicit identity/kind selection, case-insensitive uniqueness, no cross-target fallback, immutable descriptors and registration snapshots. Integration tests exercise the real DI/Core/Application path rather than mocks.

Criterion Decision Evidence
AC-01 ACCEPTED Expected README/ignore changes only among pre-existing implementation files; empty index; original assignment/roadmap/state hashes matched the report before orchestration updates; protected instructions absent
AC-02 ACCEPTED Actual root project directories are docs/src/prompts; tests under src/tests; no root tests/artifacts or nested repository
AC-03 ACCEPTED Inspected solution and all project references: Core has none; Application -> Core; both test projects -> Core/Application; all net10.0
AC-04 ACCEPTED Inspected SDK policy, nullable/build/editor settings, central package pins and assets; worker records installed SDK 10.0.402 and actual VSTest execution
AC-05 ACCEPTED Descriptor/resolver/DI source satisfies explicit validation, uniqueness, snapshot and no-fallback requirements; no production provider is fabricated
AC-06 ACCEPTED All composition tests inspected; real container/service path covers positive selection and empty/invalid/mismatched/duplicate cases
AC-07 ACCEPTED ON WORKER EXECUTION EVIDENCE Reported final Release build: zero warnings/errors; unit 35/35, integration 19/19, zero failures/skips; source case counts and existing restore/Release outputs corroborate the report
AC-08 ACCEPTED Documentation index, architecture/error contract/Mermaid, ADR, build/test guide and README describe actual scope and planned features accurately
AC-09 ACCEPTED No operational hardware/AI/UI dependency or extra placeholder project; no automatic handoff introduced
AC-10 ACCEPTED Complete report contains exact command outcomes, corrected failures, acceptance mapping and required sections in one plain copy window; no later implementation present

Worker-reported execution: Windows x64, SDK 10.0.402, runtime 10.0.13; restore, Release build and both suites succeeded after the documented repository-local NuGet feed correction. Reported total: 54 passed, zero failed, zero skipped. Existing assets confirm the framework/dependency graph; Release binaries exist for all four projects. Their presence is corroboration, not an independent test execution.

The orchestrator executed only read-only inspection and document/Git checks, including static test-case counting and ignore-policy checks. It did not execute dotnet, application builds, tests, formatting or hardware operations. Runtime results are explicitly worker evidence. The worker's original report and assignment remain unchanged; implementation is not committed by this review.

Owner architectural realignment and current inspection

On 2026-10-28 the owner canceled the two-shell plan, required Client/UI/Components and application Vertical Slice Architecture, and directed correction before Step-02. Step-01A was the corrective assignment and is now accepted.

At correction planning, inspection found the original four-project solution unchanged: Core has no dependencies, Application references Core and DI abstractions, and both tests reference Core/Application. The existing target resolver and eager registration are suitable for a feature slice and must be preserved.

There was no host/component implementation to delete or migrate. Correction was additive UI composition plus feature organization, not a repository restart. The old Step-02 was held, not executed.

After acceptance, Step-02 was regenerated from the seven-project implementation and explicitly supersedes the prior unexecuted assignment. It now uses application feature slices, reusable Core models and a thin profile metadata consumer in the existing UI. No Step-02 implementation/report exists yet.

Step-01A acceptance review

Decision: ACCEPTED, 2026-10-28. No Step-01B assignment is required.

Reviewed the assignment, worker report, solution and all project references, Client native/bootstrap/host code, RCL routes, feature pages/view model/component/styles, moved Application feature, new rendered/ graph tests, package/build configuration, README and all affected technical docs.

Criterion Decision Evidence
AC-01 ACCEPTED Existing descriptor/resolver semantics and 54 prior cases retained; expanded suites contain 39 unit/26 integration cases; root layout/history/manual workflow preserved
AC-02 ACCEPTED Actual seven-project solution, one production executable, MAUI/Windows Client configuration and native Release output
AC-03 ACCEPTED MainPage hosts UI Routes through BlazorWebView; UI owns routes/layout/pages, Components owns StatusNotice; native route/assets observations reported
AC-04 ACCEPTED Project files, graph test and independent static traversal confirm Client -> UI -> Components, allowed Application references and no cycles
AC-05 ACCEPTED Feature folder contains real resolver/DI/errors with stable public namespace and unchanged explicit selection/snapshot/no-fallback behavior
AC-06 ACCEPTED Actual HtmlRenderer component/route tests use real Core/Application DI, cover errors/unknown routes and safe text rendering, without Client references
AC-07 ACCEPTED ON WORKER EXECUTION EVIDENCE Reported complete Release solution and direct Windows Client builds: zero warnings/errors; 39 unit plus 26 integration passed, zero failed/skipped; matching source counts and Release outputs inspected
AC-08 ACCEPTED ON WORKER NATIVE EVIDENCE Detailed reported native home/selection/unregistered-physical/not-found checks, hidden error banner and both RCL CSS assets loading; native executable exists, not rerun by orchestrator
AC-09 ACCEPTED README/index/architecture/build guide and ADR-0001/0002 reflect one shell, two RCLs, VSA/modular monolith and metadata-only limitations
AC-10 ACCEPTED Evidence-bearing report, corrected failures and environment deviation disclosed; historical reports/assignments preserved and Step-02 unexecuted

Worker-reported verified platform: SDK 10.0.402, runtime 10.0.13, Windows 10.0.26100.0/win-x64, MAUI Windows manifest 10.0.110 and WebView2 155.0.4283.62. The source counts, framework/assets, seven-project graph and native/portable Release artifacts corroborate the report. They do not prove an independent runtime run. No application builds/tests/native launch were performed here.

Acceptance covers the application correction, not approval of the unintended workload action or a claim that the broader tool environment is unchanged. The deviations below are non-blocking for this verified Windows foundation and must remain visible. No environment rollback or source fix was attempted.

Prerequisites, limitations, and known issues

  • Step-01A worker evidence establishes portable and native Windows compatibility for the accepted foundation. Recheck prerequisites if the environment changes.
  • No major SDK/workload/driver installation has been authorized. Report exact missing prerequisites and mark blocked checks honestly; do not replace .NET 10 MAUI Blazor Hybrid with a web host.
  • Reported workload incident: dotnet workload restore was mistakenly invoked during inspection, began manifest updates and was stopped. Worker reports workload version 10.0.403 and newer iOS/MacCatalyst manifests; Windows manifest stayed 10.0.110. No rollback occurred. Final Windows checks passed, but broader impact is unverified. Do not repeat workload-changing commands or repair/rollback without explicit authorization; this review does not authorize them.
  • Raw git diff --check failed on README CRLF, against a mixed-line-ending index. Read-only byte inspection found 151 CRLF lines and no trailing spaces/tabs. A command-local CR-at-EOL-aware check passed, with no Git configuration changed. Require LF normalization during Step-02's already-required README update.
  • README/ADR acceptance-pending text is historical to worker completion; Step-02 must align lifecycle statements while preserving original reports/decisions.
  • No blocking Step-02 prerequisite is currently identified.
  • Simulation, replay, diagnostics, profiles, telemetry, calibration, persistence, AI and hardware operations remain unimplemented; only foundation UI is present.
  • No application build or test has been executed by the orchestrator.

Review and progression gate

On manual return, evaluate every Step-02 acceptance criterion using the original assignment, worker report, actual code/tests, dependency graph, Git changes, README/docs, and recorded build/test evidence. Do not accept solely on a success claim; do not claim independent runtime verification.

  • Inspect domain/schema invariants, feature organization, profile UI/application tests, all regressions, native profile smoke evidence and documentation.
  • If accepted: record the decision, update roadmap/state, create Step-03 and stop for manual handoff. Do not execute it.
  • If deficient: create Step-02A.md with measurable corrections and matching report requirements, update state, and stop. Do not advance to Step-03.
  • If blocked: retain the active step, document the prerequisite and required worker evidence; do not advance or mark unexecuted checks as successful.
  • Never create the next major assignment while acceptance or corrections are open.

History

Date Event Evidence / result
2026-10-28 Initial repository inspection Clean main; only root README and ignore file tracked; no application or protected instruction files found
2026-10-28 Initial roadmap, state, and Step-01 prepared Amendment layout/naming adopted; READY FOR WORKER, no implementation accepted
2026-10-28 User returned Step-01 for review Original assignment, worker report, code/tests, configuration, Git changes and documentation inspected
2026-10-28 Step-01 ACCEPTED No blocking deficiency; worker evidence reports successful Release build and 54 passed, zero failed/skipped tests; no orchestrator runtime execution
2026-10-28 Step-02 prepared Profile/module model, versioned JSON, synthetic fixtures and application selection; manual worker handoff pending
2026-10-28 Owner architecture decision superseded the dual-shell plan One MAUI Client, UI/Components RCLs, vertical-slice modular monolith; Step-01 acceptance preserved but corrective 01A required
2026-10-28 Existing solution re-inspected Only four headless projects; no obsolete hosts to delete; no application changes/builds/tests executed
2026-10-28 Step-01A prepared; Step-02 placed on hold Correction is ready for manual worker execution; old Step-02 body retained, final regeneration deferred until correction acceptance
2026-10-28 Step-01A returned and ACCEPTED Seven-project single-shell/RCL/VSA implementation inspected; worker reports successful solution/native builds, 65 passing cases and native route/asset checks
2026-10-28 Deviations recorded Unintended workload manifest updates disclosed; no rollback; README CRLF-only diff hygiene noted for next documentation update
2026-10-28 Step-02 regenerated Explicitly supersedes unexecuted pre-correction version; actual seven-project baseline and profile feature/UI scope; READY FOR WORKER

Manual handoff instruction

Provide regenerated Step-02.md to the separate worker and request execution of that assignment only. The worker must produce prompts/Step-02-Report.md and stop. Return manually to the orchestrator for review. Reports, including final chat reports, must follow the single plain triple-backtick copy-window requirement.