@popoverai/dotrequirements 0.27.4 → 0.29.0

package/dist/sync/segment.js

@@ -0,0 +1,76 @@
+/**
+ * Segment a document body into an ordered sequence of units — prose passages
+ * and requirement blocks, interleaved (the comparator's structural input).
+ *
+ * A requirement's identity is its key; a prose passage's identity is its
+ * normalized text (prose has no stable id, so a reworded passage reads as a
+ * removal-plus-addition — a conflict, per DIFF-4.3).
+ */
+import { getAllRequirements, parseRequirementBlock } from "../schema/index.js";
+/** Matches a fenced dotrequirements block; group 1 is its inner content. */
+const FENCE = /```dotrequirements\n([\s\S]*?)```/gm;
+/**
+ * Normalize prose for comparison: LF line endings, trailing whitespace
+ * stripped per line, runs of blank lines collapsed, ends trimmed. Two prose
+ * passages that differ only in incidental whitespace compare equal, so a
+ * whitespace-only reflow does not read as a conflict.
+ */
+export function normalizeProse(text) {
+    return text
+        .replace(/\r\n/g, "\n")
+        .split("\n")
+        .map((line) => line.replace(/\s+$/, ""))
+        .join("\n")
+        .replace(/\n{3,}/g, "\n\n")
+        .trim();
+}
+/**
+ * Split a body into its ordered units. Prose between (and around) fences
+ * becomes prose units when non-empty after normalization; each fence becomes a
+ * requirement unit keyed by its first-line KEY.
+ */
+export function segmentBody(body) {
+    const normalized = body.replace(/\r\n/g, "\n");
+    const units = [];
+    let lastIndex = 0;
+    FENCE.lastIndex = 0;
+    let match = FENCE.exec(normalized);
+    while (match !== null) {
+        const prose = normalizeProse(normalized.slice(lastIndex, match.index));
+        if (prose)
+            units.push({ kind: "prose", text: prose });
+        const blockContent = match[1].trim();
+        const keyMatch = blockContent.match(/^([\w-]+):/);
+        // A block whose first line isn't KEY: is malformed; parsing rejects it
+        // upstream, so segmentation never sees it in the compare path. Fall back to
+        // the leading text as a key so segmentation stays total regardless.
+        const key = (keyMatch ? keyMatch[1] : blockContent.slice(0, 24)).toUpperCase();
+        units.push({ kind: "requirement", key, blockContent });
+        lastIndex = FENCE.lastIndex;
+        match = FENCE.exec(normalized);
+    }
+    const tail = normalizeProse(normalized.slice(lastIndex));
+    if (tail)
+        units.push({ kind: "prose", text: tail });
+    return units;
+}
+/**
+ * Flatten a requirement block into a map from position-path id (e.g. "AUTH-1",
+ * "AUTH-1.0", "AUTH-1.2.1") to a canonical label+content string.
+ *
+ * Because the id encodes the position, a criterion inserted mid-list shifts the
+ * ids of everything after it — so an insertion cannot subset-match the original
+ * (DIFF-4.2), while an appended criterion adds a new id without disturbing the
+ * others (DIFF-4.1).
+ */
+export function requirementUnitMap(blockContent) {
+    const key = blockContent.match(/^([\w-]+):/)?.[1] ?? "";
+    const tree = parseRequirementBlock(key, blockContent);
+    const map = new Map();
+    for (const node of getAllRequirements([tree])) {
+        // A NUL (\u0000) separates the label from content so a label change reads as a change.
+        map.set(node.id.toUpperCase(), `${node.label}\u0000${node.content}`);
+    }
+    return map;
+}
+//# sourceMappingURL=segment.js.map

