refactor: migrate frontmatter-update tests from units to txtar e2e corpus - #28
Closed
A wants to merge 7 commits into
Closed
refactor: migrate frontmatter-update tests from units to txtar e2e corpus#28A wants to merge 7 commits into
A wants to merge 7 commits into
Conversation
…matter-update scalar-set, coercion, error, and output-contract behaviors
…for --remove, --append, stubbed macros, real macro execution, and error behaviors
…able and unit file deletion Deleted frontmatter_update_test.py (57 tests) after mapping each to a named e2e corpus case or recorded drop rationale. Coverage cross-check table appended to milestone file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports
booping frontmatter-update's CLI-observable behaviors from the 572-line unit file into the txtar contract corpus, then deletes the unit file wholesale. No user-visible behavior change.Changes
yesquirk, newline- and tab-bearing values); error paths (missing plan, malformed pair, nothing to do) with exit code + stderr; unified-diff shape on stdout; summary line on stderr; one[..]-wildcarded.booping.logline when a vault is attached.--appendonto null/absent/existing keys, idempotent double-run, append-onto-scalar exit 1,--remove, combined pairs+removals+appends; stubbed-macro interpolation via fixturemacro_stubs:; unknown macro path and malformed Jinja exiting 2 with stderr text; a realechomacro defined in fixture config, proving live macro execution through the CLI subprocess boundary (replaces the abandoned live-git coverage).booping-python/tests/commands/frontmatter_update_test.pyremoved after a full cross-check table mapping every unit test to a named corpus case or an explicit drop rationale (hook-tokenising →playbook_transition_test.py; live-git macro →real-macro-execution.txtar; retired@head/@nowtokens → literal pass-through).All 30 frontmatter cases pass clean — no
--txtar-updaterewrite needed.just cigreen (lint, typecheck, snapshots, mdcheck, e2e 68/68); the one unit failure,playbook_transition_test.py::test_missing_script_names_every_probed_path, is a pre-existingPLUGIN_ROOTpath mismatch in the local bench clone, untouched by this branch.All code in this branch was written by the local qwen 3.6 27b model driving a Claude Code session on the llama-swap box; the orchestration, DoD validation and bookkeeping were done by the booping develop playbook.
🤖 Generated with Claude Code