Files
hub/tasks/architecture/storage/specify-task-enum-pgenum.md
glm-5.1 2b63cda1c7 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.
2026-05-25 10:56:32 +00:00

1.1 KiB

id, name, status, depends_on, scope, risk, impact, level
id name status depends_on scope risk impact level
specify-task-enum-pgenum Specify Task Enum Values as Drizzle pgEnum completed
single trivial isolated implementation

Description

S15: The categorical enum values (scope, risk, impact, level, priority, status) are documented as text strings in tasks.md but not referenced as Drizzle pgEnum types. Specify that these should be pgEnum for type safety, with the decomposer template consuming the same definitions. This ensures DB-level constraints match the application-level typing.

Acceptance Criteria

  • tasks.md specifies that scope, risk, impact, level, priority, and status should use pgEnum in the Drizzle schema
  • Enum value lists in tasks.md match the pgEnum definitions
  • Note added that the decomposer template should consume these same enum definitions

References

  • docs/reviews/storage-architecture-review-2026-04-21.md#S15
  • docs/architecture/storage/tasks.md
  • docs/architecture/storage/table-reference.md (enum reference)

Notes

To be filled by implementation agent

Summary

To be filled on completion