package/dist/sync/snapshot.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Snapshot acquisition for the comparator — kept separate from comparison so
+ * the comparator stays a pure function (compare.ts). The local half reads the
+ * workspace; the cloud half is one exportProjectForCli query.
+ */
+import type { CloudSnapshot, LocalDocument, LocalSnapshot } from "./types.js";
+/**
+ * Read and classify one requirements file into a LocalDocument. A file whose
+ * body has a structural error (duplicate key/position, orphaned position) is
+ * returned with `parseError` set — the comparator reports it as invalid_file
+ * (SYNC-FAIL-4) — while its frontmatter title, if readable, is kept for display.
+ */
+export declare function readLocalDocument(filePath: string): LocalDocument;
+/**
+ * Build the local snapshot from the workspace, or from an explicit set of file
+ * paths (scope). Files are always read fresh from disk.
+ */
+export declare function acquireLocalSnapshot(workspaceRoot: string, filePaths?: string[]): Promise<LocalSnapshot>;
+export interface CloudAuth {
+    /** projectSlug + projectSecret for full access, or a bare share token. */
+    projectSlug?: string;
+    projectSecret: string;
+}
+/**
+ * Build the cloud snapshot with one exportProjectForCli query. A share token is
+ * passed as the projectSecret with no slug (the read-only wrapper resolves the
+ * project from the token) — the read-only path never writes back.
+ */
+export declare function acquireCloudSnapshot(auth: CloudAuth): Promise<CloudSnapshot>;
+//# sourceMappingURL=snapshot.d.ts.map

package/dist/sync/snapshot.js

@@ -0,0 +1,122 @@
+/**
+ * Snapshot acquisition for the comparator — kept separate from comparison so
+ * the comparator stays a pure function (compare.ts). The local half reads the
+ * workspace; the cloud half is one exportProjectForCli query.
+ */
+import * as fs from "node:fs";
+import { ConvexHttpClient } from "convex/browser";
+import YAML from "yaml";
+import { getConvexUrl } from "../config.js";
+import { api } from "../convex.js";
+import { findRequirementsFiles } from "../requirements/index.js";
+import { splitLeadingH1, validateMetadata } from "../schema/index.js";
+import { parseRequirementBlocksFromMarkdown, splitFrontmatter, stripFrontmatterBlock, } from "../schema/parser-core.js";
+/**
+ * Read and classify one requirements file into a LocalDocument. A file whose
+ * body has a structural error (duplicate key/position, orphaned position) is
+ * returned with `parseError` set — the comparator reports it as invalid_file
+ * (SYNC-FAIL-4) — while its frontmatter title, if readable, is kept for display.
+ */
+export function readLocalDocument(filePath) {
+    let raw;
+    try {
+        raw = fs.readFileSync(filePath, "utf-8");
+    }
+    catch (err) {
+        return {
+            filePath,
+            parseError: `Could not read file: ${err.message}`,
+        };
+    }
+    // Frontmatter first, so a body-parse failure still yields id/title.
+    let documentId;
+    let title;
+    let defaultPrefix;
+    let frontmatterError;
+    const split = splitFrontmatter(raw);
+    if (split) {
+        // Pull id/title from the raw YAML before schema validation: an invalid
+        // frontmatter must not cost the file its identity, or its cloud
+        // counterpart re-pairs as "only_in_repo" and a sync mints a duplicate
+        // cloud document.
+        let rawMeta;
+        try {
+            rawMeta = YAML.parse(split.yaml);
+        }
+        catch (err) {
+            frontmatterError = `Invalid YAML frontmatter: ${err.message}`;
+        }
+        if (rawMeta && typeof rawMeta === "object" && !Array.isArray(rawMeta)) {
+            const rawDoc = rawMeta.document;
+            if (rawDoc && typeof rawDoc === "object" && !Array.isArray(rawDoc)) {
+                const d = rawDoc;
+                if (typeof d.id === "string")
+                    documentId = d.id;
+                if (typeof d.title === "string")
+                    title = d.title;
+                if (typeof d.defaultPrefix === "string")
+                    defaultPrefix = d.defaultPrefix;
+            }
+        }
+        if (rawMeta !== undefined && !frontmatterError) {
+            try {
+                validateMetadata(rawMeta);
+            }
+            catch (err) {
+                // Schema-invalid frontmatter flags the file (invalid_file) instead of
+                // proceeding with half-metadata — it must never sync as if unlinked.
+                frontmatterError = `Invalid frontmatter: ${err.message}`;
+            }
+        }
+    }
+    if (frontmatterError) {
+        return { filePath, documentId, title, parseError: frontmatterError };
+    }
+    const body = stripFrontmatterBlock(raw);
+    try {
+        parseRequirementBlocksFromMarkdown(body);
+    }
+    catch (err) {
+        return { filePath, documentId, title, parseError: err.message };
+    }
+    // SYNC-TITLE-1: the body's leading H1 is the document's title. A legacy
+    // frontmatter title stands only when the body has none (SYNC-TITLE-1.1);
+    // with neither, the document is untitled (SYNC-TITLE-1.4).
+    const derivedTitle = splitLeadingH1(body).title ?? title;
+    return { filePath, documentId, title: derivedTitle, defaultPrefix, body };
+}
+/**
+ * Build the local snapshot from the workspace, or from an explicit set of file
+ * paths (scope). Files are always read fresh from disk.
+ */
+export async function acquireLocalSnapshot(workspaceRoot, filePaths) {
+    const paths = filePaths ?? (await findRequirementsFiles(workspaceRoot));
+    return { documents: paths.map(readLocalDocument) };
+}
+/**
+ * Build the cloud snapshot with one exportProjectForCli query. A share token is
+ * passed as the projectSecret with no slug (the read-only wrapper resolves the
+ * project from the token) — the read-only path never writes back.
+ */
+export async function acquireCloudSnapshot(auth) {
+    const client = new ConvexHttpClient(getConvexUrl());
+    const projectAuth = auth.projectSlug
+        ? { projectSlug: auth.projectSlug, projectSecret: auth.projectSecret }
+        : { projectSecret: auth.projectSecret };
+    const result = (await client.query(api.documents.queries.exportProjectForCli, {
+        projectAuth,
+    }));
+    return {
+        projectName: result.projectName,
+        projectSlug: result.projectSlug,
+        documents: result.documents.map((d) => ({
+            documentId: d.documentId,
+            title: d.title,
+            defaultPrefix: d.defaultPrefix,
+            body: d.markdownContent,
+            version: d.version,
+            updatedAt: d.updatedAt,
+        })),
+    };
+}
+//# sourceMappingURL=snapshot.js.map

