zara-coding: validate commit tree object identities #187

New issue

Closed

opened 2026-09-08 02:03:10 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:10 +00:00

Owner

Advances #1.

RepositoryInspector.commit() validates expected_head and the newly-created commit ID, but currently trusts git write-tree and git rev-parse <head>^{tree} outputs as object identities. A malformed tree ID can therefore be returned as structured commit evidence or compared as if canonical Git identity.

Acceptance:

deterministic RED for malformed staged-tree and parent-tree object IDs;
accept canonical 40- and 64-hex Git object IDs;
reject malformed tree identity with bounded CodingError before commit-tree/update-ref mutation;
preserve expected-head fencing, attached-branch requirement, no-staged-change rejection, bounded commit message, and structured commit evidence;
focused tests, registry compatibility, full nix flake check, generated package builds, exact-head protected merge.

Advances #1. `RepositoryInspector.commit()` validates `expected_head` and the newly-created commit ID, but currently trusts `git write-tree` and `git rev-parse <head>^{tree}` outputs as object identities. A malformed tree ID can therefore be returned as structured commit evidence or compared as if canonical Git identity. Acceptance: - deterministic RED for malformed staged-tree and parent-tree object IDs; - accept canonical 40- and 64-hex Git object IDs; - reject malformed tree identity with bounded `CodingError` before commit-tree/update-ref mutation; - preserve expected-head fencing, attached-branch requirement, no-staged-change rejection, bounded commit message, and structured commit evidence; - focused tests, registry compatibility, full `nix flake check`, generated package builds, exact-head protected merge.

nsaspy closed this issue

2026-09-08 02:03:11 +00:00

nsaspy referenced this issue from a pull request that will close it,

2026-09-08 02:19:40 +00:00

coding: fail closed on changing branch inventory #387