hub/tasks/sync/archive-migration-research.md at main

alkdev/hub

Files

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

2.4 KiB

Raw Permalink Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

archive-migration-research

Archive or Update Migration Research Docs

completed

narrow

trivial

isolated

implementation

Description

The docs/research/migration/ directory contains two files describing planned extractions that are now complete:

operations.md — Planned extraction of packages/core/operations/ and packages/core/mcp/ into @alkdev/operations
pubsub.md — Planned extraction of packages/core/pubsub/ into @alkdev/pubsub

Both contain detailed current-state analysis, migration steps, and open questions that are now resolved. They served their purpose but are now outdated and potentially confusing.

Options

A. Archive (recommended): Move both files to docs/research/migration/completed/ with a status note at the top. This preserves them for historical reference without cluttering the active research directory.

B. Update: Rewrite as "completed migration" docs showing before/after. More work for less value — the review doc already captures the migration impact.

C. Delete: Remove entirely. Loses historical context.

Also: Mark resolved findings in consistency review

docs/reviews/docs-consistency-review-2026-04-17.md has several findings that are now resolved by the extractions. Add resolution notes:

Finding	Original Issue	New Resolution
C5	PendingRequestMap is in core, not hub	Resolved: now in `@alkdev/operations`
I2	`env.ts` has PendingRequestMap interface only	Resolved: full implementation in `@alkdev/operations`
I5	`OperationContext.pubsub` typed as unknown	Resolved: `pubsub` field removed from context
I6	`OperationContext.stream` never populated	Resolved: `stream` field removed from context
I7	`@repeaterjs/repeater` version mismatch risk	Resolved: inlined in `@alkdev/pubsub`, no external dep

Acceptance Criteria

docs/research/migration/operations.md is archived or clearly marked as completed
docs/research/migration/pubsub.md is archived or clearly marked as completed
Consistency review findings C5, I2, I5, I6, I7 are marked as resolved with resolution notes
No active doc references docs/research/migration/ as authoritative for current state

References

docs/reviews/core-library-extraction-sync-2026-05-18.md (Section 2.13, 2.14)

2.4 KiB Raw Permalink Blame History