@3f-consulting/spec-controller-core 0.1.0-alpha.8 → 0.1.0-alpha.81

package/dist/parse/scenarios.d.ts

@@ -1,239 +1,14 @@
-/**
- * The SCENARIO reader — parse spec-controller's own `features/**\/*.feature` source
- * into evidence obligations: per scenario, `{ scnId, evidenceObligations }`, with
- * each (kind, level) drawn from the scenario's evidence tags (@unit → runtime/unit,
- * @integration → runtime/integration, @e2e → runtime/e2e, @performance →
- * runtime/performance — the evidence-obligation reading).
- *
- * One of the three separated inputs to the reconciler (obligations / observations /
- * static checks) — the embryonic obligation-side adapter, deliberately not a registry (v1).
- *
- * Approach: scan TAG LINES (a line whose first non-blank char is `@` and whose
- * every whitespace-separated token is a tag) for an @SCN-<FFF>-<NNN> id and any
- * co-located evidence-level tags. A scenario's @SCN id and its level tags sit on
- * the same accumulated tag block immediately above the Scenario keyword, so a tag
- * line carrying an @SCN id contributes that scenario's evidenceObligations from the level
- * tags found across the contiguous tag block.
- *
- * The `lint` quality-check is raised by a scenario's REGISTERED bare check tag, STEPS OR NONE
- * (`fitnessObligationsOf`, @SCN-LNT-006): the tag says which axis a scenario is on and the steps say
- * nothing about it (3F-3115). The retired `@lint=<guard>` form — where the scenario
- * named a runnable npm script and the run was matched back to it BY NAME — raises nothing
- * (@SCN-LNT-007): it supplies no citation, so anything it raised could never be credited under
- * the one posting rule and would read `missing` for ever. The form is inert in the READER, which
- * is what makes it retired rather than merely unused.
- *
- * Parent: @SCN-LDG-001.
- */
 import type { Scenario, QualityCheck } from "../model.js";
-import type { FitnessCheckIndex, UnspecifiedFitnessRow } from "../domain/fitnessChecks.js";
-/**
- * Recognise a `<quality-check>pending` tag (evidence-manifesto §11B) — return its deferred
- * quality-check, or `null` when the bare tag is not one of the five recognised `<qc>pending`
- * (a bare tier tag, an unknown `<x>pending`, or bare `pending`). The pure per-tag helper
- * `parseScenarios` uses to derive a pending obligation.
- */
+export declare const SCN_CODE: RegExp;
 export declare function pendingQualityCheck(tag: string): QualityCheck | null;
-/**
- * Every recognised `<quality-check>pending` spelling, derived from the map above rather than
- * listed again (@SCN-STG-002, 3F-3302).
- *
- * WHY A LIST AND NOT JUST THE PREDICATE. `pendingQualityCheck` answers "is THIS tag one", which
- * is all an obligation needs. The tag-grammar rule needs the other direction too — the words to
- * measure an unrecognised tag AGAINST, so it can name the tier a typo resembles — and a list
- * written out over there would agree with this map by diligence and then drift the first time a
- * quality-check is added.
- */
-export declare const PENDING_QUALITY_CHECK_TAGS: readonly string[];
-/**
- * The bare tags that name a RUNTIME evidence tier, derived from the map above (@SCN-STG-002,
- * 3F-3302). Exported for the same reason as the pending list beside it, and kept beneath the map
- * it reads so the two can never be edited apart.
- */
-export declare const RUNTIME_QUALITY_CHECK_TAGS: readonly string[];
-/**
- * Count every raw `@SCN-FFF-NNN` occurrence across the WHOLE source — including the
- * non-tag-line context (prose, comments, step text) the tag-line `parseScenarios`
- * deliberately ignores. A sibling read over the same source; `parseScenarios` is
- * unchanged. Each scenario contributes exactly one tag-line occurrence, so
- * the delta against `parseScenarios(...).length` is precisely the ids seen in non-tag
- * context.
- */
 export declare function countScnOccurrences(source: string): number;
