@sleepy_panda_srl/portulan 0.1.3 → 0.2.0

package/cli/feedback.mjs

@@ -1,59 +1,7 @@
 #!/usr/bin/env node
-// `portulan feedback` — file an issue from a report you previewed, seam-scanned before it leaves the
-// machine, under the Gated tier. Milestone 7's inbound half; proposal
-// `../.portulan/proposals/0014-a-feedback-pipe-points-out-of-the-seam.md` is the design.
+// `portulan feedback`: file an issue from a report you previewed, seam-scanned before it leaves the machine.
 //
-// ## The sentence the whole file follows from
-//
-// **A feedback sender is a pipe from a private workspace into a record it does not control.** An issue
-// tracker's history is permanent and its visibility is the *repository's* to change — this one was
-// public from 2026-07-27 to 2026-08-03, private after that, and is public again, which is exactly why
-// "it is public" is the wrong thing to reason from in either direction: what a sender may safely
-// include cannot depend on a setting somebody else can flip, and this one has been flipped three
-// times. The workspace it sends *from* may be a company's — repo names, paths,
-// product identifiers, gate maps, memory. `docs/plan.md` → Protocol → The seam exists because this
-// project treats that leakage as unacceptable in the other direction, and this tool points at the same
-// wall pointing out.
-//
-// Two consequences, and they are the two things that would be hard to add later:
-//
-// 1. **The payload is assembled from a closed list**, never filtered after the fact. Nothing here reads
-//    the workspace's name, its repo cards, its gate map, its memory, a git remote, a branch, or any
-//    path. The one thing it reads out of the workspace is `portulan.spec`, a version number. A filter
-//    is a list of what to remove and is wrong the day something new arrives; a closed list is a list of
-//    what to include and is wrong only when somebody widens it on purpose.
-// 2. **This product never carries seam terms.** They are client-confidential by definition. The tool is
-//    *told where a list is* and reads it; it ships none, and a term list has no place in this
-//    repository.
-//
-// ## Gated means per action, and the refusal lives in the tool
-//
-// `send` without `--approve` prints the payload and exits 2. The approval cannot be inherited from an
-// earlier `draft` or `preview`, because `core/operating/autonomy.md`'s Gated tier is per action — and a
-// queue that flushes itself when the network returns is a silent send with extra steps, which is why
-// nothing here auto-sends, retries in the background, or treats an unsent draft as anything but a file.
-//
-// The refusal is **in the tool** rather than in a host's permission table on purpose. A `Bash(...)`
-// matcher in `.portulan/gates.json` would cover one spelling of at least three (`portulan feedback
-// send`, `npx portulan feedback send`, `node cli/feedback.mjs send`) and would suggest coverage it does
-// not have. A refusal the tool itself makes holds on every host, including the hosts with no hook
-// system at all — which is the platform-floor direction this project prefers everywhere else.
-//
-// ## Exit codes
-//
-// `0` the verb succeeded · `1` **a verdict was rendered and it was no** — today that is exactly one
-// thing, a seam hit · `2` could not run: a report that is not ready, an approval that was not given, a
-// term list that was named and could not be read, a missing `gh`. The split matters at the one place it
-// is easy to get wrong: an unreadable term list is **not** a clean scan, and a report missing a required
-// answer is not a judgement about anybody's workspace.
-//
-// ## What is deliberately not here
-//
-// No OAuth device flow — the user's existing `gh` login and nothing else. No relay: proposal `0014`'s
-// Q5(b) is a hosted service and `docs/vision.md` permits exactly one by name, so it is constitutional
-// and unbuilt. No telemetry, no crash reporter, no attachments, no screenshots, no log bundles — every
-// one is an unbounded channel through the wall this file is about. And **no labels**: `0014` rules that
-// the repository owns its own labels, so the form's title prefix is what marks the kind.
+// Exit 0 succeeded · 1 a seam hit, or a filed issue its report could not record · 2 could not run.
 
 import crypto from "node:crypto";
 import fs from "node:fs";
@@ -62,34 +10,18 @@ import path from "node:path";
 import { spawnSync } from "node:child_process";
 import { pathToFileURL } from "node:url";
 
