openpinescript 0.0.0-stage → 0.1.1

package/dist/types/runtime/v1/stdlib/matrix.d.ts

@@ -0,0 +1,201 @@
+/**
+ * Pine Script matrices — the `matrix.*` namespace. v5, May 2022.
+ *
+ * ── Representation ──────────────────────────────────────────────────────────
+ *
+ * An array of row arrays, unwrapped, exactly as arrays and maps are (see
+ * ./arrays.ts for why there is no wrapper class). A matrix is therefore also a
+ * valid Pine ARRAY as far as `array.size` is concerned, which is a genuine
+ * looseness: Pine's type checker keeps them apart at compile time and this
+ * engine does not model element types at all. The alternative — a tagged
+ * wrapper — would have to be unwrapped at every boundary in the runtime for a
+ * check no script can trigger without already being rejected by TradingView.
+ *
+ * Rectangularity is an INVARIANT, not an assumption: every mutator that could
+ * break it (add_row, add_col, set) validates first, because a ragged matrix
+ * produces plausible numbers from `mult` and `det` rather than an error.
+ *
+ * ── What is deliberately absent ─────────────────────────────────────────────
+ *
+ * `matrix.eigenvalues` and `matrix.eigenvectors`. Both need an iterative
+ * eigendecomposition, and for a general (non-symmetric) matrix the eigenvalues
+ * can be complex — which Pine's `array<float>` return type cannot represent, so
+ * TradingView must be doing something the docs do not state. Guessing at it
+ * would produce numbers that look right and are not.
+ *
+ * An absent name is refused by the transpiler with "not available"; a present
+ * one that is subtly wrong is not refused at all. `pinv` IS here, because its
+ * restriction is statable — see the note on it.
+ *
+ * v5-only, which this file does not enforce: the registry split in ./index.ts
+ * keeps the namespace out of the v1–v4 views.
+ */
+import type { Context } from "../context.js";
+type Matrix = any[][];
+/**
+ * The property that marks an array as a MATRIX.
+ *
+ * A matrix is an array of arrays, which is also a perfectly good Pine array, so
+ * a value cannot answer "am I a matrix?" from its shape alone. v5's method-call
+ * syntax makes that answerable-or-not the difference between `m.get(r, c)`
+ * reaching `matrix.get` and reaching `array.get` — see `Context.builtinMethod`.
+ *
+ * NON-ENUMERABLE, and a Symbol rather than a string key, so a tagged matrix is
+ * indistinguishable from a plain array to everything else: `JSON.stringify`,
+ * spread, `Object.keys`, and the array functions in ./arrays.ts all behave
+ * exactly as they did before.
+ */
+export declare const MATRIX_TAG: unique symbol;
+export declare const matrix: {
+    /**
+     * `matrix.new<type>(rows, columns, initial_value)`.
+     *
+     * The type argument is parsed by the grammar and discarded by the emitter;
+     * only the fill value distinguishes one element type from another here.
+     */
+    new: (rows?: any, columns?: any, initial_value?: any) => Matrix;
+    rows: (id: any) => number;
+    columns: (id: any) => number;
+    elements_count: (id: any) => number;
+    is_square: (id: any) => boolean;
+    is_zero: (id: any) => boolean;
+    /**
+     * The rest of the `matrix.is_*()` family.
+     *
+     * SOURCING. Each description below is the line TradingView's own
+     * `inspect()` example on the Matrices page prints when the predicate is
+     * true, which is as close to a definition as the manual gives:
+     *
+     *   is_binary        "Contains only 1s and 0s."
+     *   is_triangular    "Contains only 0s above and/or below its main diagonal."
+     *   is_diagonal      "Only has nonzero values in its main diagonal."
+     *   is_antidiagonal  "Only has nonzero values in its main antidiagonal."
+     *   is_symmetric     "Equals its transpose."
+     *   is_antisymmetric "Equals the negative of its transpose."
+     *   is_identity      "Is the identity matrix."
+     *
+     * Squareness is required wherever the property is only defined for a square
+     * matrix — a transpose of a 2x3 has a different shape and cannot equal it,
+     * and "its main diagonal" names nothing otherwise.
+     *
+     * `matrix.is_stochastic()` is deliberately NOT here. It is a real Pine
+     * built-in and appears in the same list on that page, but the manual never
+     * says which convention it means — row-stochastic, column-stochastic or
+     * doubly stochastic are three different answers for the same matrix — and a
+     * predicate that is confidently wrong is worse than one that is missing.
+     */
+    is_binary: (id: any) => boolean;
+    is_identity: (id: any) => boolean;
+    is_diagonal: (id: any) => boolean;
+    is_antidiagonal: (id: any) => boolean;
+    is_triangular: (id: any) => boolean;
+    is_symmetric: (id: any) => boolean;
+    is_antisymmetric: (id: any) => boolean;
+    get: (id: any, row: any, column: any) => any;
+    set: (id: any, row: any, column: any, value: any) => void;
+    /** A COPY of the row, as a Pine array. Mutating it must not reach back. */
+    row: (id: any, row: any) => any[];
+    col: (id: any, column: any) => any[];
+    add_row: (id: any, row?: any, array_id?: any) => void;
+    add_col: (id: any, column?: any, array_id?: any) => void;
+    remove_row: (id: any, row?: any) => any[];
+    remove_col: (id: any, column?: any) => any[];
+    swap_rows: (id: any, row1: any, row2: any) => void;
+    swap_columns: (id: any, column1: any, column2: any) => void;
+    fill: (id: any, value: any, from_row?: any, to_row?: any, from_column?: any, to_column?: any) => void;
+    /**
+     * `matrix.reverse(id)` — reverse the order of every element, in place.
+     *
+     * "This function moves the references of an m-by-n matrix id at the i-th row
+     *  and j-th column to the m - 1 - i row and n - 1 - j column."
+     *
+     * Which is the rows reversed and each row reversed. In place, like the other
+     * structural mutators, and returning nothing.
+     */
+    reverse: (id: any) => void;
+    copy: (id: any) => Matrix;
+    transpose: (id: any) => Matrix;
+    submatrix: (id: any, from_row?: any, to_row?: any, from_column?: any, to_column?: any) => Matrix;
+    /** Row-major reshape. The element count must be preserved exactly. */
+    reshape: (id: any, rows: any, columns: any) => Matrix;
+    concat: (id1: any, id2: any) => Matrix;
+    sum: (id1: any, id2: any) => Matrix;
+    diff: (id1: any, id2: any) => Matrix;
+    /**
+     * Matrix product, or a scalar/vector multiply.
+     *
+     * Pine overloads this three ways: matrix×matrix, matrix×array (treated as a
+     * column vector) and matrix×scalar. The overloads are distinguished by what
+     * the second argument IS, which is the only information available at run
+     * time here — the emitter does not track types.
+     */
+    mult: (id1: any, id2: any) => any;
+    /**
+     * `matrix.pow(id, power)` — a square matrix multiplied by itself `power`
+     * times; the identity at 0. By repeated squaring.
+     */
+    pow: (id: any, power: any) => Matrix;
+    /**
+     * `matrix.eigenvectors(id)` — a matrix whose COLUMNS are the eigenvectors,
+     * in the order `eigenvalues` returns their values. The accumulated QR
+     * rotations, which are the eigenvectors of a symmetric matrix exactly and
+     * the Schur vectors of any other.
+     */
+    eigenvectors: (id: any) => Matrix;
+    /**
+     * `matrix.eigenvalues(id)` — a square matrix's eigenvalues, largest first.
+     * By the unshifted QR algorithm, which converges to the real eigenvalues;
+     * a pair of complex ones has no real answer and stays as the 2x2 block's
+     * diagonal.
+     */
+    eigenvalues: (id: any) => number[];
+    /**
+     * Determinant by Gaussian elimination with partial pivoting.
+     *
+     * Not cofactor expansion: that is O(n!) and loses to rounding well before
+     * it loses to time. Partial pivoting is what keeps the result usable when a
+     * leading element is near zero, which is the common case for a matrix built
+     * from price data.
+     */
+    det: (id: any) => number;
+    /** Inverse by Gauss-Jordan. `na`-filled when the matrix is singular. */
+    inv: (id: any) => Matrix;
+    /**
+     * Kronecker product. Exact — no tolerance, no iteration.
+     *
+     * `a` is `m×n` and `b` is `p×q`, so the result is `mp×nq`: every element of
+     * `a` is replaced by that element times the whole of `b`.
+     */
+    kron: (id1: any, id2: any) => Matrix;
+    /**
+     * Rank — the number of linearly independent rows.
+     *
+     * Row echelon form with partial pivoting. A pivot counts as zero below a
+     * tolerance scaled to the matrix's largest element, because a rank computed
+     * against an absolute epsilon is a rank that depends on the units the
+     * prices are quoted in.
+     */
+    rank: (id: any) => number;
+    /**
+     * Moore-Penrose pseudo-inverse, for a FULL-RANK matrix.
+     *
+     * Computed from the normal equations — `(AᵀA)⁻¹Aᵀ` when the columns are
+     * independent, `Aᵀ(AAᵀ)⁻¹` when the rows are — which is exact for a
+     * full-rank matrix and is the standard construction.
+     *
+     * A RANK-DEFICIENT matrix has a pseudo-inverse too, but computing it needs
+     * a singular value decomposition, and the cutoff that decides which
+     * singular values count as zero is a tolerance TradingView does not
+     * publish. Rather than pick one, this returns an `na`-filled matrix of the
+     * right shape — the same answer `inv` gives a singular matrix, so a script
+     * that checks for `na` catches both.
+     */
+    pinv: (id: any) => Matrix;
+    trace: (id: any) => number;
+    avg: (id: any) => number;
+    max: (id: any) => number;
+    min: (id: any) => number;
+    /** Sorts ROWS by the value in `column`, ascending unless told otherwise. */
+    sort: (ctx: Context, id: any, column?: any, order?: any, sort_field?: any) => void;
+};
+export {};

