Problem
The container can produce dependency graph manifests and croco doctor can inspect .croco/build/di-graph.manifest.json, but the app-facing generation workflow should be explicit and deterministic for 1.0.
Desired outcome
Users and generated apps have a stable command to write and verify DI graph manifests.
Acceptance criteria
- Add or document a command such as
croco di graph --write .croco/build/di-graph.manifest.json.
- Ensure deterministic ordering for providers, dependencies, root IDs, and diagnostics.
- Emit stable diagnostic codes for missing providers, circular dependencies, and scope mismatches.
- Add generated app smoke coverage for manifest generation plus
croco doctor verification.
- Document the local recovery workflow for DI graph failures.
Problem
The container can produce dependency graph manifests and
croco doctorcan inspect.croco/build/di-graph.manifest.json, but the app-facing generation workflow should be explicit and deterministic for 1.0.Desired outcome
Users and generated apps have a stable command to write and verify DI graph manifests.
Acceptance criteria
croco di graph --write .croco/build/di-graph.manifest.json.croco doctorverification.