v1.0.5.post2

v1.0.5.post2: type-system documentation.

A maintainer reading the docs as a user found that the type system
was never documented as a coherent whole — a reader had to assemble
it from the graph, events, relations, and patches concept pages,
and the question "are there base object types, or just the Diligence
pack as an example?" never got a direct answer.

This post-release adds a dedicated type-system page and a README
orientation section covering the three layers:

Event types are framework-defined — a fixed vocabulary (object.created,
behavior.failed, patch.applied, and so on, plus custom event types
behaviors can emit as any string).

Object and relation types are developer-defined — any string works,
no central schema, no registration. Packs can attach optional Pydantic
validation per type, but absent a pack the data passes through. The
Diligence pack's object and relation types are an example ontology,
not framework base types.

Patch states are framework-defined: proposed, applied, rejected.

The new concepts/type-system page covers all three layers, the
composition narrative, ontology design guidance, and the Diligence
pack as a worked example. The README gains a compact "type system at
a glance" section with the full event-type vocabulary inline.

Both the rendered doc page and the machine-readable /llms.txt and
/llms-full.txt regenerate from the same source markdown.

CONTRACT v1.0.5.post2 documents the work and surfaces two v1.1
candidates (an events.md doc-drift fix and a reason-taxonomy
enumeration).

See CHANGELOG.md for full notes.