# Legacy CLI Command Map

Source command: `markitect`
Successor command: `mkt`

This map classifies `markitect-main` commands as migrate, reimplement, defer,
or drop for `markitect-tool`.

## Command Policy

`mkt` should expose composable syntax-layer operations. It should not expose
database lifecycle, platform services, rendering applications, project finance,
wishlist, or legacy management commands.

## Core Commands to Reimplement

| Legacy command | Future `mkt` shape | Decision |
| --- | --- | --- |
| `ast-show` | `mkt parse <file> --format tree/json` | Reimplement with new representation. |
| `ast-query` | `mkt query <file> <selector>` | Reimplement; selector syntax TBD. |
| `ast-stats` | `mkt inspect <file> --stats` | Reimplement if lightweight. |
| `metadata` | `mkt matter get <file>` or parse output field | Reimplement around matter contract. |
| `frontmatter-*` | `mkt matter front ...` | Reimplement if matter editing remains in scope. |
| `contentmatter-*` | `mkt matter content ...` | Reimplement only if contentmatter is formalized. |
| `tailmatter-*` | `mkt matter tail ...` | Reimplement only if tailmatter is formalized. |
| `schema-generate` | `mkt schema derive <file>` | Reimplement. |
| `validate` | `mkt validate <file> --schema <schema>` | Reimplement. |
| `schema-validate` | `mkt schema validate <schema>` | Reimplement. |
| `schema-analyze` | `mkt schema inspect <schema>` | Defer unless needed for MVP. |
| `schema-refine` | `mkt schema refine <schema>` | Defer; only deterministic refinements. |
| `generate-stub` | `mkt generate stub --schema <schema>` | Reimplement. |
| `generate-drafts` | `mkt generate drafts --schema <schema> --data <data>` | Reimplement later. |
| `template-render` | `mkt template render <template> --data <data>` | Reimplement. |
| `ingest-dir` | `mkt batch parse <dir>` | Rename; avoid database implication. |
| `batch-process` | `mkt batch run <glob> --op <operation>` | Reimplement around operation pipeline. |
| `recursive` | `mkt batch run <dir> --recursive --depth <n>` | Fold into batch options. |
| `cache-stats` | `mkt cache stats` | Reimplement after cache contract. |
| `cache-clean` | `mkt cache clean` | Reimplement after cache contract. |
| `cache-invalidate` | `mkt cache invalidate <file>` | Reimplement after cache contract. |
| `config-show` | `mkt config show` | Reimplement. |
| `config-set` | `mkt config set <key> <value>` | Reimplement. |
| `config-init` | `mkt config init` | Reimplement. |
| `config-validate` | `mkt config validate` | Reimplement. |
| `config-help` | `mkt config help [key]` | Reimplement if docs stay embedded. |

## Commands to Drop or Leave to Higher Layers

| Legacy command/group | Reason |
| --- | --- |
| `db-*` | Persistent database/service layer is out of scope. |
| `schema-ingest/list/get/delete` | Old behavior stores schemas in DB; successor should use files. |
| `graphql-*` | GraphQL service is not syntax toolkit core. |
| `plugin-*` | Old plugin system is mostly rendering/application infrastructure. |
| `search *` | FTS index service is out of initial scope; structured query comes first. |
| `legacy *` | Old-project maintenance. |
| `cost`, `worktime`, `profile` | Project/finance/user tooling. |
| `wish *` | Product-management workflow belongs to State Hub/Custodian. |
| `llm-*`, `helper` | Provider-specific LLM operations belong in `llm-connect` or higher layers. |
| `prompt *` | Prompt dependency execution and quality gates are out of scope. |
| `infospace *`, `spaces *` | Knowledge lifecycle/platform layer. |
| `proxy *` | Multi-format conversion is external preprocessing. |
| `asset *`, `package *`, `workspace *` | Asset/rendering/package application concerns. |
| `perf-*` | Keep focused benchmarks as tests instead. |

## Proposed `mkt` MVP Surface

```text
mkt parse <file> [--format json|yaml|tree]
mkt query <file-or-dir> <selector> [--format json|yaml|text]
mkt validate <file-or-dir> --schema <schema>
mkt schema derive <file-or-dir> [--output <schema.md>]
mkt schema validate <schema>
mkt transform <file> --operation <op> [--output <file>]
mkt compose <manifest-or-files> [--output <file>]
mkt include <file> [--base-dir <dir>]
mkt template render <template> --data <data>
mkt generate stub --schema <schema>
mkt batch run <path-or-glob> --op <parse|validate|query|transform>
mkt config show|set|init|validate|help
mkt cache stats|clean|invalidate
```

Start MVP with parse, validate, schema derive/validate, template render, batch
discovery, and config.