@plebeiantech/lat.md 0.12.3-fork.13 → 0.12.3-fork.14

package/dist/src/lattice.d.ts

@@ -1,109 +1,14 @@
+import type { LatFrontmatter, MdLink, Ref, Section } from './lattice-model.js';
 import type { Root } from 'mdast';
-export type Section = {
-    id: string;
-    heading: string;
-    depth: number;
-    file: string;
-    filePath: string;
-    children: Section[];
-    startLine: number;
-    endLine: number;
-    firstParagraph: string;
-    /** GitHub-compatible anchor generated from the rendered heading text. */
-    githubSlug?: string;
-};
-export type Ref = {
-    target: string;
-    fromSection: string;
-    file: string;
-    line: number;
-};
-/** An ordinary markdown destination or an undefined reference-style link. */
-export type MdLink = {
-    /** Destination exactly as authored, percent-escapes and all. */
-    url: string;
-    kind: 'link' | 'image' | 'definition';
-    line: number;
-} | {
-    /** Authored label that should have a matching definition. */
-    identifier: string;
-    /** Full reference syntax exactly as authored. */
-    source: string;
-    kind: 'linkReference' | 'imageReference';
-    line: number;
-};
-/**
- * Every field this build reads out of the `lat:` mapping. Kept in one place so
- * a field added later is covered by the misplacement check without a second
- * edit — the trap this list guards against is silent, so it must not depend on
- * whoever adds the next field remembering to register it twice.
- */
-export declare const LAT_FIELDS: readonly ["require-code-mention", "mode", "require-mode", "status", "reviewed-hash", "tags"];
-/**
- * Something wrong with the frontmatter itself, carried out of the parser for a
- * caller to report. Both kinds fail OPEN if they stay quiet: a misplaced or
- * unparseable `require-code-mention` turns a validation off and `lat check`
- * then reports success on a file that is no longer being validated.
- */
-export type FrontmatterProblem = {
-    kind: 'root-level-field';
-    field: string;
-} | {
-    kind: 'parse-error';
-    message: string;
-};
-export type LatFrontmatter = {
-    /** Every key under the `lat:` mapping, parsed but not mapped to a field. */
-    raw: Record<string, unknown>;
-    requireCodeMention?: boolean;
-    /** Populated only when something is wrong; absent on a healthy document. */
-    problems?: FrontmatterProblem[];
-};
+import type { Profiler } from './profiler.js';
+export { buildFileIndex, buildSectionSlugIndex, findSections, flattenSections, resolveRef, } from './lattice-model.js';
+export type { LatFrontmatter, MdLink, Ref, ResolveResult, Section, SectionMatch, SectionSlugIndex, } from './lattice-model.js';
+export { findLatticeDir, findProjectRoot, listLatticeFiles, } from './project-discovery.js';
+export { LAT_FIELDS } from './fork/frontmatter-fields.js';
+export type { ForkFrontmatter, FrontmatterProblem, } from './fork/frontmatter-fields.js';
 export declare function parseFrontmatter(content: string): LatFrontmatter;
-export declare function findLatticeDir(from?: string): string | null;
-export declare function findProjectRoot(from?: string): string | null;
-export declare function listLatticeFiles(latticeDir: string): Promise<string[]>;
 export declare function parseSections(filePath: string, content: string, projectRoot?: string, tree?: Root): Section[];
-export declare function loadAllSections(latticeDir: string, projectRoot?: string): Promise<Section[]>;
-export declare function flattenSections(sections: Section[]): Section[];
-/**
- * Build an index mapping path suffixes to their full vault-relative paths.
- * Used by resolveRef to allow short references when a suffix is unambiguous.
- *
- * For a file like `lat.md/guides/setup`, indexes both `guides/setup` and `setup`.
- * This ensures backward-compatible short refs after the vault root moved to the
- * project root (so section IDs now include the `lat.md/` prefix).
- */
-export declare function buildFileIndex(sections: Section[]): Map<string, string[]>;
-export type SectionSlugIndex = ReadonlyMap<string, string>;
-/**
- * Map GitHub-slugged heading paths back to canonical, literal-heading ids.
- * Every path segment accepts either representation so an implicit literal h1
- * can still prefix slugged child headings during short-ref resolution.
- */
-export declare function buildSectionSlugIndex(sections: Section[]): Map<string, string>;
-export type ResolveResult = {
-    resolved: string;
-    ambiguous: string[] | null;
-    /** When ambiguous but exactly one candidate has the section, suggest it. */
-    suggested: string | null;
-};
-/**
- * Resolve a potentially short reference to its canonical full-path form.
- * If the file segment of the ref is a bare stem that uniquely maps to one
- * full path, expands it. Otherwise returns the ref unchanged.
- *
- * When ambiguous (multiple files share the stem), returns all candidates.
- * If exactly one candidate actually contains the referenced section,
- * `suggested` is set to that candidate so the caller can propose a fix.
- */
-export declare function resolveRef(target: string, sectionIds: Set<string>, fileIndex: Map<string, string[]>, slugIndex?: SectionSlugIndex): ResolveResult;
-export type SectionMatch = {
-    section: Section;
-    reason: string;
-    score?: number;
-};
-export declare function findSections(sections: Section[], query: string): SectionMatch[];
+export declare function loadAllSections(latticeDir: string, projectRoot?: string, profile?: Profiler): Promise<Section[]>;
 export declare function extractRefs(filePath: string, content: string, projectRoot?: string, tree?: Root): Ref[];
-/** Extract link destinations and undefined full/collapsed references. */
+/** Extract link destinations and undefined reference syntax. */
 export declare function extractLinks(content: string, tree?: Root): MdLink[];