hanzo-dev
7875ae4caa
Split from hanzoai/cloud clients/framework, preserving history. This is the VALUE layer: schema definition and validation, field-value coercion, the autoname engine, argon2id Password hashing, the permission calculus, and the app-lane fixture registry. It performs no I/O, so a code generator, a UI renderer or an app lane declaring its content model can depend on it and link no database. The split line is 'does answering this question require the database'. Coercing a value to its fieldtype does not, so it lives here; verifying a Link exists in the org does, so it stays in the engine. - validate.go -> coerce.go, keeping only the DB-free half - permission.go -> perm.go, keeping only the calculus (Grants); role resolution needs tenant state and stays in the engine - resolveName moves in from store.go: it is pure naming, not storage - adds a test suite for the value layer (schema, coercion, naming, secrets, permissions, registry) Co-authored-by: Hanzo Dev <dev@hanzo.ai>