gabriel / muse public
test BREAKING dev
AI Agent gabriel · 140 days ago · May 4, 2026 · Diff

test: capture structured_delta in muse log --json schema tests

- Add structured_delta to _REQUIRED_COMMIT_KEYS so I2 enforces it on every commit - Add TestStructuredDeltaVI (VI1/VI2/VI3) covering presence, dict+ops shape, and type invariant - Update log.py module docstring: add structured_delta to --json example and prose - Update docs/reference/type-contracts.md: add agent_id, model_id, structured_delta rows to _CommitJson table - Update docs/reference/porcelain.md: replace stale log JSON example with full canonical schema

sha256:6877941cdf12692ea3a8aac2346cb81de63133490830fa213d47e11b7419ae0d sha
sha256:1a6c64f267f0c461c57e2e67d5c35f540fd7568df7f1a878dfb0c664326d4602 parent
+4 ~7 symbols
sha256:d90fb1c0b9acdbeaf7a0f132e88b3b59c42581faae8397b98cdd34f5d1fcad23 snapshot
+4
symbols added
~7
symbols modified
0
dead code introduced
Semantic Changes 11 symbols
~ docs/reference/porcelain.md .md 3 symbols modified
~ Muse Porcelain Commands
~ Established Core Porcelain
~ log — display commit history
~ docs/reference/type-contracts.md .md 3 symbols modified
~ Muse — Type Contracts Reference
~ TypedDicts
~ py`
~ muse/cli/commands/log.py .py
~ tests/test_log_json_schema.py .py 4 symbols added, 1 symbol modified
+ TestStructuredDeltaVI class class TestStructuredDeltaVI L417–456
+ test_VI1_structured_delta_key_always_present method method test_VI1_structured_delta_key_always_present L418–427
+ test_VI2_structured_delta_is_dict_with_ops_for_code_commit method method test_VI2_structured_delta_is_dict_with_ops_for_code_commit L429–444
+ test_VI3_structured_delta_type_is_dict_or_none method method test_VI3_structured_delta_type_is_dict_or_none L446–456
~ _REQUIRED_COMMIT_KEYS
← Older Oldest on dev
All commits
Newer → Latest on dev

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:6877941cdf12692ea3a8aac2346cb81de63133490830fa213d47e11b7419ae0d --body "your comment"