Add YAML->JSON migration cleanup to 0.10.0 plan

Section 6 now includes dropping the one-time YAML import that shipped in
0.9.0: the shadow structs and import path in storage, the legacy path
names, the go.yaml.in/yaml/v4 dependency, the import tests, and the
*.yaml ignore rules.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
mixeme
2026-06-24 00:51:51 +03:00
parent 55e90d80d3
commit bf9c1517a5
+11
View File
@@ -114,6 +114,17 @@ guarantee and does not have a clean per-job meaning).
has had field use. Recheck `.gitignore` / Docker / packaging ignore rules.
Keep the startup-timing instrumentation (the History "Started … in Xms" event)
so startup time can keep being measured across future changes.
- **Drop the one-time YAML→JSON migration.** The import shipped in 0.9.0, so the
transition window has passed. Remove the legacy import path:
- `src/storage/store.go`: delete the `yamlConfig` / `yamlJob` / `yamlJobsFile`
shadow structs, `importYAMLConfig` / `importYAMLJobs`, and the legacy-import
branches in `loadOrCreateConfig` / `loadOrCreateJobs`.
- `src/storage/paths.go`: remove `legacyYAMLConfigFileName` /
`legacyYAMLJobsFileName`.
- `go.mod` / `go.sum`: drop `go.yaml.in/yaml/v4` (now unused) via `go mod tidy`.
- `src/storage/store_test.go`: remove the YAML-import tests and the `writeYAML`
helper.
- `.gitignore` / `.dockerignore`: drop the `*.yaml` import-window ignores.
- **Architecture doc update.** Refresh `docs/ARCHITECTURE.md` for this milestone:
the per-job overlap policy on `domain.Job` (§4), the run-time statistics added to
`domain.JobRuntime` and seeded from log files (§2), and any `jobs_view.go` split