package/dist/sync/types.d.ts

@@ -0,0 +1,82 @@
+/**
+ * Shared vocabulary for the repo/cloud comparator (DIFF-*, SYNC-*).
+ *
+ * One vocabulary, no translation layer: the verdict identifiers here are the
+ * words the CLI prints. `verdictLabel` only reshapes an identifier into its
+ * spaced form ("additions_in_repo" -> "additions in repo"); it never renames.
+ */
+/**
+ * Per-document verdict from comparing the repo and the cloud (DIFF-1.0).
+ */
+export type Verdict = "in_sync" | "additions_in_repo" | "additions_in_cloud" | "conflict" | "only_in_repo" | "only_in_cloud" | "invalid_file";
+/** The user-facing spelling of a verdict — same words, spaced. */
+export declare function verdictLabel(verdict: Verdict): string;
+/**
+ * One document as it exists locally: a `.requirements.md` file. When the file
+ * cannot be parsed, `parseError` is set and the other content fields are absent
+ * — the comparator reports it as `invalid_file` (SYNC-FAIL-4).
+ */
+export interface LocalDocument {
+    filePath: string;
+    /** document.id from frontmatter, when the file is linked to a cloud document. */
+    documentId?: string;
+    title?: string;
+    defaultPrefix?: string;
+    /** Frontmatter-stripped markdown body (the comparison unit, SYNC-ARCH-1). */
+    body?: string;
+    parseError?: string;
+}
+/**
+ * One published document as it exists in the cloud, from exportProjectForCli.
+ */
+export interface CloudDocument {
+    documentId: string;
+    title: string;
+    defaultPrefix?: string;
+    /** Published markdownContent (SYNC-ARCH-1). */
+    body: string;
+    version: number;
+    updatedAt: number;
+}
+export interface LocalSnapshot {
+    documents: LocalDocument[];
+}
+export interface CloudSnapshot {
+    projectName: string;
+    projectSlug: string;
+    documents: CloudDocument[];
+}
+/**
+ * A single point of difference within a paired document, for verbose
+ * document-scope diff (DIFF-2). `verdict` reuses the document vocabulary at
+ * unit granularity — the verdicts are fractal.
+ */
+export interface UnitDetail {
+    /** Requirement key, or a short prose descriptor. */
+    unit: string;
+    verdict: "additions_in_repo" | "additions_in_cloud" | "conflict";
+    /** Criterion positions new on one side, when the difference is criterion-level. */
+    positions?: string[];
+    note?: string;
+}
+/**
+ * The comparison of one document across the two surfaces. Identity for
+ * scoping/output comes from documentId / filePath / title directly.
+ */
+export interface DocumentComparison {
+    verdict: Verdict;
+    /** File path when the document exists locally. */
+    filePath?: string;
+    /** Cloud document id when the document exists in the cloud. */
+    documentId?: string;
+    /** Display title (from whichever side has the document). */
+    title: string;
+    /** Parse error message when verdict is invalid_file. */
+    error?: string;
+    /** Unit-level breakdown, populated for verbose diff of non-in-sync documents. */
+    details?: UnitDetail[];
+}
+export interface ComparisonResult {
+    documents: DocumentComparison[];
+}
+//# sourceMappingURL=types.d.ts.map

