@wrtnlabs/evidence 0.0.0

package/lib/structures/IEvidenceReferenceBase.d.ts

@@ -0,0 +1,107 @@
+import type { EvidenceSeverity } from "../typings/EvidenceSeverity";
+/**
+ * Shared selection and coverage policy for one referenced population.
+ *
+ * A reference creates an independent obligation within its claim. Ordinary
+ * evidence and permitted exclusions cover selected targets and their selected
+ * descendants. Unselected structural ancestors can remain addressable so authors
+ * can cite an aggregate scope without changing the required population.
+ *
+ * The optional policies tighten different parts of that obligation:
+ *
+ * 1. `noEvidenceExclude` requires positive evidence rather than non-applicability.
+ * 2. `uniqueEvidence` limits positive semantic hosts for each selected unit.
+ * 3. `singleEvidencePerSymbol` requires one selected target per claim host.
+ * 4. `requireReview` validates a paired review against current target content.
+ *
+ * Defaults are permissive. A strict reference and a permissive reference can
+ * judge the same annotation differently without changing the shared inventory.
+ * Artifact-specific interfaces add file selection and, for Markdown, checklist
+ * semantics that require every host to answer every item.
+ */
+export interface IEvidenceReferenceBase<Type extends string, SymbolKind extends string> {
+    /**
+     * Artifact discriminator selecting the reference's extraction and target rules.
+     *
+     * This can differ from the claim's artifact type. It determines supported symbol
+     * selectors and target grammar, not which host language must acknowledge them.
+     */
+    type: Type;
+    /**
+     * Base directory for file globs and local file paths.
+     *
+     * - Defaults to the directory containing evidence.config.ts; relative roots
+     *   resolve from that directory.
+     * - Accepts absolute paths, directory symlinks, and Windows junctions.
+     * - Names one directory, not a glob. Windows drive-relative paths are invalid.
+     * - Markdown citations use this root; programming citations use the citing file.
+     *   Prisma model addresses do not contain paths.
+     */
+    root?: string;
+    /**
+     * Evidence symbol kinds selected as required units.
+     *
+     * Accepts one kind or a nonempty array. Defaults by family:
+     *
+     * - Programming: type when supported; otherwise every supported kind.
+     * - Database: model.
+     * - Markdown: file, h1, h2, h3, h4.
+     * - Swagger: operation.
+     *
+     * Unselected structural ancestors remain addressable as aggregate targets.
+     */
+    symbol?: SymbolKind | SymbolKind[];
+    /**
+     * Overrides the claim's inherited diagnostic severity.
+     *
+     * Omit or use `undefined` to inherit. `"off"` disables this reference's population
+     * and obligation after validating its configuration shape.
+     */
+    severity?: EvidenceSeverity | undefined;
+    /**
+     * Refuses exclusion acknowledgements for this reference.
+     *
+     * Report refused exclusions at their declarations and leave their targets
+     * uncovered unless positive evidence acknowledges them.
+     * The same declaration may still cover another reference that allows exclusions.
+     *
+     * @default false
+     */
+    noEvidenceExclude?: boolean;
+    /**
+     * Allows at most one distinct positive claim host per evidence unit.
+     *
+     * Repeated tags, overloads, and merged declarations do not create extra hosts.
+     * Exclusions do not count; an uncited unit still fails coverage.
+     *
+     * @default false
+     */
+    uniqueEvidence?: boolean;
+    /**
+     * Require every selected claim host to cite exactly one selected evidence unit.
+     *
+     * - Hosts without tags count as zero; repeated citations to one unit count once.
+     * - Aggregate targets count every selected descendant they cover.
+     * - An empty reference population is reported as empty and evaluates no hosts.
+     *
+     * @default false
+     */
+    singleEvidencePerSymbol?: boolean;
+    /**
+     * Require a matching review with the current target content fingerprint.
+     *
+     * - Evidence needs evidenceReview; exclusions need evidenceExcludeReview.
+     *   Reviews do not provide coverage.
+     * - Reviews carry a #-prefixed fingerprint. Missing or stale reviews fail the
+     *   obligation; diagnostics provide the expected fingerprint.
+     * - Fingerprints belong to the cited unit and its structural subtree,
+     *   independently of reference selectors.
+     * - TypeScript fingerprints include nested declarations, even withdrawn ones.
+     *   Swagger uses normalized operation content; Prisma uses parsed declarations
+     *   without the documentation comments that carry reviews.
+     * - This verifies the recorded review and fingerprint, not the truth of its prose.
+     *
+     * @default false
+     */
+    requireReview?: boolean;
+}