-// `manifest.mjs` and not `portulan.mjs`: importing the entry point from a subcommand it dispatches to
-// is a cycle, and it hung `portulan feedback --help` at exit 13. The header there is the record.
+// Not from `portulan.mjs`: importing the entry point that dispatches here is a cycle, and hangs at exit.
 import { VERSION, REPOSITORY } from "./manifest.mjs";
 
 export class FeedbackError extends Error {}
 
-/**
- * The window a second send has to clear. Proposal `0014` asks for "a short cooldown [to catch] a loop"
- * beside the re-send no-op: the no-op stops the same report going twice, and this stops a script
- * filing twenty different ones. Short enough that a person filing two real reports in a sitting waits
- * once and understands why.
- */
 export const COOLDOWN_SECONDS = 60;
 
 // ===========================================================================================
 // The forms
 // ===========================================================================================
-//
-// THE ONE CARRIER, and it is a carrier because the alternative does not exist. The forms live at
-// `.github/ISSUE_TEMPLATE/*.yml` and `package.json`'s `files` does not ship them, so a published
-// package cannot read them; parsing YAML would need a dependency this CLI is ruled not to have, and
-// generating this map would need a build step it is ruled not to have either. So the map is written
-// here and `feedback.live.test.mjs` reads the real forms and fails when the two disagree — `0020`'s
-// repair where a single carrier is impossible: one carrier plus a rail on the pair.
-//
-// `filled` marks a section this tool answers rather than the user: `version` is the Portulan version,
-// `environment` is the structured block. A fact claimed by a `filled` section is left out of the
-// environment block, so a payload never states the same thing twice.
+
+// Mirrors the forms in `.github/ISSUE_TEMPLATE/`, which do not ship; `feedback.live.test.mjs` fails when they differ.
 export const FORMS = [
     {
         kind: "bug",
@@ -128,7 +60,7 @@ export const FORMS = [
                 label: "Which part of Portulan",
                 required: true,
                 options: [
-                    "doctrine — core/: the loop, autonomy, verification, memory, evolution, safety",
+                    "doctrine — core/: the loop, autonomy, verification, memory, evolution, safety, context",
                     "mechanism — cli/, spec/, the plugin: the code that checks and enforces",
                     "workspace — .portulan/: the policy layer and the gate map",
                     "packaging — the plugin, the marketplace, install and boot",
@@ -182,7 +114,6 @@ export function form(kind) {
     return FORMS.find((entry) => entry.kind === kind) ?? null;
 }
 
-/** The repository issues are filed into — `manifest.mjs` derives it from the `bugs.url` we publish. */
 export function defaultRepository() {
     return REPOSITORY;
 }
@@ -191,10 +122,6 @@ export function defaultRepository() {
 // The report file
 // ===========================================================================================
 
-/**
- * A filename slug, and it returns "" rather than inventing one. A title of punctuation has no name in
- * it, and a report called `2026-08-10-.md` is a file nobody can find again.
- */
 export function slug(title) {
     return String(title)
         .toLowerCase()
@@ -202,7 +129,6 @@ export function slug(title) {
         .replace(/^-+|-+$/g, "");
 }
 
-/** The scaffolded report — a file the user edits, which is the whole point of the file-first design. */
 export function scaffold(kind, { title, created, failedRecipe, failedExit } = {}) {
     const declared = form(kind);
     if (!declared) throw new FeedbackError(`\`${kind}\` is not a form. The three are: ${FORMS.map((f) => f.kind).join(" · ")}`);
@@ -221,7 +147,7 @@ export function scaffold(kind, { title, created, failedRecipe, failedExit } = {}
     ];
 
     for (const section of declared.sections) {
-        if (section.filled) continue; // this tool answers it; a user editing it would be edited over
+        if (section.filled) continue;
         parts.push(`### ${section.label}`);
         const guidance = section.options
             ? "<!-- Keep exactly ONE of the lines below and delete the rest. -->\n" + section.options.join("\n")
@@ -235,14 +161,6 @@ export function scaffold(kind, { title, created, failedRecipe, failedExit } = {}
     return `${parts.join("\n\n")}\n`;
 }
 
-/**
- * Read a report back. Frontmatter through `plugin-lint.mjs`'s reader would drag a 74 KB module in for
- * four `key: value` lines, so this reads the block directly — and the block it reads is the block this
- * file wrote, which is the case that makes a local reader honest rather than lazy.
- *
- * @returns {{fields: Record<string,string>, sections: Array<{label: string, text: string}>,
- *            acknowledgements: Array<{text: string, ticked: boolean}>}}
- */
 export function parseReport(text) {
     const lines = text.split(/\r?\n/);
     if (lines[0]?.trim() !== "---") throw new FeedbackError("the report has no frontmatter block");
@@ -290,7 +208,6 @@ export function parseReport(text) {
     return { fields, sections, acknowledgements };
 }
 
-/** HTML comments carry this tool's guidance to the author; none of it belongs in a public issue. */
 function stripComments(text) {
     return text.replace(/<!--[\s\S]*?-->/g, "");
 }
@@ -299,16 +216,7 @@ function stripComments(text) {
 // The payload
 // ===========================================================================================
 
-/**
- * The bytes that would be filed. `preview` and `send` both call this, which is *why* the demonstration
- * holds: the previewed body is not compared with the sent body, it **is** the sent body. Two renderers
- * that agree today are two carriers of one fact.
- *
- * `parts` is the same content split by section, so the seam scan runs over exactly what would leave the
- * machine rather than over a reconstruction of it.
- *
- * @returns {{repo: string|null, title: string, body: string, parts: Array<{label: string, text: string}>}}
- */
+/** `preview` and `send` both render through this, so the bytes previewed are the bytes sent. */
 export function payload(report, context = {}) {
     const declared = form(report.fields.kind);
     if (!declared) throw new FeedbackError(`\`${report.fields.kind}\` is not a form`);
@@ -343,13 +251,7 @@ export function payload(report, context = {}) {
     return { repo: context.repo ?? defaultRepository(), title, body, parts };
 }
 
-/**
- * Proposal `0014`'s second part: "Portulan version, spec version, host and version, OS and
- * architecture. If the report was started from a failure, the failing recipe's **id and exit code**."
- * Not the recipe's *output*, which carries paths and file contents.
- *
- * `claimed` holds what another field on this form already asks for, so nothing is said twice.
- */
+/** A failing recipe's id and exit code, never its output, which carries paths and file contents. */
 function environmentBlock(report, context, claimed = new Set()) {
     const facts = context.facts ?? {};
     const lines = [];
@@ -359,10 +261,6 @@ function environmentBlock(report, context, claimed = new Set()) {
         `Host: ${context.host ?? "not observable from the command line — re-run with --host to name it"}`,
     );
     lines.push(`Runtime: node ${facts.node ?? process.version}`);
-    // Every fact defaults to the real machine. `?? ""` on the release was a real defect and it was
-    // invisible in the suite, which injects all four: the shipped tool printed `System: darwin arm64`
-    // — a line silently one fact short of what this block says it carries. Caught by running the
-    // demonstration rather than by reading the code, which is where this class keeps being caught.
     lines.push(`System: ${facts.platform ?? process.platform} ${facts.release ?? os.release()} ${facts.arch ?? process.arch}`);
     if (report.fields["failed-recipe"]) {
         lines.push(`Failing recipe: ${report.fields["failed-recipe"]}, exit ${report.fields["failed-exit"] ?? "unrecorded"}`);
@@ -374,16 +272,7 @@ function environmentBlock(report, context, claimed = new Set()) {
 // The seam
 // ===========================================================================================
 
-/**
- * Find the term list, and be exact about which of the three locations answered — a scan whose source a
- * reader cannot name is a scan they cannot check.
- *
- * **Only `ENOENT` means absent, and only at the convention path.** `existsSync` answers false for
- * `EACCES`, which is how #166's layer at mode `0400` skipped every location it declared while reporting
- * green. A named list that cannot be read is could-not-run, always.
- *
- * @returns {{source: string|null, terms: string[]|null}} `source: null` means no list is configured.
- */
+/** `source: null` means no list is configured; a list named or present but unreadable throws. */
 export function locateTerms({ flag, env = {}, workspaceDir } = {}) {
     if (flag) return { source: `--seam-terms ${flag}`, terms: read(flag, `--seam-terms ${flag}`) };
 
@@ -408,25 +297,7 @@ export function locateTerms({ flag, env = {}, workspaceDir } = {}) {
     }
 }
 
-/**
- * `null` when the path is there, `"ENOENT"` when it is genuinely absent, and the errno otherwise. The
- * one carrier of *only ENOENT means absent* for path probes in this file — `existsSync` collapses all
- * three into `false`, which is how a tool tells a reader the wrong thing about their disk with complete
- * confidence.
- *
- * `lstatSync` rather than `accessSync(R_OK)` or `statSync`, and each difference is a question being
- * asked. Both of this file's probes ask *is something already here*, not *may I read it* — a report at
- * mode `0000` is a file that exists and must not be written over, while an unsearchable parent is a
- * place this tool cannot see into, and that deserves a different sentence.
- *
- * **And `lstat`, because `stat` follows symlinks.** A dangling symlink at the report path makes `stat`
- * throw `ENOENT`, so the probe would answer *absent*, and the write that followed would resolve the link
- * and **land outside the workspace** — which is how a scaffold leaves the tree it was meant to stay
- * inside, the rule `cli/new.mjs` already refuses on. `lstat` describes the link itself, so a symlink of
- * any kind is *something is already here*. Found by review on this pull request, as a sibling of the
- * `existsSync` repair one round earlier: the same probe, corrected twice, because the first correction
- * answered only the errno half of the question.
- */
+/** null when anything is there, a dangling symlink included; else the errno, `ENOENT` meaning absent. */
 function whyAbsent(at) {
     try {
         fs.lstatSync(at);
@@ -436,15 +307,6 @@ function whyAbsent(at) {
     }
 }
 
-/**
- * Every write this tool makes, through one place, and every failure of one turned into a sentence.
- *
- * A bare `writeFileSync` on a read-only directory reached the top-level catch, which prints
- * `unanticipated failure` and a stack trace. The exit code was already 2, so this is not a fail-open —
- * it is the other half of the same discipline: **could-not-run has to say what could not run**, and a
- * stack trace is what a tool prints when it has nothing to say. Found by review on this pull request,
- * at three sites.
- */
 function writeOrRefuse(at, contents, what) {
     try {
         fs.mkdirSync(path.dirname(at), { recursive: true });
@@ -462,35 +324,12 @@ function parseTerms(text) {
         .map((line) => line.toLowerCase());
 }
 
-/**
- * The digest of a payload, and the reason `preview` is not optional.
- *
- * Row 7's demonstration is *"a send whose exact payload the user saw first"*, and for one draft of this
- * tool that was a property of the **flow** rather than of the mechanism: `send --approve` on a report
- * nobody had previewed filed sight-unseen, and a report edited between the preview and the send filed
- * bytes that differed from the ones that were read. Both printed the payload in the same breath, which
- * is not the same as having been seen — nobody is reading a terminal between two lines of one command.
- *
- * So `preview` stamps this digest into the report and `send` refuses unless it matches. The approval is
- * then bound to bytes rather than to an intention, and *the user saw it first* is structural. It covers
- * the machine facts too, since they are in the payload: preview with `--host X` and send without, and
- * the digest differs, because the bytes do.
- *
- * **Only `preview` stamps.** A `send` that refused for want of approval also printed the payload, and
- * stamping there would let a refusal manufacture the approval-eligibility it just declined to grant.
- */
+/** Only `preview` stamps it: a refused `send` prints the payload too, and stamping there would approve it. */
 export function digest(built) {
     return crypto.createHash("sha256").update(`${built.title}\n${built.body}`, "utf8").digest("hex");
 }
 
-/**
- * Case-insensitive substring, over the payload's own parts. Substring rather than word-boundary
- * because the terms that matter here are names and identifiers that turn up glued to other text —
- * a host, a path fragment, a ticket prefix — and a scan that missed those would be the reassuring kind.
- *
- * The hit names the term and the section and never quotes the surrounding text: this output goes to a
- * terminal and often to a log, and echoing the context would leak the thing the scan just caught.
- */
+/** Substring, since terms turn up glued to other text; a hit never quotes its context, which would leak. */
 export function scan(parts, terms) {
     const hits = [];
     for (const part of parts) {
@@ -603,12 +442,6 @@ function draft(rest, flags, { say, warn, now }) {
         warn("feedback: draft needs a --title. It becomes the issue's title and the report's filename.");
         return 2;
     }
-    // A single line, refused at the door beside the failure pair below and for the same reason. The
-    // title is written verbatim into `title: …`, and frontmatter is one key per line — so a newline or
-    // a carriage return would split it, and everything after the break would be read as another key or
-    // as body. This door already validates the two facts it is handed; the title was the neighbour it
-    // did not. Found by review on this pull request. The refusal is also the `control-chars` rule this
-    // repository already rails the tree with, applied to an argument.
     if (/[\r\n]/.test(title)) {
         warn("feedback: a title is one line. This one carries a line break, and frontmatter is one key per line —");
         warn("feedback: everything after the break would be read as another key, or as the body.");
@@ -620,9 +453,6 @@ function draft(rest, flags, { say, warn, now }) {
         return 2;
     }
 
-    // The failure pair is validated at the door rather than on the way out. A recipe id that is not a
-    // slug, or an exit code that is not an integer, means somebody is passing something other than the
-    // two facts `0014` allows — and this is the one place a report picks up anything it was not typed.
     const failedRecipe = flags["failed-recipe"];
     const failedExit = flags["failed-exit"];
     if (failedRecipe !== undefined && !SLUG.test(failedRecipe)) {
@@ -639,12 +469,6 @@ function draft(rest, flags, { say, warn, now }) {
     }
 
     const workspaceDir = path.resolve(flags.into ?? ".portulan");
-    // ONLY `ENOENT` MEANS ABSENT, here as at the term list. Both of these were `existsSync`, which
-    // answers false for `EACCES` — so an unreadable workspace was reported as *no workspace.json* and
-    // an unreadable report as *no report*, each sending the reader to the wrong fix. Found by review on
-    // this pull request, in the change whose own comments name the class for the seam scan two hundred
-    // lines up: a rule enforced at one site of an operation and not its neighbour is `0020`'s shape,
-    // committed inside the change that quotes `0020`.
     const manifest = path.join(workspaceDir, "workspace.json");
     const absent = whyAbsent(manifest);
     if (absent === "ENOENT") {
@@ -695,25 +519,11 @@ function report(verb, rest, flags, { say, warn, now, env, exec, facts }) {
 
     const parsed = parseReport(text);
 
-    // Already filed. Refused before anything else, because the answer is the same whatever the rest of
-    // the report says and because a duplicate is the failure a user notices in public.
     if (parsed.fields.issue) {
         warn(`feedback: this report was already filed — ${parsed.fields.issue}. Draft a new one to say something new.`);
         return 2;
     }
 
-    // THE WORKSPACE IS DERIVED FROM THE REPORT'S PATH, AND A WRONG DERIVATION IS A SEAM FAIL-OPEN.
-    //
-    // `<workspace>/feedback/<report>` is where `draft` writes, so two levels up is the workspace. Move
-    // the report anywhere else and the derivation still produces *a* directory — one with no
-    // `seam-terms.txt` in it — and the scan then says **nothing was scanned** while a term list sits in
-    // the workspace this report actually belongs to. A green that reports its own coverage is only
-    // honest if the coverage sentence is about the right place, and this is the one path where being
-    // wrong about it sends unscanned bytes into a public tracker.
-    //
-    // So the layout is checked rather than assumed, and a report outside it is could-not-run. Found by
-    // review on this pull request; it is the seam's own fail-closed rule applied to the step that
-    // decides *where the seam lives*, which the first cut assumed instead of establishing.
     const workspaceDir = path.dirname(path.dirname(at));
     if (path.basename(path.dirname(at)) !== "feedback") {
         warn(`feedback: ${at} is not inside a workspace's \`feedback/\` directory.`);
@@ -788,8 +598,6 @@ function report(verb, rest, flags, { say, warn, now, env, exec, facts }) {
         return 2;
     }
 
-    // The approval is bound to bytes, not to an intention. See `digest` for why this is a refusal
-    // rather than a warning: without it, "the exact payload the user saw first" is a habit.
     if (!parsed.fields.previewed) {
         warn("feedback: this report has not been previewed, so there are no bytes you have approved.");
         warn(`feedback: run \`portulan feedback preview ${at}\` and read them, then send.`);
@@ -815,11 +623,7 @@ function report(verb, rest, flags, { say, warn, now, env, exec, facts }) {
     const auth = exec("gh", ["auth", "status"]);
     if (auth.error || auth.status === null) {
         warn("feedback: `gh` was not found. This sender files under your own GitHub identity and operates no service of its own.");
-        // NOT `--body-file <the report>`. That was the first draft's suggestion and it was wrong in the
-        // one way that matters here: the report carries frontmatter, this tool's guidance comments and
-        // the raw sections, none of which is the payload — so following it would have published bytes
-        // nobody previewed, out of the verb whose whole subject is that they cannot be. Caught by
-        // review on this pull request. The two honest routes are the tool and the form.
+        // Never `--body-file <the report>`: the report is not the payload, and would file bytes nobody previewed.
         warn("feedback: install it and run this again, or paste the body printed above into the form:");
         warn(`feedback:   https://github.com/${built.repo}/issues/new/choose  —  title: ${built.title}`);
         warn(`feedback: the report stays at ${at}. Its payload is the bytes between the markers above, and nothing else in it is sent.`);
@@ -845,14 +649,7 @@ function report(verb, rest, flags, { say, warn, now, env, exec, facts }) {
         return 2;
     }
 
-    // THE ONE WRITE THAT CANNOT BE A REFUSAL, because by now the issue exists in the world.
-    //
-    // `writeOrRefuse` would throw here and the top-level handler would print `feedback: …` and exit 2 —
-    // *could not run*, about an operation that ran and filed. Worse, the sentence would send a reader
-    // back to try again, and the guard that makes a second send a no-op is exactly what just failed to
-    // land. So the send is reported as what it was, the missing guard is named, and the exit code says
-    // something is wrong without pretending nothing happened: **1**, a verdict — not 0, which would
-    // hide it, and not 2, which would deny the send. Found by review on this pull request.
+    // Not `writeOrRefuse`: the issue exists now, so a failed stamp exits 1, not 2, which would deny the send.
     try {
         fs.writeFileSync(at, stamp(text, { issue: url, sent: now().toISOString() }));
     } catch (error) {
@@ -870,12 +667,8 @@ function report(verb, rest, flags, { say, warn, now, env, exec, facts }) {
     return 0;
 }
 
-/** Every reason this report is not ready, in one pass — a user fixing one at a time is a user we lost. */
 function validate(parsed, declared) {
     const problems = [];
-    // `draft` refuses an absent or unsluggable title, but a report is a file a human edits and the
-    // frontmatter is part of it. Without this, a blanked `title:` files as a bare `[feedback] ` — a
-    // public issue with no subject, from the one verb where the artifact is permanent.
     if (!(parsed.fields.title ?? "").trim()) {
         problems.push("`title:` is empty, and the issue's title is the form's prefix plus that line.");
     }
@@ -903,11 +696,7 @@ function validate(parsed, declared) {
     return problems;
 }
 
-/**
- * The workspace's spec version, and the ONE thing this tool reads out of a workspace. Soft rather than
- * fail-closed on purpose: it is a line in an environment block, not a gate, and refusing to send a
- * report because a manifest was unreadable would put the seam's discipline behind a decoration.
- */
+/** The one fact the payload takes from a workspace: "unknown", never a refusal, when it cannot be read. */
 function readSpec(workspaceDir) {
     try {
         return JSON.parse(fs.readFileSync(path.join(workspaceDir, "workspace.json"), "utf8")).portulan?.spec ?? "unknown";
@@ -916,7 +705,6 @@ function readSpec(workspaceDir) {
     }
 }
 
-/** The most recent recorded send in this directory, for the cooldown. */
 function lastSend(workspaceDir, except) {
     const dir = path.join(workspaceDir, "feedback");
     let names;
@@ -943,20 +731,11 @@ function lastSend(workspaceDir, except) {
     return latest;
 }
 
-/**
- * Record something in the report's own frontmatter — the local artifact `0014` asks for.
- *
- * `replacing` names keys to drop first, so a second `preview` updates its digest rather than stacking
- * a second `previewed:` line that `parseReport` would silently resolve to the last one.
- */
 function stamp(text, additions, replacing = []) {
     const lines = text.split(/\r?\n/);
     const close = lines.indexOf("---", 1);
     if (close === -1) throw new FeedbackError("the report's frontmatter block is never closed");
 
-    // Scoped to the frontmatter. Filtering the whole file would delete a body line that happened to
-    // begin `previewed:` — a tool editing prose it was not asked to edit, which is worse than the
-    // duplicate key it would be preventing.
     const front = lines.slice(1, close).filter((line) => {
         const key = /^([A-Za-z_][\w-]*)\s*:/.exec(line)?.[1];
         return !(key && replacing.includes(key));