Misaka16384 tidy
When to use
magi math check reports errors, tags have sprawled into near-duplicates, or
two concept cards are about the same thing.
Method
Maths. magi math format first — it fixes mechanically what it can, free.
Then magi math check --json for what is left. Work one file at a time: fix
the first entry, re-check, and watch the rest of that file's errors vanish —
one unclosed $$ swallows everything after it and reports as many errors.
likely-macro is usually a false positive; check the source with
magi ingest crop <pdf> before touching it.
Tags. magi tags extract ., read the counts, and write the mapping that
collapses synonyms, acronyms and plurals into one tag. Show it to the human
before magi tags apply . <tag_map> <alias_map> — it rewrites every card. Two tags that are aliases of
each other usually mean two cards about one concept.
Concepts. magi link --dedup-only proposes merges. Confirm each is really
one concept, then magi wiki refactor-concept --project-dir . --old <a> --new <b>. A sub-concept
merges into its parent; read it back with magi wiki context --name <c> first.
Close with magi lint --fix and magi index.
Rules
- Never apply a tag mapping the human has not seen. It is not reversible by hand.
- Never rename a concept by editing filenames;
refactor-conceptis the only route that fixes the links too. - The unit of work is the project, not the file: re-run
magi math checkat the end and report what is still broken as partial, not as done.