package/lib/structures/IEvidenceReferenceBase.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceResolution.d.ts

@@ -0,0 +1,32 @@
+import type { IEvidenceUnit } from "./IEvidenceUnit";
+import type { IEvidenceWithdrawal } from "./IEvidenceWithdrawal";
+/**
+ * Exact inventory lookup within a selected population's structural scope.
+ *
+ * This lower-level result assumes the public address has already been parsed.
+ * It deduplicates aliases by semantic identity and preserves withdrawn matches.
+ * Incomplete inventory takes precedence because partial extraction cannot prove
+ * either uniqueness or absence.
+ */
+export interface IEvidenceResolution {
+    /**
+     * Visibility and uniqueness outcome of the address lookup.
+     *
+     * Missing means no matching scope was found in a complete inventory; incomplete
+     * means the available candidates cannot establish a trustworthy answer.
+     */
+    status: "resolved" | "ambiguous" | "hidden" | "missing" | "incomplete";
+    /**
+     * Visible matches, or withdrawn matches when no visible match exists.
+     *
+     * Multiple aliases of one identity produce one entry; distinct identities can
+     * remain ambiguous at the same public address.
+     */
+    units: IEvidenceUnit[];
+    /**
+     * Deduplicated withdrawal records associated with hidden matches.
+     *
+     * These identify the source annotations responsible for inherited exclusion.
+     */
+    withdrawals: IEvidenceWithdrawal[];
+}

package/lib/structures/IEvidenceResolution.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceReview.d.ts

@@ -0,0 +1,50 @@
+import type { EvidenceAcknowledgementKind } from "../typings/EvidenceAcknowledgementKind";
+import type { IEvidenceTargetStatement } from "./IEvidenceTargetStatement";
+/**
+ * A recorded review of an acknowledgement and the content of its cited scope.
+ *
+ * Graph evaluation pairs a review by semantic host, resolved target, and
+ * acknowledgement kind. Required reviews must also carry the current fingerprint
+ * of that target and its structural subtree. Matching target text alone cannot
+ * compensate for an unrelated host or the wrong review kind.
+ *
+ * Reviews remain separate from acknowledgements because they never discharge
+ * coverage. Missing fingerprints are retained for diagnostics, and semantic edits
+ * can expire a previously valid review. The checker validates this record and
+ * content token; it does not prove the prose true or establish who reviewed it.
+ *
+ * @example
+ * // @evidence ../api.ts#send Exercises successful delivery.
+ * // @evidenceReview ../api.ts#send #<current-fingerprint> Checked delivery errors.
+ * // The review supplements the evidence statement instead of replacing it.
+ */
+export interface IEvidenceReview extends IEvidenceTargetStatement {
+    /**
+     * Identity of this parsed review statement.
+     *
+     * Resolution records join to the review table through this ID. It is separate
+     * from the acknowledgement being reviewed, even when host and target coincide.
+     */
+    id: string;
+    /**
+     * Acknowledgement kind validated by this review.
+     *
+     * Positive evidence needs a positive review; exclusions need exclusion reviews.
+     * The wrong kind produces a pairing finding rather than satisfying review policy.
+     */
+    reviews: EvidenceAcknowledgementKind;
+    /**
+     * Content fingerprint recorded by the review author, when supplied.
+     *
+     * Omission remains a parseable review state. A reference requiring review reports
+     * a missing token or a stale token against the current target fingerprint.
+     */
+    fingerprint?: string;
+    /**
+     * Nonempty prose describing the recorded verification.
+     *
+     * Tag parsing requires explanatory text. Graph policy checks pairing and content
+     * freshness without judging whether the described verification actually occurred.
+     */
+    description: string;
+}