package/dist/types/runtime/v1/stdlib/metadata.d.ts

@@ -0,0 +1,14 @@
+export interface PineType {
+    kind: "scalar" | "series" | "tuple";
+    type?: string;
+    itemTypes?: PineType[];
+}
+export interface StdlibEntry {
+    uses_context: boolean;
+    args: string[];
+    is_getter: boolean;
+    returns: PineType;
+    is_value: boolean;
+    ref: any;
+}
+export declare function getGeneratedRegistry(): Record<string, StdlibEntry>;

package/dist/types/runtime/v1/stdlib/mtf.d.ts

@@ -0,0 +1,15 @@
+/**
+ * runtime/v1/stdlib/mtf.ts
+ * Multi-timeframe access — security() (P1).
+ *
+ * Pine: `security(symbol, resolution, expression)` evaluates `expression` on the
+ * (symbol, resolution) series and aligns the result onto the chart's bars.
+ *
+ * The transpiler passes `expression` as a deferred thunk (see emitSecurity in the
+ * visitor). We evaluate it over the supplied HTF candles inside a sub-context
+ * (ctx.evalSecurityBar rebinds the global series), advancing only through HTF bars
+ * that have already CLOSED at the current chart-bar time — never the forming HTF
+ * bar — so there is no lookahead / repaint.
+ */
+import type { Context } from "../context.js";
+export declare function security(ctx: Context, symbol: any, resolution: any, expression: () => any, gaps?: any, lookahead?: any, ignore_invalid_symbol?: any, currency?: any, calc_bars_count?: any): any;

