dedot
Goal
Find every middle dot (U+00B7) in the text the writer named, give each one a single verdict, and propose a replacement only for dots that join an open list. The review never edits the writer's text.
Workflow
When this applies
Run the review only when the writer asks for a middle-dot or punctuation review of a named Korean passage, field, section, file, selection or folder, including a final pass over text after a rewrite. For any other request (a summary, a general copyedit or spelling pass, a check of other punctuation marks such as commas or quotation marks, a translation, a rewrite), do that task as asked, at the full reach it calls for, and leave this skill out of it: no review section, and no mention of this skill, its rules or the fact that it was not used. The restraint below (only the separators change, the comma comes first, one verdict per dot, nothing said about other marks) shapes middle-dot proposals and nothing else; it never narrows another task. Such a task covers everything it asks for (in a copyedit: spelling, spacing, wording, other punctuation, sentence flow), gives each problem the fix that reads most naturally rather than the smallest one, and offers alternatives wherever a careful editor would; in a copyedit, middle dots are ordinary editing like any other mark. If the writer asks for the dots to be fixed directly in the file, do the edit they asked for, applying the judgment below to each dot (legitimate and protected dots stay, each list keeps its relation), change nothing else, and say plainly which spans changed and which dots were left and why.
Scope
The scope is exactly what the writer named. If a named file or path does not exist, say which path you looked for, mention a similarly named file nearby only as a question, and stop without reviewing anything. Create, rename or edit no file, not even a temporary extract. When the scope is part of a file (a field such as a store-listing description, the section under one heading), find its first and last line and pass them with --lines. Dots outside the scope are neither judged nor counted; one line saying that other parts also contain middle dots, with an offer to review them on request, is enough.
Finding the dots
Run node scripts/find.mjs <file-or-folder> [--lines A-B] [--json]. It lists every U+00B7 in scope with its line, column, a kind and the line text, then the in-scope total, the dots outside --lines, and any look-alike characters (U+318D ㆍ, U+2027 ‧, U+30FB ・ and others), which are different characters: never counted, never changed, mentioned only as not in scope. The kinds code, url, quote, digits, formula, catalan and bullet are protected contexts it recognised mechanically, and they stay in the count. review is everything else: read each in its full sentence or row and judge it below, and still check it for a protected context the script cannot see, such as a proper name. The script is your instrument; the report talks about the writer's text, never about the script, its kinds or exit codes. If you read files any other way, read them as UTF-8 (set PYTHONUTF8=1 for Python).