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.
2.5 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| review-sync-completeness | Review Sync Completeness and Cross-Reference Consistency | completed |
|
broad | high | phase | review |
Description
Final review gate after all sync tasks are completed. Verify that the codebase and documentation are consistent with the core library extractions. This is the stabilization gate before resuming feature development.
Checks
-
No stale references: Search entire
docs/directory for:packages/core/operations/→ should be@alkdev/operationspackages/core/pubsub/→ should be@alkdev/pubsubpackages/core/mcp/→ should be@alkdev/operations/from-mcpcore/operations/→ should be@alkdev/operationscore/pubsub/→ should be@alkdev/pubsubPubSubPublishArgsByKey→ should bePubSubEventMap@repeaterjs/repeateras a direct dependency → should note it's inlined in@alkdev/pubsub"Not started"for WebSocket EventTarget → should note it's implemented"Not started"for Call Protocol → should note it's implemented
-
Package structure: Verify
packages/core/is deleted, workspace config is correct, hub package has proper deno.json -
Type check:
deno checkpasses across the workspace -
AGENTS.md accuracy: Read through AGENTS.md and verify every claim is current
-
overview.md accuracy: Read through overview.md and verify every status is current
-
Cross-reference integrity: Every doc that mentions a module has the correct package name
-
Breaking changes documented: Verify that all breaking API changes from the review doc (Section 1.5) are reflected in relevant architecture docs
Acceptance Criteria
- No stale
packages/core/operations/orpackages/core/pubsub/references in docs - No stale
Not startedstatus for WebSocket EventTarget or Call Protocol packages/core/is deleted from workspacedeno checkpasses on workspace- AGENTS.md is accurate and current
- overview.md status table is accurate
- All breaking API changes (ResponseEnvelope, buildEnv, ScannerFS, etc.) are documented in relevant specs
References
- docs/reviews/core-library-extraction-sync-2026-05-18.md (full document)