Document the workflow and limits; flag capped histories

[adityamukho]

Closes #1.

This covers the last open acceptance criterion of #1, "Document intended workflow and limitations". The other three criteria were already met by the code merged in #3.

Changes

• README: a new "Typical workflow" section with six steps: load data, find a change, look at one entity or attribute, pick a point in both times, query at that point, keep or share it. The "Limits" list now also covers UTC times, whole-second valid time, entity names in opened files, and browser-only use.
• Transaction cap: when a database has more than 5,000 transactions, the app now shows a notice with how many it read. Before, it stopped at the cap without saying so.
• Tests: a unit test for the cap, and an e2e test that the bitemporal map shows the valid-time intervals of one attribute (:salary: the retracted 75000 and the corrected 80000).

Check against #1

Criterion	Where
Fact assertions and retractions over transaction time	Transaction log (+/−), green/red in the graph, map boxes that stop at the removing transaction, colored slider ticks
Valid-time intervals for selected entities or attributes	Bitemporal map with Entity and Attribute filters; inspector lists each version's valid range
Query results at selected temporal points	Query console with "Run at the time cursor", which adds :as-of and :valid-at and shows the query it ran
Workflow and limitations documented	README: "Typical workflow", "How it works", "Limits"

Tests

48 unit tests and 10 Playwright tests pass locally.

🤖 Generated with Claude Code

https://claude.ai/code/session_0134t1hJSVQnoAimuRboLxRp

---

Generated by Claude Code