-/**
- * The PROSE-ONLY @SCN codes (@SCN-RPT-015) — codes that appear in non-tag
- * context (prose / comments / step text) but are NEVER an @SCN tag ANYWHERE in the
- * corpus: dangling references. A CROSS-CORPUS set difference `proseCodes − tagCodes`
- * over ALL sources (unique, sorted): per source each line is inspected — a tag line
- * contributes its @SCN tokens to the TAG set; any other line contributes its @SCN
- * matches (the leading `@` stripped) to the PROSE set. The union across files is
- * load-bearing: a code tagged in one file but mentioned in prose in another is NOT
- * prose-only. Distinct from `countScnOccurrences`'s raw count (occurrences, not unique
- * dangling codes). The bare code (e.g. `SCN-FOO-001`) is its own locator.
- */
-export declare function proseOnlyCodes(sources: string[]): string[];
-/**
- * Parse the UNTAGGED scenarios — Gherkin scenario headers whose preceding contiguous
- * tag block carries no `@SCN` id (@SCN-RPT-014). Mirrors `parseScenarios`'s
- * tag-block accumulation: a tag line accumulates the block; any non-tag line closes it.
- * At each scenario header, the just-accumulated block is checked for an `@SCN` — if it
- * has none, the scenario is untagged (returns its name). The obligation-side counterpart
- * to the evidenceObservations aggregate's anomaly terms: a scenario with no evidence anchor.
- */
 export declare function parseUntaggedScenarios(source: string): string[];
-/**
- * The one word a CONVERTED check's scenario carries — the axis, and nothing about the subject.
- *
- * It is a literal rather than a registered tag because it names no characteristic: `checkTags` is
- * the answer to "which words are checks here", and this word is the answer to "which axis is this
- * scenario on", which is the same question `unit` and `integration` answer for the other axis. A
- * target does not get to spell it differently for the reason nobody spells `@unit` differently.
- */
 export declare const FITNESS_AXIS_TAG = "fitness";
