268 lines
16 KiB
Markdown
268 lines
16 KiB
Markdown
```
|
|
# Step-02 Worker Report
|
|
|
|
## Status
|
|
|
|
**COMPLETE** — implementation, complete Release build, all regression tests and
|
|
native Windows profile-feature smoke checks are complete. Manual orchestrator
|
|
acceptance remains pending. Step-03 was not started.
|
|
|
|
## Implemented functionality
|
|
|
|
- Added immutable Core vehicle/profile identity, revisions, vehicle facts, arbitrary
|
|
module instances, extensible capability declarations, status assessments,
|
|
evidence classification and applicability.
|
|
- Added Application schema-v1 JSON import/export, strict validation, atomic
|
|
registration, in-memory profile catalog, exact revision listing/selection and
|
|
export through a real DI service.
|
|
- Added the UI RCL route /vehicle-profiles. It imports explicit JSON, lists
|
|
revisions without auto-selection, requires an explicit selection, renders
|
|
identity/capability/provenance/unknown information and supplies read-only JSON
|
|
export.
|
|
- Added source-controlled synthetic truck baseline/variant and alternate-vehicle
|
|
fixtures. They are clearly marked synthetic and are not real vehicle definitions.
|
|
- Preserved the existing target selection and single-shell project graph. Profile
|
|
import/selection does not register or alter execution-target providers.
|
|
- Implemented metadata only. There is no vehicle connection/discovery, simulation,
|
|
diagnostic transport, calibration data/editor, firmware image, operation
|
|
executor, physical authorization, database, AI, cloud service or persistence.
|
|
|
|
## Domain, schema, catalog and public contracts
|
|
|
|
Core source is under src/AutoForge.Core/Vehicles/VehicleProfile.cs.
|
|
ProfileIdentifier remains stable across positive integer revisions; each revision
|
|
is an immutable saved configuration. SchemaVersion 1 is separate from profile
|
|
revision. Exact catalog identity is (profileIdentifier, revision), compared using
|
|
OrdinalIgnoreCase. Revisions under one profile identifier cannot rebind to another
|
|
vehicle or conflict on already-known manufacturer/model/year/optional identity
|
|
facts. Multiple revisions can represent distinct metadata configurations of the
|
|
same vehicle. Unknown optional facts and identifiers are explicit null.
|
|
|
|
Vehicle/module roles and operation identifiers are open strings rather than a
|
|
closed module-role enum. Module instance identity is distinct from role/name.
|
|
Capability status supports Supported, Unsupported, Unknown, Inaccessible and
|
|
Restricted. Missing declarations return a distinct not-declared Unknown
|
|
assessment. No declared status means a service, connection, permission or
|
|
authorization exists.
|
|
|
|
Evidence classifications are Verified, Unverified, Inferred and Synthetic.
|
|
Evidence includes source/description, applicable vehicle and optional model year,
|
|
exact profile revision, module and hardware/software/firmware/calibration context,
|
|
explicit optional timestamps, verification information, limitations and nullable
|
|
confidence. Numeric confidence is finite and in [0,1]. Evidence references must
|
|
resolve within the profile revision and match applicable vehicle/module identity.
|
|
Classification is supplied data, not independent verification. Evidence never
|
|
authorizes an operation.
|
|
|
|
Application public contracts are IVehicleProfileService,
|
|
IVehicleProfileJsonCodec, VehicleProfileServiceCollectionExtensions,
|
|
VehicleProfileInterchangeException and VehicleProfileCatalogException. JSON v1
|
|
requires every defined property; unknown optional values use explicit null and
|
|
collections use []. Unknown properties and duplicate or case-ambiguous object
|
|
properties are rejected. Enum tokens are uppercase exact values. Malformed,
|
|
missing, unsupported-version, invalid-type/status, duplicate identity and
|
|
dangling/conflicting applicability inputs fail explicitly with a JSON path or
|
|
catalog failure. No repair, migration, network, generated timestamp or file write
|
|
occurs. Failed JSON validation happens before registration; duplicate entries do
|
|
not replace existing profiles.
|
|
|
|
The Client composes a process-lifetime in-memory catalog; application exit clears
|
|
it. UI selection lives in the scoped page view model and is never global execution
|
|
state. See docs/vehicle-profile-schema-v1.md and ADR-0003 for the complete
|
|
documented shape and policy.
|
|
|
|
## Files created and modified
|
|
|
|
Created:
|
|
|
|
- src/AutoForge.Core/Vehicles/VehicleProfile.cs
|
|
- src/AutoForge.Application/Features/Vehicles/Profiles/VehicleProfileErrors.cs
|
|
- src/AutoForge.Application/Features/Vehicles/Profiles/VehicleProfileJsonCodec.cs
|
|
- src/AutoForge.Application/Features/Vehicles/Profiles/VehicleProfileCatalog.cs
|
|
- src/AutoForge.Application/Features/Vehicles/Profiles/VehicleProfileServiceCollectionExtensions.cs
|
|
- src/AutoForge.UI/Features/Vehicles/Profiles/VehicleProfilePageViewModel.cs
|
|
- src/AutoForge.UI/Features/Vehicles/Profiles/VehicleProfilesPage.razor
|
|
- src/AutoForge.UI/Features/Vehicles/Profiles/VehicleProfilesPage.razor.css
|
|
- src/tests/AutoForge.UnitTests/VehicleProfileDomainTests.cs
|
|
- src/tests/AutoForge.UnitTests/VehicleProfileJsonCodecTests.cs
|
|
- src/tests/AutoForge.IntegrationTests/VehicleProfileCompositionTests.cs
|
|
- src/tests/AutoForge.IntegrationTests/Fixtures/synthetic-truck-baseline.json
|
|
- src/tests/AutoForge.IntegrationTests/Fixtures/synthetic-truck-variant.json
|
|
- src/tests/AutoForge.IntegrationTests/Fixtures/synthetic-orchard-vehicle.json
|
|
- docs/vehicle-profile-schema-v1.md
|
|
- docs/adr-0003-profile-interchange-v1.md
|
|
- prompts/Step-02-Report.md
|
|
|
|
Modified:
|
|
|
|
- src/AutoForge.Client/MauiProgram.cs — register the in-memory profile feature.
|
|
- src/AutoForge.UI/Features/Foundation/AddAutoForgeUi.cs — register the scoped
|
|
profile page view model.
|
|
- src/AutoForge.UI/Layout/MainLayout.razor and _Imports.razor — navigation and
|
|
feature namespace.
|
|
- src/tests/AutoForge.IntegrationTests/AutoForge.IntegrationTests.csproj —
|
|
copy source-controlled JSON fixtures to test output.
|
|
- src/tests/AutoForge.IntegrationTests/UiCompositionTests.cs — compose profile
|
|
services alongside the existing target-selection test registration.
|
|
- README.md, docs/README.md, docs/architecture.md and docs/build-and-test.md.
|
|
- docs/adr-0002-single-shell-vsa.md — reflect Step-01A acceptance and document
|
|
the later profile slice without changing shell boundaries.
|
|
|
|
No project, RCL, executable, package dependency, central package pin or test
|
|
project was added. No existing Core/Application target behavior was moved or
|
|
removed. Only the required Step-02 report was created under prompts.
|
|
|
|
## Architecture and tests
|
|
|
|
The existing seven-project graph remains unchanged:
|
|
|
|
- Client -> UI and Application.
|
|
- UI -> Components and Application.
|
|
- Application -> Core.
|
|
- Components and Core -> no AutoForge project dependency.
|
|
- UnitTests -> Core, Application and Components.
|
|
- IntegrationTests -> Core, Application, Components and UI.
|
|
|
|
No production/test edges, cycles, second host or backend were added. The new
|
|
Application profile slice is Features/Vehicles/Profiles. The UI page and view
|
|
model are in the UI RCL and use the real service by DI. The native Client composes
|
|
the same service used in headless tests.
|
|
|
|
New unit tests cover valid/custom roles, same-role distinct modules, duplicate
|
|
module/evidence/operation identifiers, immutable input snapshots, unknown
|
|
optional values, all capability states and missing-declaration behavior,
|
|
confidence boundaries/non-finite values, classifications, timestamps,
|
|
applicability, schema round-trip, duplicate/unknown/missing properties, malformed
|
|
and unsupported JSON, invalid status and dangling evidence.
|
|
|
|
New integration tests load the baseline/variant/alternate fixtures through real
|
|
Application DI; assert values, statuses, unknowns, evidence and exact revision
|
|
selection; export/reimport; preserve immutable baseline variants; reject duplicate
|
|
and conflicting vehicle identities; verify failed imports are atomic; compose
|
|
profiles beside the unchanged target resolver; and render the actual routed UI
|
|
with metadata, errors and export. The alternate fixture uses a custom module role,
|
|
custom operation and unknown model year. The original component, route, target
|
|
selection, application and project-graph assertions remain.
|
|
|
|
## Environment and command results
|
|
|
|
- Windows 10.0.26200.0; .NET SDK 10.0.402; runtime .NET/ASP.NET Core 10.0.13.
|
|
- Windows SDK target 10.0.26100.0; MAUI Windows workload manifest 10.0.110;
|
|
read-only workload listing reports workload version 10.0.403.
|
|
- WebView2 Runtime 155.0.4283.62.
|
|
- Existing central packages and VSTest/xUnit stack were used unchanged.
|
|
- No workload-changing inspection, installation, update, repair, uninstall or
|
|
rollback command was invoked for Step-02. Read-only dotnet workload list was
|
|
used only to inspect installed prerequisites.
|
|
|
|
Commands and results:
|
|
|
|
- dotnet restore .\src\AutoForge.slnx — exit 0; all projects up to date.
|
|
- dotnet build .\src\AutoForge.slnx --configuration Release --no-restore — exit
|
|
0; all seven projects including native Client built, 0 warnings, 0 errors.
|
|
- dotnet build .\src\AutoForge.Client\AutoForge.Client.csproj --configuration Release --framework net10.0-windows10.0.26100.0 --no-restore
|
|
— exit 0; actual Windows TFM/win-x64 Client, 0 warnings, 0 errors.
|
|
- dotnet test .\src\AutoForge.slnx --configuration Release --no-build — exit 0;
|
|
UnitTests: 59 passed, 0 failed, 0 skipped. IntegrationTests: 34 passed,
|
|
0 failed, 0 skipped. Total 93 passed, 0 failed, 0 skipped.
|
|
- Baseline Step-01/Step-01A coverage was 65 cases (39 unit and 26 integration);
|
|
it remains present in the expanded total. No required test was skipped or
|
|
removed.
|
|
|
|
## Native Windows profile smoke
|
|
|
|
Launched the actual Release native executable
|
|
src/AutoForge.Client/bin/Release/net10.0-windows10.0.26100.0/win-x64/AutoForge.Client.exe
|
|
with an isolated WebView2 profile and temporary local DevTools port. The native
|
|
window title was AutoForge and the BlazorWebView loaded at https://0.0.0.1/.
|
|
|
|
- Home rendered; navigation reached /vehicle-profiles and showed an empty catalog.
|
|
- Importing the synthetic truck baseline returned a success notice, listed one
|
|
revision and did not auto-select. Explicit revision-1 selection displayed
|
|
Synthetic provenance, capability declarations, unknown values and a JSON
|
|
export containing the baseline calibration reference and applicable year.
|
|
- Importing the separate truck variant listed revision 2. Selecting revision 2
|
|
exported its variant calibration identifier and not the baseline calibration;
|
|
both revisions remained listed.
|
|
- Duplicate baseline import showed an error and retained two entries and the
|
|
explicitly selected variant. Malformed JSON also showed an error without
|
|
changing the catalog or selected variant.
|
|
- Importing/selecting the alternate profile showed its custom module role,
|
|
custom operation, and unknown model year.
|
|
- Home and /execution-targets still rendered. Target selection showed its honest
|
|
empty-provider state; profile operations did not register a provider. The
|
|
unknown path rendered the existing not-found route.
|
|
- AutoForge.UI and AutoForge.Components scoped CSS assets returned HTTP 200 and
|
|
contained the profile/status styles. Healthy route display had no unhandled
|
|
error banner.
|
|
- Stopped the exact native process and removed its exact temporary WebView2
|
|
profile. No screenshot was retained; observations came from the live native
|
|
WebView DOM and resource responses.
|
|
|
|
## Acceptance criteria evidence
|
|
|
|
| Criterion | Status | Evidence |
|
|
|---|---|---|
|
|
| AC-01 | PASSED | Existing seven-project graph, target behavior and manual/protected workflow preserved; final complete suite reports all 65 baseline cases within 93 passes. |
|
|
| AC-02 | PASSED | Immutable validated profiles/configuration revisions, vehicle identities, arbitrary modules and explicit unknowns in Core; domain positive/negative tests pass. |
|
|
| AC-03 | PASSED | All five states and missing-declaration Unknown lookup; duplicate operations rejected and no operational behavior added. Unit and fixture integration assertions pass. |
|
|
| AC-04 | PASSED | Provenance classes/source/confidence/timestamps/applicability and explicit model-year/module identities round-trip; mismatch/dangling tests pass. |
|
|
| AC-05 | PASSED | Strict schema-v1 parser/serializer round-trips and rejects malformed, missing, future, unknown, duplicate, invalid-status and invalid-reference inputs. |
|
|
| AC-06 | PASSED | Real DI catalog supports exact revision selection, immutable revisions and atomic failure; rendered UI imports/lists/selects/exports; native workflow verified. |
|
|
| AC-07 | PASSED | Three checked-in synthetic fixtures cover truck baseline/revision variant, alternate inventory, custom role/operation, all capability states and explicit provenance. |
|
|
| AC-08 | PASSED | Full Release solution and direct native build each 0 warnings/errors; 59 unit and 34 integration tests pass; native profile/route/assets smoke completed. |
|
|
| AC-09 | PASSED | README/index/architecture/build guide/schema guide/ADR reflect actual metadata-only behavior and lifecycle; README working file is LF with no trailing whitespace. |
|
|
| AC-10 | PASSED | This report created; protected assignment/orchestration files unchanged; no Step-03, stage, commit or push. |
|
|
|
|
## Corrected failures and known limitations
|
|
|
|
- An early domain test exposed that an omitted capability collection was rejected
|
|
instead of representing no declarations. The direct constructor now snapshots
|
|
an empty collection; the missing lookup explicitly reports Unknown.
|
|
- Early tests also exposed incorrect test-input string replacements and a
|
|
route-message case mismatch. The test probes were corrected to mutate the
|
|
intended JSON property and assert the rendered message accurately.
|
|
- A first invalid-applicability test fixture replacement did not alter the JSON.
|
|
The test now replaces the first applicability vehicle ID explicitly; it
|
|
verifies vehicle mismatch rejection and catalog revision rebind rejection.
|
|
- A first native list probe selected by position after sorting rather than by
|
|
identity. The corrected native probe selects exact identifiers/revisions and
|
|
confirmed variant and alternate selections.
|
|
- One build/test pair was initially launched concurrently; MSB3026 reported an
|
|
xUnit output-file lock and retry. The subsequent final sequential full build
|
|
completed with 0 warnings/0 errors, followed by the successful full test run.
|
|
- A PowerShell DevTools helper invocation had a spacing typo and stopped after
|
|
native launch; the corrected run completed. A DevTools evaluation during a
|
|
navigation was invalidated when the WebView context changed; verification
|
|
reconnected and confirmed the not-found page. Neither was an application
|
|
failure.
|
|
- The catalog is in-memory and clears at process exit. Strict v1 rejects unknown
|
|
properties and future schema versions until a deliberate supported migration
|
|
is implemented. No real vehicle compatibility or operational support is
|
|
implied.
|
|
|
|
## Documentation, preservation and handoff
|
|
|
|
Added schema-v1 documentation and ADR-0003. Updated the root README, documentation
|
|
index, architecture/build guidance and ADR-0002. ADR-0001 and all prior reports
|
|
remain unchanged. Step-01A is described as accepted; Step-02 implementation is
|
|
complete for worker review, not yet manually accepted.
|
|
|
|
The root README working file is LF-normalized (149 LF, 0 CRLF, 0 trailing
|
|
whitespace). Git core.autocrlf is true and the existing index README is CRLF, so
|
|
Git emits its normal LF-to-CRLF working-copy warning; no global Git setting or
|
|
unrelated file was changed to suppress it. The CRLF-aware diff whitespace check
|
|
passed.
|
|
|
|
Final Git/status review found only the expected source, UI, tests, fixtures,
|
|
README and technical-documentation changes plus this new report. Prompts/
|
|
ROADMAP.md, STATE.md, Step-01/Step-01A assignments and reports, Step-02.md,
|
|
protected instructions and Git metadata were unchanged. The only prompts change
|
|
is this report. Top-level project directories remain docs, src and prompts.
|
|
No dependency pins changed, no workload-changing command was invoked, and no
|
|
commit, stage, push, destructive cleanup or automatic handoff occurred.
|
|
|
|
Implementation and verification are complete for manual orchestrator review.
|
|
STOP here; do not begin Step-03.
|
|
```
|