105-1: Setup seed path: domain correction
Status: 2026-04-03
Contents key
This page
Related pages
Public steps
- 105-3: Align pipeline-spec-lib and README with the target model
- 105-4: Prove test runs, J01-9 unblocking, and the closing picture
- 105-2: Full P_0-to-P_n derivation and manifest thinning
Step-specific public work status for 105-1 under J01-105. This page isolates the setup seed case because it fixes a model error before the wider manifest thinning can be trusted.
Goal
setupmust no longer depend onLEBENSLAUF_PUBLIC_PROFILE.- Sample content is provided only through one fixed source and one fixed target.
- Existing user data must not be overwritten silently by the setup path.
Report
- Initial finding: the former seed path coupled sample content to the build profile, which made the setup semantics incoherent.
- Target state from the issue derivation:
--copy-sample-contentinstead of--reset-sample-content, fixed sourcesrc/resources/fixtures/lebenslauf/daten-gueltig.yaml, fixed targetdaten-sample.yaml, explicit failure when the target already exists. - This step records the domain cut and the evidence plan; implementation and check runs remain open in the source repo.
Current status
- Jira subtask
J01-122exists. - The domain target state is separated from the rest of
J01-105and is publicly referenceable. - Code and test evidence are still open for this step.
Verification plan
| Check | Expectation | Evidence / Location | Status |
|---|---|---|---|
| Setup decoupled | LEBENSLAUF_PUBLIC_PROFILE no longer appears in the seed path |
app repo, setup code | open |
| Fixed sample source | Seed reads daten-gueltig.yaml as a fixed fixture |
app repo, setup code | open |
| Fixed target name | Seed writes to daten-sample.yaml |
app repo, setup code | open |
| No silent overwrite | Existing target triggers a clear error path | app repo, check run | open |
Open points
- Align how the new seed path must be reflected in CLI, README, and tests.
- Decide whether existing setup tests are extended or newly cut.