package/dist/sync/types.js

@@ -0,0 +1,12 @@
+/**
+ * Shared vocabulary for the repo/cloud comparator (DIFF-*, SYNC-*).
+ *
+ * One vocabulary, no translation layer: the verdict identifiers here are the
+ * words the CLI prints. `verdictLabel` only reshapes an identifier into its
+ * spaced form ("additions_in_repo" -> "additions in repo"); it never renames.
+ */
+/** The user-facing spelling of a verdict — same words, spaced. */
+export function verdictLabel(verdict) {
+    return verdict.replace(/_/g, " ");
+}
+//# sourceMappingURL=types.js.map

package/dist/templates/context-file-section.md

@@ -57,7 +57,8 @@ test(requirement('REQ-ID.0'), () => { /* test specific criterion */ });
 **Authoring:**
 - `dotreq create-requirement-document [path]` - Print the template and style guide
 - `dotreq validate [glob]` - Check syntax (works offline)
-- `dotreq push [file]` - Sync to cloud (shows diff preview, then confirms)
+- `dotreq diff [scope...]` - Show how the repo and the cloud differ (read-only)
+- `dotreq sync [scope...]` - Reconcile the repo and the cloud (both contribute by default)
 
 **Review (judgment runs in the dispatched subagent):**
 - `dotreq style-check <file>` - Emits the style guide + content for the reviewer to judge (`--source cloud` for hosted review)

package/dist/templates/example-requirements.js

