Skip to content

Baseline filenames don't match consolidated frame IDs #1

Description

@nickcottrell

What

After the consolidation in 1714881 (46 → 26 chapter configs with new chXX_<slug> IDs), the configs in .build/contexts/ use the new naming (ch01_eye_of_the_tempest.yaml) but manuscript/_seed/baseline/ still uses the old act1_chN.md convention.

Why it matters

  • The README's "diff against the canonical baseline to see how close it landed" workflow requires a 1:1 filename mapping. Right now there isn't one.
  • Anyone running generate_unified_all.sh produces frames named chXX_*.md in manuscript/drafts/draft-<ts>/, with no obvious way to compare them to the corresponding baseline.

Suggested fix

Rename manuscript/_seed/baseline/*.md to match the new frame IDs from .build/contexts/. Mapping comes from each config's chapter_id field. A small script reading the configs and renaming the baselines would be deterministic.

If the baselines are conceptually different from the consolidated structure (e.g. one new frame absorbed two old chapters), the renaming script should at least drop a CSV mapping in _archive/ so the lineage is preserved.

Out of scope

The 4 broken-YAML configs (ch01, ch09, ch10, ch13) were patched separately in e5e6e4a.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions