Setup repo: migrate architecture specs, code stubs, and tasks from alkhub_ts

Copy architecture docs, ADRs, storage domain specs, research, reviews,
and 56 storage architecture tasks from the alkhub_ts monorepo. Adapt for
standalone @alkdev/hub repo structure (src/ not packages/hub/).

Sanitize all sensitive information:
- Replace private IPs (10.0.0.1) with localhost defaults
- Remove internal server hostnames (dev1, ns528096)
- Replace /workspace/ private paths with npm package references
- Remove hardcoded credentials from examples
- Rewrite infrastructure.md without private network details

Add Deno project scaffolding: deno.json (pinned deps), .gitignore,
AGENTS.md, entry point. Migrate existing code stubs (crypto, config
types, logger) with updated import paths.

tasks/architecture/storage/storage-spec-stabilization.md

@@ -0,0 +1,32 @@
+---
+id: storage-spec-stabilization
+name: Storage Spec Stabilization
+status: pending
+depends_on: [cascade-decisions, data-integrity-specs, spec-adr-consistency, index-strategy, security-specs, add-account-deactivation, add-audit-log-context, add-caller-account-id, add-spoke-reconnecting-state, clarify-session-spec-details, define-call-graph-retention, document-accesslevel-authorization, document-system-account-email-convention, document-api-key-expiration-behavior, document-cross-table-status-mapping, document-edge-type-semantics, document-jsonb-column-boundaries, document-mappings-valid-shapes, document-org-ownership-transfer, enhance-detections-table, fix-parts-timestamps-spec, improve-mappings-spec, rename-task-dependencies-column, resolve-key-version-redundancy, specify-task-enum-pgenum, split-operations-into-definitions-and-registrations, config-hub-startup-system, review-cascade-data-integrity, review-security-encryption-config, review-operations-schema-stabilization]
+scope: broad
+risk: critical
+impact: project
+level: review
+---
+
+## Description
+
+THE top-level meta-task for stabilizing the storage architecture. This is the gate that must pass before implementation of the storage layer can begin. It depends on all five sub-groups: cascade decisions, data integrity specs, spec/ADR consistency, index strategy, and security specs. When this is complete, the storage spec is implementable without contradictions or critical gaps.
+
+## Acceptance Criteria
+
+- [ ] All dependent tasks are completed
+- [ ] Cross-references between completed tasks are consistent
+- [ ] No remaining contradictions in the covered domain
+
+## References
+
+- docs/reviews/storage-architecture-review-2026-04-21.md
+
+## Notes
+
+> To be filled by implementation agent
+
+## Summary
+
+> To be filled on completion