docs(site): the communication pass — threat model, homepage claims, status (#134)

* docs: neutral posture — rendered docs carry no issue references

Documentation addresses app authors in the present tense; history and
provenance live in git, issues, and the decision records.

* docs(site): the communication pass — threat model, homepage claims, status

The threat-model page states in one place what the sync server can and
cannot see, what the user holds, the ticket/XSS custody story, and
where the lines move (shared-field encryption designed; metadata
blindness out of scope under the pinned engine). It is the definition
behind the homepage phrase 'the user holds the keys', which stays.

Homepage: the offline-reconciliation copy now states what the CRDT
actually guarantees — every edit survives, replicas converge, same-field
collisions resolve last-writer-wins — and the limits section carries the
project status plainly: five canaried engine defects at the pin, not yet
for data you cannot afford to lose, and a link to the threat model.
README carries the same status. The two current decision records join
the site sidebar (numberPrefixParser off so ids match filenames), and
sync-and-recovery and permissions cross-link the threat model.

Part of #122 (§1-§3) and closes out #123's D section.

commit

c4ef777579023db6ec6ee769a57ca23db1ba2379

parent

8642d2989609bbc9481401ca26d2416b72112d25

author

FelineStateMachine <dami.etoile@gmail.com>