package/lib/structures/IEvidenceReview.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceAddress.d.ts

@@ -0,0 +1,39 @@
+/**
+ * Logical spelling through which a physical source participates in analysis.
+ *
+ * A physical file can have several symlink or hard-link addresses. Keeping each
+ * spelling preserves population selection and relative citation origins without
+ * reading or counting the physical source repeatedly. Dependency-only addresses
+ * support extraction but do not automatically join the selected population.
+ */
+export interface IEvidenceSourceAddress {
+    /**
+     * Absolute logical path retaining the selected link spelling.
+     *
+     * This can differ from the physical path used to deduplicate source reads.
+     */
+    absolute: string;
+    /**
+     * Case-sensitive, slash-separated path relative to the population root.
+     *
+     * Population globs and root-relative artifact targets use this spelling rather
+     * than the file's physical path.
+     */
+    relative: string;
+    /**
+     * Display path expressed from the configuration directory.
+     *
+     * Across volumes it remains absolute because a relative filesystem path cannot
+     * represent that relationship.
+     */
+    display: string;
+    /**
+     * Whether the address belongs to the selected source population.
+     *
+     * False marks support files loaded to analyze a selected dependency. Omission
+     * means selected, preserving the ordinary discovery record's default.
+     *
+     * @default true
+     */
+    selected?: boolean;
+}

package/lib/structures/IEvidenceSourceAddress.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceDependency.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Filesystem location needed to observe source changes or recovery.
+ *
+ * A dependency can name a read file, a directory whose topology affects globs,
+ * or a currently missing path. Watch retains these records after failures so a
+ * newly created or repaired input can trigger evaluation without editing a file
+ * that was already present in the successful snapshot.
+ */
+export interface IEvidenceSourceDependency {
+    /**
+     * Absolute logical or physical path that can invalidate the result.
+     *
+     * The path need not exist. Dropping missing dependencies would prevent watch
+     * from observing their later creation or restoration.
+     */
+    path: string;
+    /**
+     * Whether observation includes descendants of the recorded path.
+     *
+     * False denotes an exact dependency. Recursive directory observation detects
+     * topology changes that can add selected files beyond the known source list.
+     */
+    recursive: boolean;
+}

package/lib/structures/IEvidenceSourceDependency.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceDiagnostic.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Filesystem discovery failure retained in a source snapshot.
+ *
+ * A failed read, unstable source, or unresolved path boundary prevents the loader
+ * from certifying a complete population. Adapters can preserve this failure when
+ * producing graph diagnostics instead of silently omitting the affected file.
+ */
+export interface IEvidenceSourceDiagnostic {
+    /**
+     * Stable category of the failed discovery operation.
+     *
+     * Callers can distinguish access, spelling, encoding, and snapshot-consistency
+     * failures without interpreting platform-specific message text.
+     */
+    code: "root-unreadable" | "path-unreadable" | "case-mismatch" | "symlink-cycle" | "not-file" | "invalid-encoding" | "source-changed";
+    /**
+     * Absolute logical path involved in the failure.
+     *
+     * This retains the author-visible address even when its physical target could
+     * not be read or resolved.
+     */
+    path: string;
+    /**
+     * Explanation of the cause and affected discovery operation.
+     *
+     * Concrete filesystem details complement the stable category when diagnosing
+     * permission failures, changing files, or invalid source contents.
+     */
+    message: string;
+}

package/lib/structures/IEvidenceSourceDiagnostic.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceFile.d.ts