-/**
- * The scenarios ON the fitness axis that no configured row NAMES (@SCN-LNT-020) — a corpus that has
- * half-converted a check: the tag moved and the row was never written.
- *
- * IT RAISES NOTHING AND THAT IS NOT NEGOTIABLE. Such a scenario has said which axis it is on and
- * then said nothing about what it asserts; there is no characteristic to raise an obligation FOR,
- * and reaching for the nearest word is the near-match courtesy the portfolio roster already
- * refuses. So `convertedFitnessObligationsOf` above answers the empty list, and this reads the same
- * two facts — the axis tag, and the row's absence — to say WHO.
- *
- * THE RUN ALREADY REDS ON IT, through no rule of this function's. A converted check's scenario
- * carries the axis tag and its `@SCN` and nothing else, so a scenario no row names reconciles to
- * zero rows on BOTH sides and is out of balance through the degenerate `both-missing` item — canon's
- * row for exactly this profile (Scenario Exists, Evidence Obligation None, Evidence Observation
- * None). No outcome is minted here, and none is needed.
- *
- * WHAT IS ADDED IS THE SENTENCE. That degenerate item cannot say WHY: its own gloss is about a
- * scenario carrying no `@SCN`, and this one carries one. So the run NAMES these, count and id, where
- * it already names the other corpus-shape faults — facts only, no prescribed cure, and the reader
- * is left with the one remedy there is, which is to write the row.
- *
- * IT READS THE WALK IT IS HANDED rather than taking a source of its own, and it reads the same
- * `FITNESS_AXIS_TAG` and the same registry the obligation rule reads. A second walk would be free to
- * disagree about which scenario it is looking at, and a corpus naming one scenario while the rule
- * raised nothing for another is precisely the disagreement `parseTaggedScenarios` was extracted to
- * foreclose.
- *
- * NAMED ONCE however many of a scenario's effective tags name the axis (@SCN-LDG-020) — naming it
- * twice would put one remedy on the report twice and make the count say there are two
- * half-converted checks where there is one.
- */
-export declare function unconfiguredFitnessScenarios(scenarios: readonly TaggedScenario[], fitnessChecks: FitnessCheckIndex): string[];
-/**
- * THE CONFIGURED ROWS THE CORPUS CARRIES NO SCENARIO FOR (3F-3472, @SCN-LNT-027) — the mirror of
- * `unconfiguredFitnessScenarios` directly above, in MANIFEST order.
- *
- * THE RUN DOES NOT ALREADY RED ON IT, WHICH IS THE WHOLE DIFFERENCE BETWEEN THE TWO. Its mirror
- * adds only a sentence, because a scenario no row names already reconciles to zero rows on both
- * sides and is out of balance through the degenerate item. A row no scenario names raised NOTHING:
- * the obligations travel with the scenarios, so a row with no scenario contributed a characteristic
- * nobody asked for and the run read balanced over a check that was declared and never specified.
- * `double-entry-manifesto.md` names that shape exactly — a ledger catches a credit that never
- * arrived and is blind to a debit that was never raised.
- *
- * IT READS THE WALK IT IS HANDED, for its mirror's reason: a second walk would be free to disagree
- * about which scenarios the corpus holds, and a row raised against a corpus the obligations were
- * not taken from is the phantom-row fault (@SCN-LNT-009) reached from the manifest side.
- *
- * EVERY `@SCN`-CARRYING SCENARIO COUNTS, NOT THE `@fitness` ONES ALONE. The claim is that the
- * corpus carries no scenario for the row — so a scenario carrying the row's code and saying nothing
- * about the fitness axis is still a scenario somebody wrote under that code, and minting a debit
- * beside it would report a check nobody has specified where one has been started.
- */
-export declare function unspecifiedFitnessRows(scenarios: readonly TaggedScenario[], fitnessChecks: FitnessCheckIndex): UnspecifiedFitnessRow[];
-/**
- * One `@SCN`-carrying scenario as the corpus READS it, before any obligation rule is applied:
- * its id and its EFFECTIVE tag set (its own tags, then everything it inherits from its `Rule:`
- * and `Feature:`).
- *
- * Extracted so a second corpus reader cannot grow a second tag-inheritance walk. That walk is
- * where both of `parseScenarios`'s historical false-greens lived — the UNDER-READ (a hoisted
- * tier tag invisible, so its obligation was never raised) and the OVER-READ (a tag block above a
- * `Rule:` emitted as a scenario). A reader that re-derived "which tags does this scenario carry"
- * would be free to reproduce either one alone, silently, exactly as the retired hand-rolled scan
- * did beside cucumber's own parse.
- */
 export interface TaggedScenario {
-    /** The bare scenario id, e.g. `SCN-LDG-001` (no leading @). */
-    scnId: string;
-    /** The scenario's OWN tags first, then its inherited ones — bare, no leading @. */
-    tags: readonly string[];
-    /**
-     * The scenario's EXTENT in the source — 1-based and INCLUSIVE, so `lines.slice(startLine - 1,
-     * endLine)` is exactly this scenario's text (@SCN-SSM-010, 3F-3044). It rides on this walk for the
-     * reason the walk was extracted at all, sharpened by what an extent is FOR: a second pass over the
-     * same file would be free to disagree with this one about which scenario it is looking at, and the
-     * caller that wants an extent is asking which scenario some text belongs to — so a disagreeing
-     * second pass is precisely how that question gets the neighbour's answer.
-     *
-     * `startLine` is the lesser of the scenario's first OWN tag line and its keyword line — an
-     * inherited `Rule:`/`Feature:` tag is not part of this scenario's text. `endLine` is the line
-     * before the next block starts (a scenario, a `Rule:` — or its first tag line — a `Background:`,
-     * or EOF), TRIMMED BACK over trailing blank and comment lines.
-     *
-     * The trim is load-bearing rather than tidiness: without it a blank line or a comment sitting
-     * between two scenarios belongs to the preceding one, and an edit there reads as a change to a
-     * scenario it is not part of — neighbour-inheritance rebuilt at a smaller scale, which is the one
-     * outcome @SCN-SSM-010 rules out.
-     *
-     * Derived from AST locations rather than from step positions, so docstrings, data tables and
-     * `Examples:` blocks are covered with no special case.
-     */
-    startLine: number;
-    /** The last line of this scenario's text — see `startLine`. 1-based, inclusive. */
-    endLine: number;
+    readonly scnId: string;
+    readonly tags: readonly string[];
+    readonly name: string;
 }
