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.
This commit is contained in:
36
tasks/architecture/storage/resolve-key-version-redundancy.md
Normal file
36
tasks/architecture/storage/resolve-key-version-redundancy.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
id: resolve-key-version-redundancy
|
||||
name: Resolve client_secrets KeyVersion Redundancy
|
||||
status: completed
|
||||
depends_on: []
|
||||
scope: narrow
|
||||
risk: low
|
||||
impact: isolated
|
||||
level: implementation
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
W07: `client_secrets` has both a standalone `keyVersion` column (integer NOT NULL DEFAULT 1) AND `keyVersion` embedded in the `value` JSONB (`EncryptedData.keyVersion`). These can diverge with no documented invariant.
|
||||
|
||||
Either remove the standalone column (read from `value.keyVersion`), or document that the standalone column is authoritative and must be kept in sync with the JSONB value.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] Decision documented: remove standalone column OR document authoritative source
|
||||
- [ ] If keeping standalone: add invariant that standalone column and `value.keyVersion` are always in sync
|
||||
- [ ] `services.md` updated to reflect the decision
|
||||
- [ ] `table-reference.md` updated if column is removed
|
||||
|
||||
## References
|
||||
|
||||
- docs/reviews/storage-architecture-review-2026-04-21.md#W07
|
||||
- docs/architecture/storage/services.md:71, :82-86
|
||||
|
||||
## Notes
|
||||
|
||||
> To be filled by implementation agent
|
||||
|
||||
## Summary
|
||||
|
||||
> To be filled on completion
|
||||
Reference in New Issue
Block a user