You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 368aa6d
Browse filesBrowse the repository at this point in the historyBrowse files
🚨 Bind a Git observation to the route and the turn it was read on (#940)
Four corrections both #940 reviewers reproduced against 94496999.
**A directory is a directory under either spelling.** `<Git.File path="dir/" />`
answered with the blob at `dir/inside.txt` under a path claiming to be `dir/`.
The argument Git receives is a pathspec rather than a lookup: `dir` matches the
directory entry and `dir/` matches the things inside it, and the read took the
first record without checking whose path it was. It now resolves the entry at
exactly the path asked for; a path that matched records but is not one of them
is the directory it is, and refuses.
**Trusted admission holds a saved route to the history that made it.** A fully
shaped observation whose checkout named a root nothing selected was admitted,
and its completed terminal reused with no Git at all — the body that checks the
live registry is never entered for a completed terminal. Admission now requires
the selection and the checkout to be ones a preceding placement in that same
history made, before completed or unfinished reuse, decided from parsed
historical facts with no canonicalization and no `git`. A cold reuse whose
checkout has since been deleted still answers, and a history holding no
observation record is unaffected.
**One entry's reads and mutations share one native turn.** The reads keyed it
`observation <commonDirectory>` while the transitions and the publication keyed
it `git <commonDirectory>`, so sharing the serializer shared nothing: a
same-entry `<Git.Add>` reached native Git while a `<Git.Diff>` still owned its
multi-command read. The key is now named once, `nativeGitTurn()`, and all three
callers take it — held through joined teardown and the acknowledged append.
Cross-entry independence is untouched: that is a mutation lease, not this queue.
**The journey's two missing checkpoint-2 reads and its per-phase immutability
evidence** are completed in `sidekick-journey-completion.md` through the real
terminal and ACP Sidekick, with paired before/after fingerprints around every
phase. The original journey's proven portions stand. Its host count is corrected
to 95 of 447 with 8 `config` calls, and its unverifiable tree metadata is
withdrawn for a tree object this repository holds.
Co-Authored-By: Claude Opus 5 <[email protected]>
0 commit comments