-/**
- * Read every `@SCN`-carrying scenario with its EFFECTIVE tags — the corpus walk `parseScenarios`
- * is built on, and the same walk any other whole-corpus tag question is answered from.
- *
- * The obligation rule is deliberately NOT applied here: what a scenario TAGS and what it OWES are
- * different questions, and the second is `obligationsFromTags`'. Keeping them apart is what lets
- * the citation seam ask the first without inheriting a reading of the second.
- *
- * WHY THE WALK IS THE AST'S AND NOT A SCAN'S. This was a hand-rolled TAG-LINE SCAN that saw only
- * the contiguous tag block directly above a `Scenario:`. Gherkin does not work that way — a
- * scenario INHERITS the tags of its `Feature:` and of any enclosing `Rule:`. Two bugs followed,
- * and both were false-greens:
- *
- *   UNDER-READ. An evidence tier hoisted to the Feature/Rule line — idiomatic, valid Gherkin,
- *   exactly what an author does with a tier shared by every scenario beneath — was INVISIBLE. The
- *   obligation was never RAISED, so its missing evidence could never reconcile `missing`, and the
- *   run read BALANCED (exit 0) while cucumber named a tier nothing proved. Unlike the corrupt-
- *   file false-green (3F-1767), this one fires on WELL-WRITTEN files — which makes it likelier.
- *
- *   OVER-READ. Any non-tag line flushed the accumulated block, so a tag block above a `Rule:` was
- *   emitted AS IF it were a scenario. The corpus did not merely miss scenarios — it INVENTED them.
- *
- * EVERY tag inherits, `@SCN` included: parity with cucumber is the goal, and excluding one would
- * invent a rule cucumber does not have. A hoisted `@SCN` therefore gives every scenario beneath it
- * the same id — a corpus-authoring fault, but a VISIBLE one (whether it should red is a deferred
- * policy question, 3F-1774's sibling).
- *
- * An UNPARSEABLE source THROWS, from `parseFeatureDocument` — it never yields an empty corpus, for
- * the reason recorded there.
- */
 export declare function parseTaggedScenarios(source: string): TaggedScenario[];
-/**
- * Parse the SCENARIO CORPUS — the ledger's DEBIT side — from the REAL Gherkin AST (@SCN-LDG-020,
- * 3F-1775), the same parser cucumber uses. So the scenarios spec-controller reconciles carry
- * EXACTLY the tags cucumber gives them: one reading of the file, not two.
- *
- * The corpus walk is `parseTaggedScenarios`'; this is the OBLIGATION rule applied over it. An
- * unparseable source still THROWS from the walk rather than yielding an empty corpus.
- *
- * `checkTags` — the registry's bare check tags (@SCN-LNT-006) — is ADDITIVE and defaults to none, so
- * `parseScenarios` keeps its place on the v1 barrel and every existing caller
- * reads exactly the corpus it read before. A target that has registered nothing raises no fitness
- * obligations, which is what lets the bare-tag reading land ahead of the corpus sweep that uses it.
- *
- * `fitnessChecks` — the target's CONFIGURED ROWS (@SCN-LNT-018) — is trailing and optional for the
- * same reason, and carries the scenario's own `scnId` into the obligation rule: a converted check's
- * characteristic is keyed by the row it is owed on, so the rule cannot be applied to a tag set
- * alone. Empty by default, so a target that has converted nothing raises nothing on this route.
- */
-export declare function parseScenarios(source: string, deferralTags?: readonly string[], checkTags?: readonly string[], fitnessChecks?: FitnessCheckIndex): Scenario[];
+export declare function parseScenarios(source: string, deferralTags?: readonly string[]): Scenario[];
 //# sourceMappingURL=scenarios.d.ts.map

