Artifact Description [80ae671092]

Artifact 80ae67109261c7b97711fb1b145cb1783976871e2d573ede52326ed1a4ee2f72:

• File README.md
  • 2026-07-19 22:10:59 — part of check-in [ab4951c2e8] on branch p5b-docs — docs: honest 0.1.0 limitations table and release notes

    Add a Limitations section to the README and a docs/RELEASE-NOTES-0.1.0.md release asset, both re-derived from current shipped behavior rather than assumed.

    The caveats are the deliberate deferrals, verified against the binary and source: diff is working-tree-vs-current-check-in and name-status only, with no rev-to-rev form; the sync server code is a fixed informational placeholder while the per-repo project code is real (derived on init, persisted, adopted on clone); the R and W cards are parsed but not interpreted, whereas T and U are acted on; and stash/grep/ui/settings have no equivalent.

    The notes name the local fossil 2.28 that the interop smoke passes against, flag that the runner version lags and must be confirmed at ship, and cite the pack re-deltification measurements to their benchmark commit bab9303056. (user: dmestas, size: 4207) [annotate] [blame] [check-ins using]

  • 2026-07-19 22:41:58 — part of check-in [7ba838ab6c] on branch trunk — Merge p5b-docs: 0.1.0 release notes and an honest limitations table

    Adds the release notes as a shipped asset and a limitations section to the README, both stating plainly what 0.1.0 does not do: diff is name-status against the current check-in only, the sync server code is an informational placeholder while the project code is real, the R and W cards are carried but not interpreted, and stash/grep/ui/settings and rev-to-rev diff are absent. The notes record what the conformance claim rests on -- smoke driving the real fossil binary in CI -- and cite the pack measurements to their existing benchmark rather than restating them as fresh claims. The version stamp is left for the ship step. (user: dmestas, size: 4207) [annotate] [blame] [check-ins using]