mirror of
https://github.com/himanshudongre/smriti.git
synced 2026-08-28 05:14:59 +00:00
3b6ef000dc
The repo-state section added by the previous commit shows working-tree and git-upstream drift. It does not answer the question Smriti's trust story actually needs: has the repo moved since the last checkpoint? Record git provenance on checkpoints and compare against it. The CLI captures the git HEAD and branch when it creates a checkpoint; the V4 commit endpoint stores that under the commit's context_blob and returns it on read. `smriti state` then compares the working repo against the latest checkpoint's recorded HEAD/branch and surfaces: - repo unchanged since the last checkpoint - repo is N commit(s) ahead — recorded state may be stale - repo history has diverged from the last checkpoint - the last checkpoint was taken on a different branch All local and read-only: no fetch, no reconciliation. Checkpoints made before this feature (or by the MCP server) record no git state and are simply left uncompared. |
||
|---|---|---|
| .. | ||
| alembic | ||
| app | ||
| config | ||
| tests | ||
| alembic.ini | ||
| Dockerfile | ||
| pyproject.toml | ||