@@ -0,0 +1,50 @@
+import type { IEvidenceSourceAddress } from "./IEvidenceSourceAddress";
+/**
+ * Captured UTF-8 file content with every selected logical address preserved.
+ *
+ * Discovery deduplicates filesystem identity while retaining aliases, so linked
+ * paths do not create duplicate source populations or disappear from citation
+ * lookup. Hard links can share an ID even when their canonical paths differ.
+ * Adapters read `content` rather than reopening those paths after discovery.
+ *
+ * The source digest covers original bytes for change detection. Review
+ * fingerprints instead describe semantic units and exclude accepted annotation
+ * ranges; substituting a whole-file digest would give them the wrong boundary.
+ */
+export interface IEvidenceSourceFile {
+    /**
+     * Filesystem identity used to deduplicate the captured source.
+     *
+     * Discovery uses device/inode identity where available and falls back to realpath.
+     * Logical aliases and hard links can therefore share this ID without losing paths.
+     */
+    id: string;
+    /**
+     * Canonical path used to read this file's bytes.
+     *
+     * This path anchors physical declaration sites. Hard-linked paths may share the
+     * same source ID, while logical citation paths remain in `addresses`.
+     */
+    physicalPath: string;
+    /**
+     * Decoded source text with its original line endings and byte-order mark.
+     *
+     * Declaration ranges and documentation mappings refer to this exact string.
+     * Normalize only where a later semantic digest requires it, not before extraction.
+     */
+    content: string;
+    /**
+     * SHA-256 of the original file bytes for cache invalidation.
+     *
+     * This detects source changes, including edits irrelevant to one unit's semantic
+     * fingerprint. Review tokens are constructed separately from unit content.
+     */
+    digest: string;
+    /**
+     * Logical addresses retained in deterministic path order.
+     *
+     * Physical deduplication must preserve each selected alias for target lookup.
+     * Address metadata distinguishes selection spelling from the canonical read path.
+     */
+    addresses: IEvidenceSourceAddress[];
+}

package/lib/structures/IEvidenceSourceFile.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceLocation.d.ts

@@ -0,0 +1,23 @@
+import type { IEvidenceSourceRange } from "./IEvidenceSourceRange";
+/**
+ * Source coordinate suitable for both declarations and file-level failures.
+ *
+ * Extraction can identify a file even when reading or parsing it fails before a
+ * span exists. The optional range preserves that distinction instead of inventing
+ * a line number for diagnostics without a concrete source position.
+ */
+export interface IEvidenceSourceLocation {
+    /**
+     * File associated with the declaration or diagnostic.
+     *
+     * Reporters can display this path even when no source range is available.
+     */
+    file: string;
+    /**
+     * Source span narrowing the location within the file.
+     *
+     * Omission denotes file-level context; when present, its start supplies the
+     * line and column displayed by text reporters.
+     */
+    range?: IEvidenceSourceRange;
+}

package/lib/structures/IEvidenceSourceLocation.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourcePosition.d.ts

@@ -0,0 +1,36 @@
+/**
+ * A position measured in the original UTF-16 source string.
+ *
+ * Offsets follow JavaScript string indexing, while line and column numbers are
+ * one-based for diagnostics. No newline normalization occurs: CRLF retains both
+ * code units, and a supplementary Unicode character occupies two code units.
+ * Adapters and decoded-documentation mappers must return this coordinate system
+ * rather than byte offsets or visual editor columns.
+ *
+ * @example
+ * // In "A😀\r\nB", B begins at offset 5, line 2, column 1.
+ * // The emoji contributes two code units and the CRLF contributes two more.
+ */
+export interface IEvidenceSourcePosition {
+    /**
+     * Zero-based UTF-16 offset into the captured source string.
+     *
+     * This is suitable for `String.slice` without byte conversion. Surrogate pairs
+     * occupy two positions, so a code-point count cannot substitute for the offset.
+     */
+    offset: number;
+    /**
+     * One-based line number in the original source.
+     *
+     * LF advances the line, including the LF in CRLF. Preserving original line
+     * endings keeps the offset and diagnostic coordinates on the same text.
+     */
+    line: number;
+    /**
+     * One-based UTF-16 column within the line.
+     *
+     * CR and each surrogate code unit occupy one column. This records string
+     * position, not rendered width or a Unicode code-point column.
+     */
+    column: number;
+}

