Files
markitect-tool/workplans/MKTT-WP-0002-markitect-main-migration.md

100 lines
2.4 KiB
Markdown

---
id: MKTT-WP-0002
type: workplan
title: "markitect-main Scope Extraction"
domain: markitect
status: done
owner: markitect-tool
topic_slug: markitect
planning_priority: complete
planning_order: 20
depends_on_workplans:
- MKTT-WP-0001
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_id: "0fe54d2c-d579-4b03-a647-7a15bb835893"
---
# MKTT-WP-0002: markitect-main Scope Extraction
## Purpose
Inventory `markitect-main`, identify which behavior belongs in the new
syntax-layer toolkit, and prepare migration/reimplementation slices.
## P2.1 - Complete first-pass scope assessment
```task
id: MKTT-WP-0002-T001
status: done
priority: high
state_hub_task_id: "950de9fd-7540-4e0f-bc4a-2fa86fc9fccc"
```
Compare the old repo against the new PRD/FRS and document candidate modules,
out-of-scope areas, and migration principles.
## P2.2 - Extract reusable behavior test list
```task
id: MKTT-WP-0002-T002
status: done
priority: high
state_hub_task_id: "994a8c17-bd13-476b-9b8e-86c50e1c4897"
```
Review `markitect-main/tests`, `testdata`, schema fixtures, and CLI integration
tests. Create a candidate test migration list organized by FRS section.
Technical debt: `TD-MKTT-002`.
Output: `docs/markitect-main-test-migration-inventory.md`.
## P2.3 - Map legacy commands to `mkt`
```task
id: MKTT-WP-0002-T003
status: done
priority: high
state_hub_task_id: "f82b1f2c-887b-4378-b70b-84c1cb051742"
```
Inventory old `markitect` CLI commands and classify each as migrate,
reimplement, rename, defer, or out of scope for `mkt`.
Output: `docs/legacy-cli-command-map.md`.
## P2.4 - Decide compatibility policy
```task
id: MKTT-WP-0002-T004
status: done
priority: medium
state_hub_task_id: "56a12905-c3ec-42b0-893a-47ef023ea10a"
```
Define whether any old module paths, command names, file formats, or schema
names deserve compatibility shims in the successor.
Output: `docs/compatibility-policy.md`.
## Extension Points
`EP-MKTT-002` tracks the query backend adapter boundary: keep the initial query
API small, but leave room for JSONPath-like or alternate selectors if they fit
the provider-neutral contract.
## P2.5 - Identify external dependencies
```task
id: MKTT-WP-0002-T005
status: done
priority: medium
state_hub_task_id: "4d51e763-bf5f-483b-8948-6306ff5a58bb"
```
Separate core dependencies from optional integrations. Initial candidates:
`markdown-it-py`, `PyYAML`, `jsonpath-ng`, and optional `llm-connect`.
Output: `docs/dependency-classification.md`.