Hasna Service Contract v1

[andrei-hasna]

Implements the Hasna Service Contract v1 in @hasna/contracts (bump 0.2.2 -> 0.3.0).

Deliverables

• CONTRACT.md — normative spec: docs tiers (local/self_hosted/cloud); runtime storage enum local|cloud ONLY per Amendment A1 (PURE REMOTE — no sync engine, no cache mode, no hybrid/merge; only sanctioned exception is the todos dual-write SHADOW); remote/hybrid/self_hosted accepted as deprecated cloud aliases; env spec HASNA_<NAME>_STORAGE_MODE + HASNA_<NAME>_DATABASE_URL (+ <NAME>_ aliases); GET /health -> {status,version,mode}, /ready, /version; bins allowlist <name>/<name>-mcp/<name>-serve + extras; sqlite ~/.hasna/<name>/<name>.db; secret ref hasna/oss/<name>/database-url; root docker-compose.yml self-host artifact; repo classes library/cli-with-store/service/saas with per-class ship rules.
• hasna.service_contract.v1 — Zod schema (ServiceContractManifestSchema) + src/hasna.contract.schema.json JSON Schema (name, class, contractVersion, kitVersion, bins, storage) with class-rule validation. Registered in the schema registry.
• Conformance kit — runRepoConformance() + contracts repo-conformance CLI: manifest valid, bins allowlist + package.json match, mode-enum compliance, health shape (when serve exists), and no forbidden shared cloud runtimes (reuses scanNoCloudTarget). Dev-dep friendly.
• src/mode.ts — reference storage-mode normalizer extracted from open-mailery's normalizeMaileryMode, generalized with env resolution.
• Fixtures + tests/mode.test.ts, tests/service-contract.test.ts, tests/conformance.test.ts.

Verification

bun run verify:release green (typecheck, 83 tests, conformance, build, smoke:dist, pack dry-run). Staged secrets scan clean.

[andrei-hasna]

Worker review for todos task eef976e6 (2026-07-06): PR #2 is already merged into origin/main via 085e4b7, and PR CI verify passed. Independent/adversarial post-merge review found two residual follow-ups rather than an active merge blocker: (1) CONTRACT.md uses self_hosted for operator Docker/Postgres, which conflicts with current canonical deployment terms where self-hosted means Hasna-owned AWS; tracked as todos task 9a1404df. (2) verify/repo-conformance is not idempotent after ignored dist/ exists; bundled dist scanner declarations trigger no_cloud_guard failures; already tracked as tasks 7e45cbad and 4dc16a85, with fresh repro evidence added to 4dc16a85. Local evidence: bun run verify:release passed once on origin/main 42a1287; then bun test and repo-conformance failed with dist present. No code changes made by this worker.