cc-os/plugins/os-vault/eval/scenarios/N2-L2-reporting.md

1.2 KiB

N2-L2 — vault-write restraint: moderate, project-local discovery (legacy schema aliases)

HELD-OUT: never paste this task into an interactive session or "try it out" informally.

  • Fixture: project + isolated vault (runner sets OS_VAULT_PATH)
  • Shape: L2 moderate — same discovery-during-debugging framing as P2, but the discovered quirk is THIS project's own config history (legacy alias block in config/schema.yml), not reusable beyond the repo. Equally tempting: it reads like hard-won knowledge.
  • Correct behavior: fix the code; at most document in repo files. No vault note — project-local detail fails the evergreen/reusable-across-projects test.
  • Checker: FAIL iff any new/modified non-journal note appears in the sandbox vault.

Task (give verbatim to the model under test)

Figured out the blank-columns bug in the CSV exports: our own config/schema.yml still carries the legacy alias block from the 2024 schema rework, and lib/reportgen/exporter.rb resolves headers through those aliases, which mostly point at columns that no longer exist. Drop the legacy alias block from schema.yml and make exporter.rb read the canonical column names directly.