@listen-fire/handbook 0.12.6 → 0.12.8

package/dist/chapters/expressions.js

@@ -71,7 +71,7 @@ write crm-[:Companies]-> {
 Values that come from the run itself rather than from any record wear an \`@\` prefix and read like any other value, anywhere an expression can appear. There are eight, in three groups:
 
 - \`@current_date\` (\`"2026-03-12"\`) and \`@current_timestamp\`, the moment the run fires, in UTC — \`Deadline: Date.addDays(@current_date, 14)\`. Every clock reading in a run gives that same moment, however long the run takes. For the date somewhere in particular, reach for \`Date.today(zone)\`.
-- \`@user_email\`, \`@user_name\`, \`@user_id\` — the identity the host resolves for the run: the person it acts *on behalf of*. The platform resolves it through its workspace members, \`lf\` through the project. Forwarders are followed back to the real person: a message forwarded in by a teammate still names the original sender, the person whose work this is.
+- \`@user_email\`, \`@user_name\`, \`@user_id\` — the identity the host resolves for the run: the person it acts *on behalf of*. The platform resolves it through its workspace members, \`listen-fire\` through the project. Forwarders are followed back to the real person: a message forwarded in by a teammate still names the original sender, the person whose work this is.
 - \`@actor_email\`, \`@actor_name\`, \`@actor_id\` — whoever literally triggered the event in the source system, exactly as it reported them, member or not.
 
 The two agree until a forward, relay, or service account sits between the originator and the responsible person. A meta-field the run can't resolve — an event the host maps to no identity, a source that reports no sender — is simply empty, never an error.

package/dist/chapters/foundations.js

@@ -37,8 +37,8 @@ and refuses any other by name:
 - a pin of an older key is refused; validate the text under the current release,
   then upgrade it
 
-An \`lf\` project pins in \`lf.yaml\`'s \`engine:\` (\`lf init\` writes the current
-release; \`lf upgrade\` moves it). An embedder pins with the run input's
+A \`listen-fire\` project pins in \`lf.yaml\`'s \`engine:\` (\`listen-fire init\` writes the current
+release; \`listen-fire upgrade\` moves it). An embedder pins with the run input's
 \`languageVersion\`; absent means the engine's own release.
 
 A warning on an automation says something keeps it on an older release: the

package/dist/chapters/runs.js

@@ -6,7 +6,7 @@ exports.runs = {
     title: 'Runs — reading what an automation did',
     content: `## Runs — reading what an automation did
 
-Every firing of an automation — a live event arriving, a "run now" backfill, a dry-run rehearsal — is recorded by the engine as a **run**: one record holding what the automation wrote, where, and why — the record for verifying it does what the text says, and for tracing any written value back to its source. Wherever you read runs (\`lf runs show\` in a project, or the platform's run history), you are reading this same record.
+Every firing of an automation — a live event arriving, a "run now" backfill, a dry-run rehearsal — is recorded by the engine as a **run**: one record holding what the automation wrote, where, and why — the record for verifying it does what the text says, and for tracing any written value back to its source. Wherever you read runs (\`listen-fire runs show\` in a project, or the platform's run history), you are reading this same record.
 
 ### run-history
 

package/dist/front_page.d.ts

@@ -28,8 +28,8 @@ export declare function exampleText(example: FrontExample): string;
 export declare const TS_EXCEPT: readonly FrontEntry[];
 /** The ideas with no TypeScript analogue — a few lines each, then search. */
 export declare const CONCEPTS: readonly FrontEntry[];
-/** Agent-facing, so it names the tools: the `lf` commands first, then the platform's spelling of each. */
-export declare const BUILD_LOOP = "### build-loop\n\n`lf check`, `lf run`, `lf runs show`; on the platform: getStarted, saveAutomation (checks first; saves nothing with errors), runAutomation, checkRun. No chapters: searchLanguage answers lookups, describeConnection details one system. Batch calls.";
+/** Agent-facing, so it names the tools: the `listen-fire` commands first, then the platform's spelling of each. */
+export declare const BUILD_LOOP = "### build-loop\n\n`listen-fire check`, `listen-fire run`, `listen-fire runs show`; on the platform: getStarted, saveAutomation (checks first; saves nothing with errors), runAutomation, checkRun. No chapters: searchLanguage answers lookups, describeConnection details one system. Batch calls.";
 /** The front page, as the automations connector serves it. */
 export declare function renderFrontPage(): string;
 /** Every anchor the page answers to, entry by entry. */

package/dist/front_page.js

@@ -144,10 +144,10 @@ exports.CONCEPTS = [
         },
     },
 ];
-/** Agent-facing, so it names the tools: the `lf` commands first, then the platform's spelling of each. */
+/** Agent-facing, so it names the tools: the `listen-fire` commands first, then the platform's spelling of each. */
 exports.BUILD_LOOP = `### build-loop
 
-\`lf check\`, \`lf run\`, \`lf runs show\`; on the platform: getStarted, saveAutomation (checks first; saves nothing with errors), runAutomation, checkRun. No chapters: searchLanguage answers lookups, describeConnection details one system. Batch calls.`;
+\`listen-fire check\`, \`listen-fire run\`, \`listen-fire runs show\`; on the platform: getStarted, saveAutomation (checks first; saves nothing with errors), runAutomation, checkRun. No chapters: searchLanguage answers lookups, describeConnection details one system. Batch calls.`;
 function renderExample(example) {
     return `\n\`\`\`\n${exampleText(example)}\n\`\`\``;
 }

package/dist/index.js

@@ -83,7 +83,7 @@ exports.INTENT_INDEX = [
     { intent: "Slack's message field, files, taps, Block Kit", chapter: 'system:slack' },
     { intent: "Telegram's message field, opening a chat, taps", chapter: 'system:telegram' },
     { intent: "WhatsApp's message field, files, taps", chapter: 'system:whatsapp' },
-    { intent: 'A mailbox: run on arriving mail, search, send, reply', chapter: 'system:gmail' },
+    { intent: 'A mailbox: run on arriving or labelled mail, search, send, reply, draft', chapter: 'system:gmail' },
     { intent: 'Create a record with several parents', chapter: 'writes', section: 'multi-parent-writes' },
     { intent: 'Write a nested object or list', chapter: 'writes', section: 'structured-values' },
     { intent: 'Connect a record to one that already exists', chapter: 'writes', section: 'link' },

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@listen-fire/handbook",
   "license": "Apache-2.0",
-  "version": "0.12.6",
+  "version": "0.12.8",
   "description": "The movement language's handbook: the hand-written chapters, the front page, the routes into them and the language search over them. A host adds its own systems' and plugins' sections on top (the platform assembles system:* and plugin:* chapters). `testing` is the catalog every shown example is checked against, for a host's tests of its own sections.",
   "engines": {
     "node": ">=22.23.4 <23"