@@ -10,8 +10,6 @@ export function generateExampleRequirements(projectId = "local") {
 projectId: ${projectId}
 pulledAt: ${now}
 version: 1
-document:
-  title: "Example Requirements"
 ---
 
 # Example Requirements

package/dist/templates/example-requirements.ts

@@ -13,8 +13,6 @@ export function generateExampleRequirements(
 projectId: ${projectId}
 pulledAt: ${now}
 version: 1
-document:
-  title: "Example Requirements"
 ---
 
 # Example Requirements

package/dist/templates/requirements-readme.js

@@ -6,8 +6,7 @@ export function generateRequirementsReadme() {
 
 This directory contains requirements for the project. Requirements can be:
 - Hand-authored locally in Markdown files
-- Generated via \`dotrequirements pull\` from dot•requirements cloud
-- Synced bidirectionally with \`dotrequirements push\`
+- Synced bidirectionally with dot•requirements cloud via \`dotrequirements sync\`
 
 ## File Format
 
@@ -21,8 +20,8 @@ Requirements use the \`*.requirements.md\` naming pattern. See the [Requirements
 
 ## Commands
 
-- \`dotrequirements pull\` - Sync requirements from cloud
-- \`dotrequirements push\` - Push local requirements to cloud
+- \`dotrequirements sync\` - Reconcile requirements with the cloud (both directions)
+- \`dotrequirements diff\` - Show how the repo and the cloud differ (read-only)
 - \`dotrequirements validate\` - Validate requirement files
 
 Learn more: https://dotrequirements.io

package/dist/templates/requirements-readme.ts

@@ -6,8 +6,7 @@ export function generateRequirementsReadme(): string {
 
 This directory contains requirements for the project. Requirements can be:
 - Hand-authored locally in Markdown files
-- Generated via \`dotrequirements pull\` from dot•requirements cloud
-- Synced bidirectionally with \`dotrequirements push\`
+- Synced bidirectionally with dot•requirements cloud via \`dotrequirements sync\`
 
 ## File Format
 
@@ -21,8 +20,8 @@ Requirements use the \`*.requirements.md\` naming pattern. See the [Requirements
 
 ## Commands
 
-- \`dotrequirements pull\` - Sync requirements from cloud
-- \`dotrequirements push\` - Push local requirements to cloud
+- \`dotrequirements sync\` - Reconcile requirements with the cloud (both directions)
+- \`dotrequirements diff\` - Show how the repo and the cloud differ (read-only)
 - \`dotrequirements validate\` - Validate requirement files
 
 Learn more: https://dotrequirements.io

package/dist/templates/skills/codebase-to-spec/SKILL.md

@@ -92,8 +92,8 @@ The spec is written; this step is about what the user does with it. End the run
 
 1. If no cloud credentials exist, run `{{DOTREQ_CLI}} link --yes --json` via Bash. The user completes login in the browser; everything else is yours.
 2. If link exits with code 2, its JSON is a `decision_needed` — multiple teams, existing projects, or a plan at its project limit. Relay the options conversationally (they are the user's choice, not yours), then retry link with the chosen option's `retryFlag` appended.
-3. Once linked, run `{{DOTREQ_CLI}} push --yes`. Present each document's web URL from the output as the place the user's team reviews it.
-4. Hand over the share mechanics from link's JSON, matched to the teammate's surface: the `inviteUrl` for a teammate who will review in the web platform, and the `sharePullCommand` for a teammate working in their IDE. If link omitted one (e.g. the user isn't a team admin), hand over what's there without apology.
+3. Once linked, run `{{DOTREQ_CLI}} sync --repo-contributes --yes`. Present each document's web URL from the output as the place the user's team reviews it.
+4. Hand over the share mechanics from link's JSON, matched to the teammate's surface: the `inviteUrl` for a teammate who will review in the web platform, and the `shareSyncCommand` for a teammate working in their IDE. If link omitted one (e.g. the user isn't a team admin), hand over what's there without apology.
 5. With the spec in the cloud, offer to set up the assistant you are running as to work from the spec going forward — framed as that outcome ("I can work from this spec in future sessions"), not as configuration. On acceptance, run `{{DOTREQ_CLI}} ai-setup --assistant <id>` with the identifier for this assistant (e.g. `claude-code`).
 
 If the user declines the team-review offer, note that it stands for later and don't repeat the pitch.

package/dist/utils/project-settings.d.ts

@@ -41,7 +41,6 @@ export interface ProjectInfo {
  * Returns undefined if either is missing.
  */
 export declare function getCredentialsFromEnv(): ProjectSettings | undefined;
-export declare function setAuthFromEnv(enabled: boolean): void;
 /**
  * Find the project root by walking up from startDir looking for .requirements/ folder
  * Returns the directory containing .requirements/, or undefined if not found
@@ -66,8 +65,15 @@ export declare function writeProjectSettings(projectRoot: string, settings: Proj
  * Returns undefined if no project found
  */
 export declare function getProjectInfo(startDir?: string): ProjectInfo | undefined;
+export declare function setPreferEnvCredentials(enabled: boolean): void;
 /**
- * Get project credentials, throwing helpful error if not available
+ * Get project credentials, throwing a helpful error if not available.
+ *
+ * AUTHZ-6: the settings file wins when present; the environment is the fallback
+ * when no settings file is on disk. A local checkout's binding is never
+ * overridden by an ambient environment (AUTHZ-6.0), while a CI checkout with no
+ * settings file authenticates from DOTREQ_PROJECT_ID / DOTREQ_PROJECT_SECRET
+ * (AUTHZ-6.1) — no flag required.
  */
 export declare function getProjectCredentials(startDir?: string): ProjectSettings;
 //# sourceMappingURL=project-settings.d.ts.map

package/dist/utils/project-settings.js

@@ -18,19 +18,6 @@ export function getCredentialsFromEnv() {
     }
     return undefined;
 }
-/**
- * AUTHZ-6: explicit CI/CD credential injection. Set by the global
- * --auth-from-env flag (cli.ts preAction hook); when enabled,
- * getProjectCredentials reads DOTREQ_PROJECT_ID / DOTREQ_PROJECT_SECRET
- * instead of file-based discovery. Without the flag those variables are
- * ignored entirely — the explicit opt-in prevents credential conflicts
- * between local and CI environments. (Previously the retired MCP server's
- * --auth-from-env; ported to the CLI with identical semantics.)
- */
-let authFromEnv = false;
-export function setAuthFromEnv(enabled) {
-    authFromEnv = enabled;
-}
 /**
  * Find the project root by walking up from startDir looking for .requirements/ folder
  * Returns the directory containing .requirements/, or undefined if not found
@@ -167,25 +154,61 @@ export function getProjectInfo(startDir = process.cwd()) {
     };
 }
 /**
- * Get project credentials, throwing helpful error if not available
+ * SYNC-ALIAS-1.3: the retired `--auth-from-env` global flag survives as a
+ * deprecated alias for the commands already in users' CI (the doc-site taught
+ * `dotreq --auth-from-env push`). When set, environment credentials replace
+ * file discovery entirely — the flag's original semantics — so an old
+ * invocation behaves identically.
+ */
+let preferEnvCredentials = false;
+export function setPreferEnvCredentials(enabled) {
+    preferEnvCredentials = enabled;
+}
+/**
+ * Get project credentials, throwing a helpful error if not available.
+ *
+ * AUTHZ-6: the settings file wins when present; the environment is the fallback
+ * when no settings file is on disk. A local checkout's binding is never
+ * overridden by an ambient environment (AUTHZ-6.0), while a CI checkout with no
+ * settings file authenticates from DOTREQ_PROJECT_ID / DOTREQ_PROJECT_SECRET
+ * (AUTHZ-6.1) — no flag required.
  */
 export function getProjectCredentials(startDir = process.cwd()) {
-    // AUTHZ-6.0 / 6.1: with the explicit flag, env credentials replace
-    // file-based discovery entirely
-    if (authFromEnv) {
+    // SYNC-ALIAS-1.3: deprecated --auth-from-env keeps its original semantics —
+    // env replaces file discovery entirely.
+    if (preferEnvCredentials) {
         const envCredentials = getCredentialsFromEnv();
         if (!envCredentials) {
-            throw new Error("--auth-from-env requires both DOTREQ_PROJECT_ID and DOTREQ_PROJECT_SECRET environment variables to be set.");
+            throw new Error("Both DOTREQ_PROJECT_ID and DOTREQ_PROJECT_SECRET must be set to authenticate from the environment.");
         }
         return envCredentials;
     }
-    const info = getProjectInfo(startDir);
-    if (!info) {
-        throw new Error('No dotrequirements project found. Run "dotrequirements init" to create one.');
+    // File wins: a present, valid settings file is authoritative. readProjectSettings
+    // throws on a present-but-invalid file, surfacing it rather than silently
+    // falling through to the environment.
+    const root = findProjectRoot(startDir);
+    if (root) {
+        const settings = readProjectSettings(root);
+        if (settings)
+            return settings;
+    }
+    // No settings file on disk — fall back to the environment (AUTHZ-6.1).
+    const envCredentials = getCredentialsFromEnv();
+    if (envCredentials) {
+        // AUTHZ-6.1: announce the fallback, on stderr so it never pollutes stdout
+        // that a caller may be parsing.
+        process.stderr.write("Authenticating from the DOTREQ_PROJECT_ID / DOTREQ_PROJECT_SECRET environment variables.\n");
+        return envCredentials;
     }
-    if (!info.credentials) {
-        throw new Error('Project is not connected to cloud. Run "dotrequirements link" to connect.');
+    // AUTHZ-6.2: exactly one variable set is a misconfiguration, not a silent
+    // no-op — name both.
+    if (process.env.DOTREQ_PROJECT_ID || process.env.DOTREQ_PROJECT_SECRET) {
+        throw new Error("Both DOTREQ_PROJECT_ID and DOTREQ_PROJECT_SECRET must be set to authenticate from the environment.");
+    }
+    // AUTHZ-6.3 / AUTHZ-2: neither a settings file nor environment credentials.
+    if (!root) {
+        throw new Error('No dotrequirements project found. Run "dotrequirements init" to create one.');
     }
-    return info.credentials;
+    throw new Error("Cloud features require authentication. Run 'dotrequirements link'.");
 }
 //# sourceMappingURL=project-settings.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@popoverai/dotrequirements",
-  "version": "0.27.4",
+  "version": "0.29.0",
   "description": "Requirements tracking CLI and test harness",
   "type": "module",
   "bin": {

package/dist/commands/pull.d.ts

@@ -1,8 +0,0 @@
-interface PullOptions {
-    project?: string;
-    document?: string;
-    share?: string;
-}
-export declare function pullCommand(options: PullOptions): Promise<void>;
-export {};
-//# sourceMappingURL=pull.d.ts.map