package/dist/types/runtime/v1/stdlib/renames.d.ts

@@ -0,0 +1,117 @@
+/**
+ * The v3 → v4 rename table.
+ *
+ * ── What this is ────────────────────────────────────────────────────────────
+ *
+ * §3a of the v3→v4 migration guide is a pure alias list: v4 moved a pile of
+ * loose globals into namespaces and changed nothing about what they mean.
+ * `red` became `color.red`, `period` became `timeframe.period`, `ticker` became
+ * `syminfo.ticker`. Same value, same implementation, new spelling.
+ *
+ * So this is DATA, not code. Each entry names the v4 spelling and the v1–v3
+ * registry key it renames, and the alias inherits that key's entry wholesale —
+ * `uses_context`, `is_getter`, `args`, `returns`, `ref`. Re-implementing
+ * `timeframe.period` as a second function beside `period` would be two things
+ * to keep in step with no test that could catch them drifting.
+ *
+ * ── The bar counter is NOT here ─────────────────────────────────────────────
+ *
+ * `n` → `bar_index` is the one rename that is not an alias: v4 REMOVES `n`.
+ * Every other old spelling below is also removed at v4, but they are removed by
+ * absence from v4's registry view, which costs nothing. The bar counter needs a
+ * real poison pill because the runtime binds it directly as a series rather
+ * than through the registry — so it lives in LANGUAGE_PROFILES[4].banned.
+ *
+ * ── Source ──────────────────────────────────────────────────────────────────
+ *
+ * https://www.tradingview.com/pine-script-docs/migration-guides/to-pine-version-4/
+ * transcribed into docs/common/VERSIONS.md §3a.
+ */
+/** One rename: the v4 spelling, and where its value comes from. */
+export interface RenameSpec {
+    /** The v4 spelling, e.g. "color.red". */
+    readonly to: string;
+    /** The v1–v3 registry key it renames, e.g. "red". */
+    readonly from?: string;
+    /**
+     * A literal, for the handful of v4 constants with no reachable v1–v3
+     * spelling in this engine. Used only where `from` genuinely cannot be given.
+     */
+    readonly value?: unknown;
+}
+/**
+ * Namespaces that exist ONLY from v4, and are therefore removed from the v1–v3
+ * registry view.
+ *
+ * They live in the ordinary stdlib source files — the runtime is one
+ * implementation across versions by design — so without this list the
+ * generator would make `array.new_float` and `label.new` resolvable at v1,
+ * where TradingView reports `Undeclared identifier`.
+ *
+ * Dates, from the v4 release notes:
+ *   line, label      June 2019
+ *   array            September 2020
+ *   box, table       May 2021
+ *
+ * `xloc`, `yloc`, `extend`, `position` and `text` are the constant namespaces
+ * that only exist to parameterise the above, so they are v4-only for the same
+ * reason.
+ */
+export declare const V4_ONLY_NAMESPACES: readonly string[];
+/**
+ * FLAT names that exist only from v4 — the indicator functions TradingView
+ * added in March 2020.
+ *
+ * Separate from V4_ONLY_NAMESPACES because these are not namespaces: they are
+ * bare function names sitting in the same flat space as `sma` and `rsi`, so
+ * gating them needs an exact-name list rather than a root-prefix one.
+ *
+ * Until this existed, a //@version=3 script calling `bb()` compiled and ran
+ * here while TradingView answered
+ *
+ *     Could not find function or function reference 'bb'
+ *
+ * — a parity gap in the opposite direction from most: the engine was too
+ * permissive, not too strict. It was recorded in conformance/golden/README.md
+ * as unfixable-for-now, because gating it would have made
+ * golden/v4/harness_builtins.pine unrunnable while v4 had no pipeline. It has
+ * one now, so the gate costs nothing.
+ *
+ * The volume family — obv, pvt, nvi, pvi, accdist, iii, wad, wvad — is still
+ * absent from the registry, so there is nothing to gate for those. Each has
+ * published variants that disagree on the SEED value, and a seed guessed wrong
+ * produces a series that is the right shape and the wrong number forever;
+ * an absent name is refused instead.
+ */
+export declare const V4_ONLY_NAMES: readonly string[];
+export declare const V4_RENAMES: readonly RenameSpec[];
+/**
+ * The v1–v3 spellings v4 removes.
+ *
+ * Every `from` above, minus the names that survive v4 under their old spelling
+ * because something ELSE of that name is what moved. `line` is the clearest
+ * case: `plot.style_line` is the renamed constant, but v4 also has a `line`
+ * DRAWING type, so the word itself is very much still in the language.
+ *
+ * Removal is what makes a v4 script fail on a v3 spelling the way TradingView
+ * does, instead of silently accepting both dialects.
+ */
+export declare const V4_REMOVED: readonly string[];
+/**
+ * Pine names this engine knows about and deliberately does NOT implement.
+ *
+ * The volume family has published variants that disagree on the SEED value,
+ * and a seed guessed wrong produces a series that is the right shape and the
+ * wrong number forever — so no implementation is offered. See the note in
+ * runtime/v1/stdlib/renames.ts.
+ *
+ * They are listed here because "absent from the registry" and "not a Pine name
+ * at all" must not produce the same diagnostic. `accdist` is real Pine, so
+ * `Undeclared identifier` would be a lie; it also cannot be allowed to compile
+ * into a silent `undefined`. runtime/v1/index.ts binds each one as a poison pill that
+ * throws only when READ, which is what lets
+ * conformance/v3/corpus/cci_commodity_channel_index.pine keep running: it
+ * mentions `accdist` in a branch selected by an input, and every other branch
+ * still works.
+ */
+export declare const UNIMPLEMENTED_BUILTINS: ReadonlySet<string>;

