Description
After charter adf migrate introduces formatting issues in .adf files (duplicate list markers like - - -, HTML comment blocks, markdown tables in CONTEXT sections), charter adf fmt --write would be the natural fix. However, fmt doesn't catch these structural issues.
Examples of artifacts fmt should normalize
- Duplicate list markers:
- - - Product: → - Product:
- HTML comments in ADF sections:
<!-- charter:module-index:start --> inside CONTEXT blocks should be stripped
- Markdown tables in ADF sections: Table syntax (
| Module | Triggers |) is not valid ADF content and should be flagged or removed
- Dangling references: Bare lines like
- \.ai/manifest.adf`` in CONSTRAINTS that are pointer artifacts, not actual constraints
Expected Behavior
If adf fmt is the canonical normalizer for ADF files, it should:
- Collapse consecutive list markers (
- - - → -)
- Strip HTML comments from ADF section bodies
- Flag or remove non-ADF content (markdown tables, raw URLs without context)
- Produce clean, parseable ADF output
This would serve as a safety net for migrate/tidy artifacts and also help users who hand-edit .adf files.
Environment
Description
After
charter adf migrateintroduces formatting issues in.adffiles (duplicate list markers like- - -, HTML comment blocks, markdown tables in CONTEXT sections),charter adf fmt --writewould be the natural fix. However, fmt doesn't catch these structural issues.Examples of artifacts fmt should normalize
- - - Product:→- Product:<!-- charter:module-index:start -->inside CONTEXT blocks should be stripped| Module | Triggers |) is not valid ADF content and should be flagged or removed- \.ai/manifest.adf`` in CONSTRAINTS that are pointer artifacts, not actual constraintsExpected Behavior
If
adf fmtis the canonical normalizer for ADF files, it should:- - -→-)This would serve as a safety net for migrate/tidy artifacts and also help users who hand-edit
.adffiles.Environment