ctxr-cli 0.26.0 → 0.27.0

package/dist/core/publish/send-copies.js

@@ -0,0 +1,15 @@
+/**
+ * send-copies-beside-their-page: a send copy is a file built from a note and
+ * sent to someone — a record of what went out on a day. Directly in a page
+ * folder, beside `index.html`, a file in one of these formats is one; anywhere
+ * below it, the same file is an input the page uses (file-pdfs-beside-their-page
+ * D3). A closed list, so a missed format goes unchecked rather than failing a
+ * page over a file nobody sent (D1). Adding a format is one entry here.
+ */
+export const SEND_COPY_EXTENSIONS = ['.pdf', '.docx', '.xlsx', '.pptx'];
+/** The send-copy extension `fileName` carries, lower-cased, or `null` when it is not a send copy. */
+export function sendCopyExtension(fileName) {
+    const lower = fileName.toLowerCase();
+    return SEND_COPY_EXTENSIONS.find((extension) => lower.endsWith(extension)) ?? null;
+}
+//# sourceMappingURL=send-copies.js.map

package/dist/core/publish/send-copies.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"send-copies.js","sourceRoot":"","sources":["../../../src/core/publish/send-copies.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAsB,CAAC,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,OAAO,CAAC,CAAC;AAE3F,qGAAqG;AACrG,MAAM,UAAU,iBAAiB,CAAC,QAAgB;IAChD,MAAM,KAAK,GAAG,QAAQ,CAAC,WAAW,EAAE,CAAC;IACrC,OAAO,oBAAoB,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,CAAC,SAAS,CAAC,CAAC,IAAI,IAAI,CAAC;AACrF,CAAC"}

package/dist/version.d.ts

@@ -1,5 +1,5 @@
 /** Kept in sync with package.json's "version" field. */
-export declare const CLI_VERSION = "0.26.0";
+export declare const CLI_VERSION = "0.27.0";
 /**
  * The npm package this executable is published as. Bound here, beside the
  * version, because the release check resolves the latest published release by

package/dist/version.js

@@ -1,5 +1,5 @@
 /** Kept in sync with package.json's "version" field. */
-export const CLI_VERSION = '0.26.0';
+export const CLI_VERSION = '0.27.0';
 /**
  * The npm package this executable is published as. Bound here, beside the
  * version, because the release check resolves the latest published release by

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ctxr-cli",
-  "version": "0.26.0",
+  "version": "0.27.0",
   "description": "Context store for AI coding agents — markdown and git, catalog and graph retrieval, no vector database.",
   "type": "module",
   "license": "MIT",

package/templates/skills/ctxr-publish.md

@@ -96,8 +96,8 @@ this choice. Why: a page filed under a word that names nothing helps no reader.
 
 Never start the page's own name with a date (`YYYY-` or `YYYY-MM-DD-`). That naming is reserved for
 the frozen pages that `ctxr publish new --disposable` makes. The rule applies to the final segment, not
-to the folders above it. It does not apply to a PDF file in the page's folder, which starts with its
-render date (step 8). The command refuses to overwrite an existing folder. If a folder already
+to the folders above it. It does not apply to a send copy in the page's folder, which starts with
+the date you made it (step 8). The command refuses to overwrite an existing folder. If a folder already
 exists for this subject, edit its files directly. Do not run `publish new` again. Why: a rename or an
 overwrite breaks a link that somebody already has.
 
@@ -134,7 +134,8 @@ Run `ctxr publish check <path>`. It runs the mechanical half of the checklist:
   with a real date at the start of its name;
 - for a permanent page, the note it represents (`represented-note`) and that note's recorded hash
   (`represented-note-hash`).
-- for each PDF at the page folder's root, a file name that starts with a real date (`pdf-name`).
+- for each send copy at the page folder's root, a file name that starts with a real date
+  (`send-copy-name`).
 
 The command reports the page's lifespan. It exits non-zero and names every failing check. Fix all of
 them before you report the page as ready. The command answers only what the files can show. Why: the
@@ -188,27 +189,38 @@ changed after the stamp. To confirm a stale page, do these steps in order:
 `ctxr publish stamp` never overwrites a marker. Why: a stamp without a review confirms nothing, so
 the stale report stays until somebody removes the marker.
 
-**A PDF of the page.** Make a PDF only when you send the page as a document. Why: every PDF is
-kept, so a PDF for each edit fills the folder.
+**Send copies of the page.** A send copy is a file that you make from the note and send to somebody.
+It is a `.pdf`, `.docx`, `.xlsx` or `.pptx` file. Make a send copy only when you send one. Why: every
+send copy is kept, so a send copy for each edit fills the folder.
 
-Write the PDF into the page's folder, next to `index.html`. Start its file name with the date you
-render it: `<YYYY-MM-DD>-<name>.pdf`. `ctxr publish check` fails a PDF at the folder root that has no
-real date (`pdf-name`). `ctxr publish check --json` lists each PDF with its address. Give that address
-when you hand on the PDF.
+Write the send copy into the page's folder, next to `index.html`. Start its file name with the date
+you make it: `<YYYY-MM-DD>-<name>.<extension>`. `ctxr publish check` fails a send copy at the folder
+root that has no real date (`send-copy-name`). `ctxr publish check --json` lists each send copy with
+its address. Give that address when you hand on the send copy.
 
-A PDF is never a page on its own. A document that you send as a PDF still needs an `index.html`, and
-you print the PDF from it. Why: every command that reads pages finds a page by its `index.html`. The
-stamp on its README then reports the page and its PDFs as stale together.
+A send copy is never a page on its own. A document that you send as a PDF, a Word file, a workbook or
+a deck still needs an `index.html` for the same content. Why: every command that reads pages finds a
+page by its `index.html`. The stamp on its README then reports the page and its send copies as stale
+together.
 
-When the page changes, write a new dated PDF. Do not change or remove an earlier PDF. Why: an earlier
-file can be the one a recipient got, and the folder then shows what you sent on each date.
+When the page changes, write a new dated send copy. Do not change or remove an earlier one. Why: an
+earlier file can be the one a recipient got, and the folder then shows what you sent on each date.
 
-Put a PDF that the page uses, but that you did not render, in the page's `assets/` folder. Why:
-`ctxr publish check` reads only the PDFs at the folder root as the page's renderings.
+Put a file that the page uses, but that you did not make, in the page's `assets/` folder. Why:
+`ctxr publish check` reads only the files at the folder root as the page's send copies.
 
-The store chooses how to make the PDF. You can print `index.html`, which already has a print rule.
-You can also use the store's own document skill, if it keeps its styled HTML as `index.html`.
-Contexture does not render PDFs.
+The store chooses how to make a send copy. You can print `index.html` to a PDF, because it already
+has a print rule. You can also use the store's own document or spreadsheet skill. Contexture does not
+make send copies.
+
+**A file that is its own source.** Some office files are not made from a note. An example is a
+financial model that somebody edits by hand in a spreadsheet. Do not publish that file. Keep it in
+the store, next to the note that describes it, with no date in its name. Why: the file is the source,
+and the note describes it. A published copy would sit where retrieval does not look, and the stale
+report would treat the note as the source. Git keeps the file's history. When you send a copy of the
+file to somebody, that copy is a send copy: write it, dated, into the page's folder.
+
+A file that you received from somebody is a capture. File it where the store keeps its captures.
 
 Never revise a disposable page after it lands. Why: it is a snapshot of one moment, and its link
 shows that moment. Make a new disposable page instead. Do not remove a disposable page yourself.