package/dist/types/runtime/v1/stdlib/renames5.d.ts

@@ -0,0 +1,113 @@
+/**
+ * The v4 → v5 rename table.
+ *
+ * ── What this is ────────────────────────────────────────────────────────────
+ *
+ * v5 is, in bulk, one enormous renaming. §4a of the migration guide moves the
+ * entire technical-analysis library under `ta.`, the maths under `math.`, the
+ * data requests under `request.`, the ticker constructors under `ticker.` and
+ * string handling under `str.`. Nothing about what any of them MEAN changed:
+ * `sma(close, 20)` and `ta.sma(close, 20)` are the same function.
+ *
+ * So this is DATA, exactly as ./renames.ts is for v3 → v4, and it shares that
+ * file's `RenameSpec` shape. Each entry names the v5 spelling and the v4
+ * registry key it renames, and the alias inherits that key's entry wholesale —
+ * `uses_context`, `is_getter`, `args`, `returns`, `ref`. Re-implementing
+ * `ta.sma` beside `sma` would be two things to keep in step with no test that
+ * could catch them drifting.
+ *
+ * ── The source list, and the two names that are not on it ───────────────────
+ *
+ * The lists below are transcribed from docs/common/VERSIONS.md §4a,
+ * which in turn is transcribed from TradingView's v4 → v5 migration guide.
+ *
+ * `trix` is the exception: it does not appear in the guide's enumeration and is
+ * moved here anyway, because the rule the guide states is that the
+ * technical-analysis library moved to `ta.` — the enumeration is the list of
+ * members, not a set of exceptions to it.
+ *
+ * `fixnan` was treated the same way and that was WRONG. It is na HANDLING, like
+ * `na` and `nz`, and none of that family moved. The argument for moving it
+ * cited conformance/v5/golden/harness_state.pine calling `ta.fixnan` — which
+ * was circular: the generator produced that spelling from this very list.
+ * TradingView's own compiler settled it, rejecting the generated harness with
+ *
+ *     Could not find function or function reference 'ta.fixnan'
+ *
+ * so `ta.fixnan` does not resolve here either. The FLAT name is the v5
+ * spelling, and the next block keeps it.
+ *
+ * ── The bar counter is NOT here ─────────────────────────────────────────────
+ *
+ * `n` → `bar_index` happened at v4 and v5 inherits it. It is a poison pill on
+ * the language profile rather than an alias, for the reasons in ./renames.ts.
+ *
+ * ── Source ──────────────────────────────────────────────────────────────────
+ *
+ * https://www.tradingview.com/pine-script-docs/migration-guides/to-pine-version-5/
+ * transcribed into docs/common/VERSIONS.md §4.
+ */
+import type { RenameSpec } from "./renames.js";
+/**
+ * Namespaces that exist ONLY from v5, and are therefore removed from the v1–v4
+ * registry views.
+ *
+ * They live in the ordinary stdlib source files — the runtime is one
+ * implementation across versions by design — so without this list the generator
+ * would make `str.length` and `matrix.new` resolvable at v1, where TradingView
+ * reports `Undeclared identifier`.
+ *
+ * Dates, from the v5 release notes:
+ *   str, math, ta, request, ticker, log, runtime   v5 launch
+ *   matrix                                          May 2022
+ *   map                                             August 2023
+ *
+ * `ta`, `math` and `ticker` carry no generated keys of their own — every member
+ * arrives as an ALIAS — so listing them removes nothing today. They are here so
+ * that a future `ta.*` implemented directly rather than aliased is gated by
+ * default rather than by remembering to.
+ */
+export declare const V5_ONLY_NAMESPACES: readonly string[];
+/**
+ * EXACT keys that exist only from v5 — the typed input functions, and the
+ * dataset-extent variables.
+ *
+ * Separate from V5_ONLY_NAMESPACES because `input.*` is not a v5-only
+ * namespace: v4 has `input.float` as a CONSTANT and v5 has it as a FUNCTION, so
+ * gating the whole root would take v4's constants away with it. See the header
+ * of ./inputs.ts for how one runtime object serves both readings.
+ */
+export declare const V5_ONLY_NAMES: readonly string[];
+export declare const V5_RENAMES: readonly RenameSpec[];
+/**
+ * Every v4 spelling that is not writable at v5.
+ *
+ * The `from` side of every rename above, plus the outright removals. Removal is
+ * what makes a v5 script fail on `sma(close, 20)` the way TradingView does,
+ * instead of silently accepting both dialects — which is the failure mode this
+ * whole table exists to prevent.
+ */
+export declare const V5_REMOVED: readonly string[];
+/**
+ * v5 positional orders that differ from the order of this engine's
+ * parameters, mapped by NAME the way V6_POSITIONAL is for v6.
+ *
+ * `strategy.exit`: v5's reference puts `comment_profit`, `comment_loss` and
+ * `comment_trailing` between `comment` and `when`. The engine's signature keeps
+ * v4's order, where `when` follows `comment`, and appends the three — so
+ * without this a v5 call passing them by position bound the first to `when`
+ * and the second to `alert_message`.
+ */
+export declare const V5_POSITIONAL: Readonly<Record<string, readonly string[]>>;
+/**
+ * Keyword names that v5 renamed, by the name a v1-v4 script wrote, mapped to
+ * the engine's parameter. Read by Context.call when binding keywords below v5.
+ *
+ * docs/common/VERSIONS.md §4b, from the migration guide:
+ * `strategy.entry(long=)` -> `strategy.entry(direction=)`, and the same for
+ * `strategy.order`. The engine's `strategy.order` calls the parameter `dir`.
+ * Positionally nothing moved, so only keyword use needs this; before it
+ * `strategy.entry(id = "L", long = false)` dropped the direction and opened a
+ * long, or, with the argument recorded and ignored, nothing at all.
+ */
+export declare const V4_RENAMED_PARAMS: Readonly<Record<string, Readonly<Record<string, string>>>>;