package/dist/parse/scenarios.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"scenarios.d.ts","sourceRoot":"","sources":["../../src/parse/scenarios.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAKH,OAAO,KAAK,EAAE,QAAQ,EAAsB,YAAY,EAAuB,MAAM,aAAa,CAAC;AACnG,OAAO,KAAK,EAAE,iBAAiB,EAAE,qBAAqB,EAAE,MAAM,4BAA4B,CAAC;AAoB3F;;;;;GAKG;AACH,wBAAgB,mBAAmB,CAAC,GAAG,EAAE,MAAM,GAAG,YAAY,GAAG,IAAI,CAEpE;AAED;;;;;;;;;GASG;AACH,eAAO,MAAM,0BAA0B,EAAE,SAAS,MAAM,EAEvD,CAAC;AASF;;;;GAIG;AACH,eAAO,MAAM,0BAA0B,EAAE,SAAS,MAAM,EAAsC,CAAC;AAiB/F;;;;;;;GAOG;AACH,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAE1D;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,MAAM,EAAE,CAe1D;AAYD;;;;;;;GAOG;AACH,wBAAgB,sBAAsB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,EAAE,CAkB/D;AA6DD;;;;;;;GAOG;AACH,eAAO,MAAM,gBAAgB,YAAY,CAAC;AAwC1C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,wBAAgB,4BAA4B,CAC1C,SAAS,EAAE,SAAS,cAAc,EAAE,EACpC,aAAa,EAAE,iBAAiB,GAC/B,MAAM,EAAE,CAQV;AAED;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,sBAAsB,CACpC,SAAS,EAAE,SAAS,cAAc,EAAE,EACpC,aAAa,EAAE,iBAAiB,GAC/B,qBAAqB,EAAE,CAQzB;AAsED;;;;;;;;;;;GAWG;AACH,MAAM,WAAW,cAAc;IAC7B,+DAA+D;IAC/D,KAAK,EAAE,MAAM,CAAC;IACd,mFAAmF;IACnF,IAAI,EAAE,SAAS,MAAM,EAAE,CAAC;IACxB;;;;;;;;;;;;;;;;;;;;OAoBG;IACH,SAAS,EAAE,MAAM,CAAC;IAClB,mFAAmF;IACnF,OAAO,EAAE,MAAM,CAAC;CACjB;AAkFD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,cAAc,EAAE,CA0CrE;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,cAAc,CAC5B,MAAM,EAAE,MAAM,EACd,YAAY,GAAE,SAAS,MAAM,EAAO,EACpC,SAAS,GAAE,SAAS,MAAM,EAAO,EACjC,aAAa,GAAE,iBAA6B,GAC3C,QAAQ,EAAE,CAWZ"}
+{"version":3,"file":"scenarios.d.ts","sourceRoot":"","sources":["../../src/parse/scenarios.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,QAAQ,EAAsB,YAAY,EAAuB,MAAM,aAAa,CAAC;AAEnG,eAAO,MAAM,QAAQ,QAAmC,CAAC;AAUzD,wBAAgB,mBAAmB,CAAC,GAAG,EAAE,MAAM,GAAG,YAAY,GAAG,IAAI,CAEpE;AAiBD,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAE1D;AAKD,wBAAgB,sBAAsB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,EAAE,CAiB/D;AAED,eAAO,MAAM,gBAAgB,YAAY,CAAC;AAkC1C,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,IAAI,EAAE,SAAS,MAAM,EAAE,CAAC;IACjC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AAYD,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,cAAc,EAAE,CA4BrE;AAED,wBAAgB,cAAc,CAC5B,MAAM,EAAE,MAAM,EACd,YAAY,GAAE,SAAS,MAAM,EAAO,GACnC,QAAQ,EAAE,CAKZ"}