Vijay Janapa Reddi 2b381bb949 refactor(vault-cli): rename --legacy-json to --local-json ...

The flag is the StaffML frontend's local-dev fallback (read corpus.json
from disk via NEXT_PUBLIC_VAULT_FALLBACK=static), not a deprecated path.
"Legacy" implied "soon to be removed"; "local-json" describes its actual
role and reads correctly in scripts and docs.

- vault-cli: rename CLI flag, parameter, result key, and help text.
- CI workflows + pre-commit config: invoke the new flag name.
- All scripts that print the command (suggest_exemplars,
  pre_commit_corpus_guard, promote_validated, rename_legacy_ids,
  export_to_staffml, the paper analyze_corpus/generate_*) updated.
- Comments and docs (ARCHITECTURE, CHANGELOG, REVIEWS, TESTING,
  MASSIVE_BUILD_RUNBOOK, DEPRECATED, AUTHORING, plus frontend
  comments and .env.example / .gitignore) updated.

The "legacy_json" sentinel string in corpus_stats.json._meta.source
is intentionally NOT renamed — it is a stable artifact format read
by downstream paper-generation tooling.

2026-04-30 09:30:28 -04:00

..

ID_SCHEMES.md

docs: refresh paper + ID_SCHEMES for new published count (9,224)

2026-04-25 09:54:44 -04:00

id-renames-2026-04-25.yaml

refactor(vault): rename 4,754 cohort-tagged IDs to clean <track>-NNNN form

2026-04-25 10:32:20 -04:00

MASSIVE_BUILD_RUNBOOK.md

refactor(vault-cli): rename --legacy-json to --local-json

2026-04-30 09:30:28 -04:00

QUESTION_QUALITY_RUBRIC.md

…