package/dist/types/runtime/v1/stdlib/renames6.d.ts

@@ -0,0 +1,81 @@
+/**
+ * The v5 → v6 registry delta.
+ *
+ * ── Why there is no rename table ───────────────────────────────────────────
+ *
+ * v4 and v5 were each, in bulk, a renaming: `sma` → `ta.sma`, `red` →
+ * `color.red`. v6 renames NOTHING. Every v5 spelling is still a v6 spelling,
+ * which is why this file has no `RenameSpec[]` and why `V6_VIEW` is built with
+ * an empty rename step.
+ *
+ * What v6 does to the registry instead is:
+ *
+ *   ADD     new built-ins, from the launch notes and the two years of monthly
+ *           releases after it — V6_ONLY_NAMES / V6_ONLY_NAMESPACES below
+ *   CHANGE  the VALUE of three colour constants and one default — handled at
+ *           the point of use, not here, because the key is unchanged
+ *   REMOVE  nothing that is a NAME
+ *
+ * ── Why V6_REMOVED is empty rather than absent ─────────────────────────────
+ *
+ * The migration guide does remove things: `transp` from six plotting
+ * functions, `when` from seven strategy functions. Neither is a registry key.
+ * They are PARAMETERS, and a parameter is removed by refusing it at the call
+ * site, where the error can name the argument and the line — which is
+ * transpiler/v6/ToJsVisitor.ts.
+ *
+ * The empty array is kept, and spread, so that `V6_VIEW` reads the same as
+ * `V4_VIEW` and `V5_VIEW` and so that the question "did v6 take a name away?"
+ * has an answer in the code rather than in a reader's memory.
+ *
+ * ── Source ─────────────────────────────────────────────────────────────────
+ *
+ * https://www.tradingview.com/pine-script-docs/migration-guides/to-pine-version-6/
+ * https://www.tradingview.com/pine-script-docs/release-notes/
+ */
+/**
+ * Namespaces that exist only from v6. A member of one of these must not
+ * resolve at v1–v5, however completely it is implemented in the shared
+ * stdlib — the same gate `V5_ONLY_NAMESPACES` applies to `str.*` and
+ * `matrix.*`.
+ */
+export declare const V6_ONLY_NAMESPACES: readonly string[];
+/**
+ * Individual names that arrive at v6, for namespaces that already existed.
+ *
+ * Listed by name rather than by namespace because every one of these joins a
+ * namespace v5 already has — `request.footprint()` is new, `request.*` is not
+ * — so gating the root would take the whole namespace out of v5 with it.
+ */
+export declare const V6_ONLY_NAMES: readonly string[];
+/**
+ * The v6 POSITIONAL order of functions whose shared signature differs from it,
+ * by parameter name. Read by Context.positionalForVersion.
+ *
+ * The shared stdlib keeps one signature per function, the union of every
+ * version's, and v6 removed parameters from the middle of several — `transp`
+ * (MG §"The transp parameter is removed") and `when` (§"Removal of when
+ * parameter"). Opening a one-slot gap where each was assumed the rest already
+ * matched v6, and it did not: `fill()` has no `show_last`, and
+ * `strategy.entry`'s tenth v6 argument, `disable_alert`, landed in a broker
+ * internal. Mapping BY NAME has no such assumption: the n-th positional
+ * argument is the n-th name here, wherever the shared function keeps it, and a
+ * name the shared function lacks is dropped and recorded like any unknown
+ * argument.
+ *
+ * Names are the shared function's where they differ only in spelling — the
+ * engine's `strategy.order` calls its direction `dir`.
+ */
+export declare const V6_POSITIONAL: Readonly<Record<string, readonly string[]>>;
+/** Spellings v6 takes away. See the header: there are none. */
+export declare const V6_REMOVED: readonly string[];
+/**
+ * Parameters v6 added to functions that earlier versions already have,
+ * keyed by registry name.
+ *
+ * Not a registry key, so not a view: the FUNCTION exists at every version and
+ * only its signature grew. Context.call reads this when binding keyword
+ * arguments, and below v6 a listed name is dropped and recorded as unknown —
+ * exactly the treatment it got before it was added.
+ */
+export declare const V6_ONLY_PARAMS: Readonly<Record<string, readonly string[]>>;