/**
 * .what = tells whether OUR OWN invocation's setup minted a run, despite this
 *         process holding no run id
 * .why = 🔴 it is the ONE discriminator between two cells that SHARE A SYMPTOM and
 *        must never share a message:
 *
 *          no run id + no marker of ours  →  a genuinely unhooked consumer. their
 *                                            config is at fault; name the two keys
 *          no run id + a marker of OURS   →  our setup DID run for this very
 *                                            invocation, and the id failed to reach
 *                                            this process. a BROKEN MINT CHAIN —
 *                                            OUR defect, reported loudly and
 *                                            correctly by the teardown's own guard
 *
 *        by ENV those two states are identical, which is why the unhooked notice
 *        fired on both: it told a consumer to add config they had already added,
 *        and blamed them for a defect of ours. `case=10`'s demo forbids exactly
 *        that — *"the two cells share a symptom and must never share a message."*
 *
 *        the env cannot tell them apart. the DISK can, and it is already ours to
 *        read: a marker is written ONLY by our own setup
 *
 * .note = 🔴 the test is PID LINEAGE, never "is some run live". a coarser form —
 *         *any* marker whose process still answers — silences the notice for an
 *         unhooked consumer who merely runs beside a wired peer in the same scope,
 *         and this repo's own acceptance children proved it: they spawn beneath a
 *         live wired parent, and every unhooked case went silent.
 *
 *         a marker's `pid` is the process that ran the setup. our own invocation's
 *         setup is therefore either THIS process (a `--runInBand` run, or a vitest
 *         thread pool that shares one pid) or our PARENT (the fork the runner made
 *         to carry us). a peer's runner is neither, by construction — so the false
 *         positive is excluded rather than filtered (`rule.prefer.prevent-over-correct`)
 *
 * .note = the STATE is not read at all, and that is deliberate. `held`, `partial`,
 *         and `open` alike prove the setup ran; the question here is provenance,
 *         never progress
 *
 * .note = the answer is MEMOIZED per process, and it may be: a process cannot
 *         change invocations mid-life. without the memo a broken chain pays one
 *         readdir per allocation, in the worker — the exact cost profile this
 *         behavior exists to avoid
 *
 * .note = the HEALTHY path never calls this at all — a run that HAS an id does not
 *         ask. so a wired consumer pays no scan whatsoever
 */
export declare const isOwnRunMinted: (input: {
    tmpDir: string;
}) => boolean;
/**
 * .what = clears the memoized answer
 * .why = enables tests to drive both branches in one process
 *
 * @internal - only for test use
 */
export declare const resetOwnRunMinted: () => void;