@hawkeyexl/manni 2.3.7 → 2.3.9

package/dist/docmeta.js

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
 import {
   buildProgram
-} from "./chunk-4YJ4TCKM.js";
+} from "./chunk-HOLRWVCO.js";
 import {
   runIfMain
-} from "./chunk-D5FTEP3H.js";
+} from "./chunk-LC4H35XX.js";
 
 // src/docmeta.ts
 runIfMain(import.meta.url, () => buildProgram().name("docmeta"));

package/dist/index.d.ts

@@ -1077,7 +1077,10 @@ interface RunConfigOptions {
     noConfig?: boolean;
     /**
      * Positional inputs; empty means fall back to the configured collections'
-     * `paths:` (proposal 0041).
+     * `paths:` (proposal 0041). The stdin token `-` cancels that implicit
+     * fallback like any other input, but never an explicit `--collection`:
+     * stdin is no path, so it rides beside the flag and the named collection is
+     * still resolved.
      */
     inputs: string[];
     /**
@@ -1094,7 +1097,8 @@ interface RunConfig {
     config: DocmetaConfig | null;
     /**
      * What to resolve: the positional inputs, or the selected collections'
-     * `paths:`, concatenated in declaration order.
+     * `paths:` concatenated in declaration order — with the stdin token, when
+     * `--collection` put both in one run, kept at the front.
      */
     inputs: string[];
     /**
@@ -1105,7 +1109,9 @@ interface RunConfig {
      * both, so there is exactly one base per run and no ambiguity about which it
      * is. Positional paths are typed by a person standing in a shell, so they
      * stay relative to the working directory; a collection's globs were written
-     * next to the config, so they resolve from there.
+     * next to the config, so they resolve from there. Stdin decides nothing
+     * here: it is no path, so it needs no base of its own, and a `-` beside
+     * `--collection` leaves the base to the collections.
      */
     base: string;
     /**
@@ -1155,9 +1161,10 @@ interface RunConfig {
      */
     declaredCollections: CollectionConfig[];
     /**
-     * Whether `inputs` came from the collections rather than the command line.
+     * Whether the collections supplied `inputs` rather than the command line.
      * The corpus invariant every scoped check reads: a positional path means the
-     * operator chose part of the corpus.
+     * operator chose part of the corpus. True whenever `--collection` named one,
+     * stdin beside it included.
      */
     fromCollections: boolean;
     /**
@@ -4646,7 +4653,12 @@ interface CiteRunOptions {
     configPath?: string;
     /** `--no-config`: skip discovery and run on the built-in defaults. */
     noConfig?: boolean;
-    /** Positional inputs; empty means fall back to the selected collections' `paths:`. */
+    /**
+     * Positional inputs; empty means fall back to the selected collections'
+     * `paths:`. The stdin token `-` cancels that implicit fallback like any
+     * other input, but never an explicit `--collection`: stdin is no path, so
+     * it rides beside the flag and the named collection is still resolved.
+     */
     inputs: string[];
     /**
      * `--collection <name>`, repeatable: the collections this run covers. Empty

package/dist/index.js

@@ -5,7 +5,7 @@ import {
   reencryptMetadata,
   runKeyRotate,
   runKeySet
-} from "./chunk-Y2XNDEM6.js";
+} from "./chunk-YSI2VNKE.js";
 import {
   BinMissing,
   COMMON_FORMATS,
@@ -127,7 +127,7 @@ import {
   valueOf,
   vendorFileName,
   writeFileAtomic
-} from "./chunk-D5FTEP3H.js";
+} from "./chunk-LC4H35XX.js";
 
 // src/key/index.ts
 var key_exports = {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hawkeyexl/manni",
-  "version": "2.3.7",
+  "version": "2.3.9",
   "description": "One command line for documentation that is meant to be checked. `manni meta` validates the presence and format of document metadata (Markdown frontmatter and more) against JSON Schema, built for CI. Formerly docmeta.",
   "type": "module",
   "bin": {