Repository navigation
App placement and HTTP contracts 0.10.0
Pre-releaseStrict app placement and named HTTP route contracts are now reusable without Core. Surface/ApiRoute wire types, private/public action admission, native UI path/scope checks, declared slot permissions, route method/name/scope rules and limits retain the native grammar and precise error pointers.
Existing native views, known team scopes and read-only effects are mandatory trusted host policies without default approvals. Veyndo uses its existing view registry, scope catalog and verified read predicate. Full view compilation, actual actor/context grants, pinned UI bytes, installed-package authority, routing and action execution remain host responsibilities.
Validation: 78 independent model tests, direct model/storage clippy, runnable Rust example and actual isolated PostgreSQL storage/installation contract. Native composition is checked in the matching Core change. The README now groups reusable model contracts instead of accumulating separate release paragraphs.