From 73c3b295af515b2d31f55d6fe4593979ce0f48ef Mon Sep 17 00:00:00 2001 From: "Ullman, Brad (DCYF)" Date: Fri, 27 Mar 2026 17:12:26 -0700 Subject: [PATCH 01/21] add plan and progress --- .gitignore | 1 + plan.md | 173 ++++++++++++++++++++ progress-src-step-templates-legacy-clean.md | 81 +++++++++ 3 files changed, 255 insertions(+) create mode 100644 plan.md create mode 100644 progress-src-step-templates-legacy-clean.md diff --git a/.gitignore b/.gitignore index 96cc31e06..2d1c306e9 100644 --- a/.gitignore +++ b/.gitignore @@ -13,6 +13,7 @@ step-templates/*.ps1 step-templates/*.sh step-templates/*.py diff-output/ +.tmp*/ /.vs !.vscode *copy.ps1 diff --git a/plan.md b/plan.md new file mode 100644 index 000000000..6fc258b20 --- /dev/null +++ b/plan.md @@ -0,0 +1,173 @@ +# Plan: Rebuild The Step Template Unpack Work From `master` + +## Goal + +Start from `master` and implement a safe migration path from legacy packed templates in `step-templates/*.json` to editable source folders in `src/step-templates//`. + +The result should preserve existing site behavior while making script changes reviewable as normal files. + +## Desired End State + +For every step template: + +- source lives under `src/step-templates//` +- `metadata.json` contains template metadata only +- script content lives in separate files +- packed `step-templates/*.json` can still be generated for existing consumers +- migration can be done gradually in batches without breaking the build + +## Constraints + +- `master` currently treats `step-templates/*.json` as the legacy artifact shape +- the migration must be incremental, not a flag day rewrite +- reviewability matters, especially for script changes +- round-trip equivalence matters more than elegance + +## Work Breakdown + +### 1. Define The Source Format + +Choose and document the source-root contract: + +- `src/step-templates/