package/lib/structures/IEvidenceSourcePosition.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceRange.d.ts

@@ -0,0 +1,28 @@
+import type { IEvidenceSourcePosition } from "./IEvidenceSourcePosition";
+/**
+ * A half-open span in the original captured source string.
+ *
+ * The inclusive start and exclusive end match JavaScript slicing. Both positions
+ * retain diagnostic coordinates in the same unnormalized UTF-16 text, so adapters
+ * can expose serializable locations without retaining their parser nodes.
+ *
+ * @example
+ * const fragment: string = content.slice(range.start.offset, range.end.offset);
+ * // Equal offsets describe an empty span, such as an inserted missing token.
+ */
+export interface IEvidenceSourceRange {
+    /**
+     * Inclusive first position belonging to the span.
+     *
+     * Use its offset as the first argument to `String.slice`; line and column
+     * provide the corresponding original-source diagnostic location.
+     */
+    start: IEvidenceSourcePosition;
+    /**
+     * Exclusive position immediately after the span.
+     *
+     * Use its offset directly as the slicing end. Adding one would include an
+     * unrelated character and mishandle zero-width ranges.
+     */
+    end: IEvidenceSourcePosition;
+}

package/lib/structures/IEvidenceSourceRange.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceRoot.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Configured, logical, and physical locations of a source population's root.
+ *
+ * Relative roots resolve from the configuration directory, while directory
+ * symlinks and Windows junctions can redirect the physical scan. These spellings
+ * remain separate so discovery can enforce boundaries and diagnostics can still
+ * explain the path the user configured, including roots that cannot be read.
+ */
+export interface IEvidenceSourceRoot {
+    /**
+     * Root spelling authored in configuration, defaulting to a dot.
+     *
+     * Preserve this value for explanations rather than replacing it with the
+     * resolved absolute or physical path.
+     */
+    declared: string;
+    /**
+     * Absolute logical directory before following filesystem links.
+     *
+     * Relative configuration roots are anchored here. This may differ from the
+     * physical scan directory when a symlink or junction redirects the root.
+     */
+    absolute: string;
+    /**
+     * Canonical directory used for scanning when discovery resolves the root.
+     *
+     * Omission records that no directory could be resolved. The logical path remains
+     * available for diagnostics and watch recovery of a missing or repaired root.
+     */
+    physical?: string;
+    /**
+     * User-facing root path relative to the configuration directory where possible.
+     *
+     * Cross-volume paths remain absolute. This presentation choice does not replace
+     * logical or physical identity during source discovery.
+     */
+    display: string;
+}

package/lib/structures/IEvidenceSourceRoot.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceSelection.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Filesystem selection shared by claim and reference discovery.
+ *
+ * The source loader resolves the root from the configuration directory and
+ * applies ordered patterns within that logical root. Artifact-specific symbol
+ * selection happens later, after these files have been read and extracted.
+ */
+export interface IEvidenceSourceSelection {
+    /**
+     * Population directory resolved from the configuration file's directory.
+     *
+     * Omission uses the configuration directory itself, independently of the
+     * process working directory at extraction time.
+     */
+    root?: string;
+    /**
+     * Ordered root-relative inclusion and exclusion patterns.
+     *
+     * These follow the shared claim files contract; their order controls which
+     * logical addresses remain selected before artifact extraction.
+     */
+    files: string[];
+}

package/lib/structures/IEvidenceSourceSelection.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSourceSnapshot.d.ts

@@ -0,0 +1,53 @@
+import type { IEvidenceSourceDependency } from "./IEvidenceSourceDependency";
+import type { IEvidenceSourceDiagnostic } from "./IEvidenceSourceDiagnostic";
+import type { IEvidenceSourceFile } from "./IEvidenceSourceFile";
+import type { IEvidenceSourceRoot } from "./IEvidenceSourceRoot";
+/**
+ * Captured discovery result for one configured source selection.
+ *
+ * The loader resolves a root, applies ordered globs, reads files, and deduplicates
+ * physical identities while preserving logical addresses. Adapters consume this
+ * snapshot so declaration positions and content come from the same source revision.
+ *
+ * Dependencies include locations needed to observe new files and repairs.
+ * Diagnostics and completeness distinguish an empty successful selection from a
+ * failed discovery that happened to return no files; adapters must retain that
+ * distinction instead of treating either state as a passing empty inventory.
+ */
+export interface IEvidenceSourceSnapshot {
+    /**
+     * Configured and resolved root shared by the population's logical addresses.
+     *
+     * It retains the authored spelling even when physical directory resolution
+     * fails, keeping diagnostics and recovery dependencies attributable.
+     */
+    root: IEvidenceSourceRoot;
+    /**
+     * Captured physical files ordered by their first selected address.
+     *
+     * The list can be partial after failure. Inspect `complete` before treating it
+     * as the full source population, even when some files were loaded successfully.
+     */
+    files: IEvidenceSourceFile[];
+    /**
+     * Existing and missing filesystem locations needed for invalidation.
+     *
+     * Directories and absent paths preserve discovery topology, allowing watch to
+     * observe newly selected files and recovery from failed reads.
+     */
+    dependencies: IEvidenceSourceDependency[];
+    /**
+     * Discovery findings retained alongside any successfully captured files.
+     *
+     * The list remains meaningful when no file could be read. Adapters translate
+     * these findings into inventory diagnostics rather than discarding them.
+     */
+    diagnostics: IEvidenceSourceDiagnostic[];
+    /**
+     * Whether discovery completed without failures.
+     *
+     * An empty successful glob selection remains complete. Missing roots, unreadable
+     * files, or other discovery failures cannot be concealed by an empty file list.
+     */
+    complete: boolean;
+}

package/lib/structures/IEvidenceSourceSnapshot.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/lib/structures/IEvidenceSupportedDatabaseLanguage.d.ts

@@ -0,0 +1,36 @@
+import type { EvidenceDatabaseType } from "../typings/EvidenceDatabaseType";
+import type { IEvidenceDatabaseLanguageAdapter } from "./IEvidenceDatabaseLanguageAdapter";
+import type { IEvidenceLanguageGrammar } from "./IEvidenceLanguageGrammar";
+/**
+ * Database capability entry guaranteed to have a certified schema adapter.
+ *
+ * Supported-database queries use this narrower shape after excluding grammar-only
+ * entries. The required adapter contract lets callers inspect extraction and
+ * target-address boundaries without another availability check.
+ */
+export interface IEvidenceSupportedDatabaseLanguage {
+    /**
+     * Configuration discriminator selecting this database family.
+     *
+     * Claims and references use this value to choose schema extraction.
+     */
+    type: EvidenceDatabaseType;
+    /**
+     * Display label for the supported schema language.
+     *
+     * Reports retain the separate type discriminator for configuration use.
+     */
+    name: string;
+    /**
+     * Grammar variants and logical filename rules associated with the adapter.
+     *
+     * These describe syntax selection without implying that metadata inspection loads WASM.
+     */
+    grammars: IEvidenceLanguageGrammar[];
+    /**
+     * Guaranteed schema extraction and documentation-host contract.
+     *
+     * This includes selectors, address policy, and explicit unsupported capabilities.
+     */
+    adapter: IEvidenceDatabaseLanguageAdapter;
+}

package/lib/structures/IEvidenceSupportedDatabaseLanguage.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });