@forwardimpact/outpost 3.8.1 → 3.10.0

package/config/scheduler.json

@@ -1,32 +1,38 @@
 {
   "agents": {
     "postman": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "full",
       "schedule": { "type": "cron", "expression": "*/15 8-18 * * 1-5" },
       "enabled": true
     },
     "concierge": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "full",
       "schedule": { "type": "cron", "expression": "*/30 8-18 * * 1-5" },
       "enabled": true
     },
     "librarian": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 9,12,15,18 * * 1-5" },
       "enabled": true
     },
     "chief-of-staff": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 7,18 * * 1-5" },
       "enabled": true
     },
     "recruiter": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 8,12,17 * * 1-5" },
       "enabled": true
     },
     "head-hunter": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 9 * * 1-5" },
       "enabled": true
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forwardimpact/outpost",
-  "version": "3.8.1",
+  "version": "3.10.0",
   "description": "Personal operations center — context from email, calendar, and knowledge assembled so preparation is continuous, not a morning scramble.",
   "homepage": "https://www.forwardimpact.team",
   "repository": {

package/src/agent-runner.js

@@ -11,6 +11,7 @@ import {
   loadManifest,
   draftSkills,
 } from "./posture.js";
+import { resolvePrivilege, disclaimFor } from "./privilege.js";
 import { buildSpawnEnv } from "./spawn-env.js";
 
 /**
@@ -176,6 +177,24 @@ export class AgentRunner {
    * @param {Record<string, string>} [configEnv] - Extra env vars from config
    */
   async wake(agentName, agent, state, configEnv) {
+    // Resolve the mandatory privilege level before any work. A missing or
+    // invalid level is fail-closed: log and skip the wake — no agent process is
+    // spawned with a guessed privilege. The level lives in the user-only trust
+    // root, so a spawned agent cannot raise its own.
+    let level;
+    try {
+      level = resolvePrivilege(agent);
+    } catch (err) {
+      this.#log(
+        JSON.stringify({
+          event: "outpost.privilege.rejected",
+          agent: agentName,
+          error: err.message,
+        }),
+      );
+      return;
+    }
+
     if (!agent.kb) {
       this.#log(`Agent ${agentName}: no "kb" specified, skipping.`);
       return;
@@ -191,6 +210,13 @@ export class AgentRunner {
     const claude = await this.#findClaude();
 
     this.#log(`Waking agent: ${agentName} (kb: ${agent.kb})`);
+    this.#log(
+      JSON.stringify({
+        event: "outpost.privilege.resolved",
+        agent: agentName,
+        level,
+      }),
+    );
 
     const as = (state.agents[agentName] ||= {});
     as.status = "active";
@@ -226,6 +252,7 @@ export class AgentRunner {
         env,
         kbPath,
         this.#runtime,
+        disclaimFor(level),
       );
       this.#activeChildren.add(pid);
 

package/src/kb-manager.js

@@ -2,7 +2,7 @@
  * KBManager — knowledge base init/update operations.
  */
 
-import { join, dirname, resolve } from "node:path";
+import { join, dirname, resolve, basename } from "node:path";
 import { homedir } from "node:os";
 import { createLogger } from "@forwardimpact/libtelemetry";
 
@@ -23,6 +23,33 @@ export class KBManager {
     this.#logger = createLogger("outpost", runtime);
   }
 
+  /**
+   * Resolve a knowledge-base name to its path under the XDG data home,
+   * `~/.local/share/fit/outpost/<name>`. The argument is a single path segment,
+   * never an arbitrary filesystem path, so a provisioned KB always lands outside
+   * TCC-protected folders. The name is validated — not sanitised — against the
+   * same rule as `agent-path.js`: a name carrying `/`, `\`, `..`, NUL, or a
+   * leading `~` could steer the KB back inside `~/Documents`, reopening the TCC
+   * hole, so it is rejected rather than rewritten.
+   * @param {string} name - The KB name (e.g. `Team`, `personal`).
+   * @returns {string} Absolute path under the data home.
+   * @throws {Error} when `name` is empty, non-string, or an unsafe segment.
+   */
+  static kbPathForName(name) {
+    if (
+      typeof name !== "string" ||
+      name.length === 0 ||
+      name.includes("/") ||
+      name.includes("\\") ||
+      name.includes("..") ||
+      name.includes("\0") ||
+      name.startsWith("~")
+    ) {
+      throw new Error(`unsafe KB name: ${JSON.stringify(name)}`);
+    }
+    return join(homedir(), ".local/share/fit/outpost", name);
+  }
+
   /**
    * Test whether a path exists, via the async fs surface.
    * @param {string} p
@@ -187,6 +214,7 @@ export class KBManager {
       await this.#ensureDir(join(dest, d));
 
     await this.copyBundledFiles(templateDir, dest);
+    await this.#linkIntoDocuments(dest);
 
     this.#logger.info(
       `Knowledge base initialized at ${dest}\n\nNext steps:\n  1. cd ${dest} && npx apm install\n  2. claude\n  3. Run the person-identify skill to populate your identity`,
@@ -194,6 +222,31 @@ export class KBManager {
     return { ok: true, value: { dest } };
   }
 
+  /**
+   * Create a navigation symlink at `~/Documents/<name>` pointing to the KB.
+   * The KB data itself stays under the XDG data home, outside TCC-protected
+   * folders — this is only a convenience pointer so the KB is easy to find and
+   * open from Finder. Best-effort: a pre-existing entry is left untouched, and
+   * any failure (e.g. macOS denying write access to `~/Documents`) is logged,
+   * never fatal, because the KB is already provisioned at `dest`.
+   * @param {string} dest - Absolute path to the provisioned KB.
+   * @returns {Promise<void>}
+   */
+  async #linkIntoDocuments(dest) {
+    const link = join(homedir(), "Documents", basename(dest));
+    if (await this.#exists(link)) {
+      this.#logger.info(`  Skipped ${link}: already exists`);
+      return;
+    }
+    try {
+      await this.#ensureDir(dirname(link));
+      await this.#fs.symlink(dest, link, "dir");
+      this.#logger.info(`  Linked ${link} -> ${dest}`);
+    } catch (err) {
+      this.#logger.info(`  Could not link into ~/Documents: ${err.message}`);
+    }
+  }
+
   /**
    * Update an existing knowledge base with the latest bundled files.
    * @param {string} targetPath

package/src/outpost.js

@@ -4,7 +4,7 @@
 //   fit-outpost                     Wake due agents once and exit
 //   fit-outpost daemon              Run continuously (poll every 60s)
 //   fit-outpost wake <agent>        Wake a specific agent immediately
-//   fit-outpost init <path>         Initialize a new knowledge base
+//   fit-outpost init [name]         Initialize a knowledge base by name (default: Team)
 //   fit-outpost update [path]       Update KB with latest CLAUDE.md, agents and skills (defaults to current directory)
 //   fit-outpost stop                Gracefully stop daemon and all running agents
 //   fit-outpost validate            Validate agent definitions exist
@@ -58,7 +58,7 @@ function buildDefinition(version) {
       },
       {
         name: "init",
-        args: "<path>",
+        args: "[name]",
         description: "Initialize a new knowledge base",
       },
       {
@@ -433,13 +433,20 @@ export async function run(runtime, version) {
       return 1;
     },
     init: async () => {
-      if (!args[0]) {
-        cli.usageError("missing required argument <path>");
+      // `init [name]` provisions a KB by name under the data home (default
+      // `Team`), never an arbitrary path — so the substrate cannot be
+      // steered back into a TCC-protected folder. An unsafe name is refused.
+      const name = args[0] ?? "Team";
+      let target;
+      try {
+        target = KBManager.kbPathForName(name);
+      } catch {
+        cli.usageError(`invalid KB name "${name}"`);
         return 2;
       }
       const tpl = await requireTemplateDir();
       if (tpl === null) return 1;
-      const result = await kbManager.init(args[0], tpl);
+      const result = await kbManager.init(target, tpl);
       if (!result.ok) {
         proc.stderr.write(result.error + "\n");
         return result.code;

package/src/privilege.js

@@ -0,0 +1,45 @@
+/**
+ * Privilege — resolve an agent's least-privilege execution level and map it to
+ * the hop-2 spawn disclaim flag.
+ *
+ * The level governs the macOS reach the daemon grants a woken agent. `full`
+ * keeps today's single-grant model (the child inherits `fit-outpost.app` as its
+ * responsible process, so Full Disk Access and Automation flow to it); a
+ * `restricted` agent is held responsible for itself, so those grants are not
+ * extended and it can reach only non-TCC-protected substrate.
+ *
+ * The level is mandatory and lives in the same user-only trust root as the
+ * spawn-env allow-set and the state roots, so an agent cannot raise its own
+ * level. Patterned on `posture.js` but with no `effective*` coercion and no
+ * default — a missing or unrecognised value throws.
+ */
+
+/** The two privilege levels, in declaration order. */
+export const PRIVILEGE_LEVELS = ["full", "restricted"];
+
+/**
+ * Resolve an agent's declared privilege level. The level is mandatory: a
+ * missing or unrecognised value throws — there is no default.
+ * @param {{ privilege?: string }} agent - One agent's config.
+ * @returns {"full"|"restricted"} The declared level.
+ * @throws {Error} when `agent.privilege` is not one of {@link PRIVILEGE_LEVELS}.
+ */
+export function resolvePrivilege(agent) {
+  const level = agent?.privilege;
+  if (!PRIVILEGE_LEVELS.includes(level)) {
+    throw new Error(
+      `invalid privilege "${level}"; expected one of ${PRIVILEGE_LEVELS.join(", ")}`,
+    );
+  }
+  return level;
+}
+
+/**
+ * Map a level to the hop-2 disclaim flag: `restricted` self-disclaims (`1`),
+ * `full` keeps the inherited responsible process (`0`).
+ * @param {"full"|"restricted"} level
+ * @returns {0|1}
+ */
+export function disclaimFor(level) {
+  return level === "restricted" ? 1 : 0;
+}

package/templates/.claude/agents/chief-of-staff.md

@@ -14,16 +14,18 @@ single briefing.
 
 ## Priorities
 
-`Knowledge/Priorities/` is the backbone of every briefing. Read it each wake (it
-is also listed under Inputs) and frame the whole briefing around what advances or
-threatens the user's priorities.
+`Knowledge/Priorities/` is the backbone of every briefing. Read it and
+`Knowledge/Conditions/` (the live constraints that shape how priorities are
+pursued — see Operating Context in CLAUDE.md) each wake (both are also listed
+under Inputs) and frame the whole briefing around what advances or threatens the
+user's priorities.
 
 - **Always consider them.** Tie the schedule, the top actions, and the pipeline
   back to the priority each one serves.
 - **Always escalate risks.** Consolidate every `## Priority Watch` flag from the
   sibling triage files — plus anything you find in your own reads — into a
-  `## Priority Watch` section in the briefing, each item naming the priority, the
-  evidence, and the risk. A signal that could contradict, block, or slow a
+  `## Priority Watch` section in the briefing, each item naming the priority,
+  the evidence, and the risk. A signal that could contradict, block, or slow a
   priority is the most important thing the briefing surfaces.
 
 ## Inputs
@@ -37,7 +39,7 @@ authoritative current-state summaries:
 - `~/.cache/fit/outpost/state/recruiter_triage.md`
 - `~/.cache/fit/outpost/state/head_hunter_triage.md`
 
-Plus directly: `Knowledge/Priorities/`, `Drafts/`,
+Plus directly: `Knowledge/Priorities/`, `Knowledge/Conditions/`, `Drafts/`,
 `~/.cache/fit/outpost/apple_calendar/`, and unchecked `- [ ]` items in
 `Knowledge/`.
 
@@ -64,7 +66,7 @@ and "Still Outstanding".
 
 ## Output
 
-```
+```text
 Decision: {morning/evening} briefing — {key insight about today}
 Action: Created Briefings/{YYYY-MM-DD}-{morning|evening}.md
 ```

package/templates/.claude/agents/concierge.md

@@ -18,11 +18,13 @@ recordings.
 
 ## Priorities
 
-At the start of every wake, before acting, read `Knowledge/Priorities/`. The
-user's priorities are the lens for all your work this wake.
+At the start of every wake, before acting, read `Knowledge/Priorities/` and
+`Knowledge/Conditions/` (which constrains them — see Operating Context in
+CLAUDE.md). The user's priorities are the lens for all your work this wake.
 
 - **Always consider them.** Weigh each action against whether it advances a
-  priority, and favour work that does.
+  priority, and favour work that does. Let the active conditions shape how you
+  act on it.
 - **Always flag risks.** When you encounter a chat, email, transcript, or any
   other signal that could **contradict, block, or slow** a priority, record it
   under a `## Priority Watch` heading in your triage report — name the priority,
@@ -53,7 +55,7 @@ over **anarlog-process** (catch-up work).
 
 After acting, emit exactly:
 
-```
+```text
 Decision: {what you observed and why you chose this action}
 Action: {what you did, e.g. "meeting-prep for 2pm with Sarah Chen"}
 Priority Watch: {priority at risk + one-line why, or "none"}

package/templates/.claude/agents/head-hunter.md

@@ -21,11 +21,13 @@ benchmark promising matches, and write prospect notes for the user to review.
 
 ## Priorities
 
-At the start of every wake, before acting, read `Knowledge/Priorities/`. The
-user's priorities are the lens for all your work this wake.
+At the start of every wake, before acting, read `Knowledge/Priorities/` and
+`Knowledge/Conditions/` (which constrains them — see Operating Context in
+CLAUDE.md). The user's priorities are the lens for all your work this wake.
 
 - **Always consider them.** Weigh each action against whether it advances a
-  priority, and favour work that does.
+  priority, and favour work that does. Let the active conditions shape how you
+  act on it.
 - **Always flag risks.** When you encounter a chat, email, transcript, or any
   other signal that could **contradict, block, or slow** a priority, record it
   under a `## Priority Watch` heading in your triage report — name the priority,
@@ -63,7 +65,7 @@ wake — the chief-of-staff reads it.
 
 ## Output
 
-```
+```text
 Decision: {source chosen and why}
 Action: {what was scanned, e.g. "scanned HN Who Wants to Be Hired March 2026, 47 posts"}
 Prospects: {N} new ({strong} strong, {moderate} moderate), {total} total

package/templates/.claude/agents/librarian.md

@@ -16,11 +16,13 @@ you process new data into the knowledge graph and keep everything organized.
 
 ## Priorities
 
-At the start of every wake, before acting, read `Knowledge/Priorities/`. The
-user's priorities are the lens for all your work this wake.
+At the start of every wake, before acting, read `Knowledge/Priorities/` and
+`Knowledge/Conditions/` (which constrains them — see Operating Context in
+CLAUDE.md). The user's priorities are the lens for all your work this wake.
 
 - **Always consider them.** Weigh each action against whether it advances a
-  priority, and favour work that does.
+  priority, and favour work that does. Let the active conditions shape how you
+  act on it.
 - **Always flag risks.** When you encounter a chat, email, transcript, or any
   other signal that could **contradict, block, or slow** a priority, record it
   under a `## Priority Watch` heading in your triage report — name the priority,
@@ -31,18 +33,20 @@ user's priorities are the lens for all your work this wake.
 
 Assess what needs processing:
 
-1.  Check for unprocessed synced files (mail and calendar data):
+1. Check for unprocessed synced files (mail and calendar data):
 
-        node .claude/skills/extract-entities/scripts/state.mjs check
+   ```text
+    node .claude/skills/extract-entities/scripts/state.mjs check
+   ```
 
-2.  Count existing knowledge graph entities:
+2. Count existing knowledge graph entities:
 
-    ls Knowledge/People/ Knowledge/Organizations/ Knowledge/Projects/
-    Knowledge/Topics/ Knowledge/Priorities/ 2>/dev/null | wc -l
+   ls Knowledge/People/ Knowledge/Organizations/ Knowledge/Projects/
+   Knowledge/Topics/ Knowledge/Priorities/ 2>/dev/null | wc -l
 
 Write triage results to `~/.cache/fit/outpost/state/librarian_triage.md`:
 
-```
+```text
 # Knowledge Triage — {YYYY-MM-DD HH:MM}
 ## Pending Processing
 - {count} unprocessed synced files
@@ -64,7 +68,7 @@ Choose the most valuable action:
 
 After acting, output exactly:
 
-```
+```text
 Decision: {what you observed and why you chose this action}
 Action: {what you did, e.g. "extract-entities on 7 files"}
 Priority Watch: {priority at risk + one-line why, or "none"}

package/templates/.claude/agents/postman.md

@@ -17,11 +17,13 @@ and Teams, triage what's new, take the most valuable action.
 
 ## Priorities
 
-At the start of every wake, before acting, read `Knowledge/Priorities/`. The
-user's priorities are the lens for all your work this wake.
+At the start of every wake, before acting, read `Knowledge/Priorities/` and
+`Knowledge/Conditions/` (which constrains them — see Operating Context in
+CLAUDE.md). The user's priorities are the lens for all your work this wake.
 
 - **Always consider them.** Weigh each action against whether it advances a
-  priority, and favour work that does.
+  priority, and favour work that does. Let the active conditions shape how you
+  act on it.
 - **Always flag risks.** When you encounter a chat, email, transcript, or any
   other signal that could **contradict, block, or slow** a priority, record it
   under a `## Priority Watch` heading in your triage report — name the priority,
@@ -54,7 +56,7 @@ email only.
 
 After acting, emit exactly:
 
-```
+```text
 Decision: {what you observed and why you chose this action}
 Action: {what you did, e.g. "draft-emails for thread 123"}
 Priority Watch: {priority at risk + one-line why, or "none"}

package/templates/.claude/agents/recruiter.md

@@ -22,11 +22,13 @@ assessment and recommendation references the standard.
 
 ## Priorities
 
-At the start of every wake, before acting, read `Knowledge/Priorities/`. The
-user's priorities are the lens for all your work this wake.
+At the start of every wake, before acting, read `Knowledge/Priorities/` and
+`Knowledge/Conditions/` (which constrains them — see Operating Context in
+CLAUDE.md). The user's priorities are the lens for all your work this wake.
 
 - **Always consider them.** Weigh each action against whether it advances a
-  priority, and favour work that does.
+  priority, and favour work that does. Let the active conditions shape how you
+  act on it.
 - **Always flag risks.** When you encounter a chat, email, transcript, or any
   other signal that could **contradict, block, or slow** a priority, record it
   under a `## Priority Watch` heading in your triage report — name the priority,
@@ -60,11 +62,12 @@ screen > sync. Stage 3 **never** triggers automatically — only on user request
 
 Triage state goes to `~/.cache/fit/outpost/state/recruiter_triage.md` every wake
 (the chief-of-staff reads it): needs-action by stage, recently processed
-candidates, pipeline totals by stage/track, aggregate diversity, retention flags.
+candidates, pipeline totals by stage/track, aggregate diversity, retention
+flags.
 
 ## Output
 
-```
+```text
 Decision: {observation and chosen action}
 Action: {e.g. "req-screen for John Smith against J060 forward-deployed"}
 Stage: {1 | 2 | sync | erasure}

package/templates/.claude/skills/anarlog-follow/references/coaching.md

@@ -6,7 +6,7 @@ Reference for `anarlog-follow` Phases 2 and 3.
 
 ### For interviews
 
-```
+```text
 Following: {Title}
 Type: {Interview type}
 Candidate: {Name} — {current role} at {employer}
@@ -27,7 +27,7 @@ Watching for: {specific signals at this interview stage}
 
 ### For general meetings
 
-```
+```text
 Following: {Title}
 Attendees: {names with roles}
 
@@ -66,7 +66,7 @@ Suggested topics:
 
 Output **only when actionable**. Each nudge: 1–3 lines max.
 
-```
+```text
 Probe deeper: {Name} mentioned {topic} — ask for a specific example
 Gap: screening flagged {skill} as uncertain. Try: "{question}"
 Confirmed: {Name} demonstrated {skill} at {level} — "{brief quote}"

package/templates/.claude/skills/anarlog-trim/SKILL.md

@@ -46,9 +46,11 @@ Run this skill:
 ### Step 0 — Validate the session
 
 1. Confirm the session directory exists:
-   ```
+
+   ```text
    ~/Library/Application Support/anarlog/sessions/{uuid}/
    ```
+
 2. Confirm `transcript.json` exists and has at least one transcript with words.
 3. Read `_meta.json` to get the session title for context.
 
@@ -132,7 +134,8 @@ json.dump(data, open(path, 'w'), indent=2)
 ```
 
 4. Print a summary:
-   ```
+
+   ```text
    Trimmed: {title}
      Before: {original_words} words, {original_duration}
      After:  {new_words} words, {new_duration}
@@ -147,11 +150,14 @@ people who did not consent to being recorded. The full audio file must be
 deleted to respect participant privacy.
 
 1. Delete the audio file:
+
    ```bash
    rm "~/Library/Application Support/anarlog/sessions/{uuid}/audio.mp3"
    ```
+
 2. Confirm deletion and inform the user:
-   ```
+
+   ```text
    Audio deleted: audio.mp3 removed (recording contained unconsented content beyond the meeting)
    ```
 

package/templates/.claude/skills/candidate-report/SKILL.md

@@ -50,7 +50,8 @@ before deciding whether to invest interview time.
 - [ ] Verdict class matches the overall assessment.
 - [ ] Report fits on a single A4 page (browser print preview).
 - [ ] CSS is inlined in the `<style>` block.
-- [ ] Footer shows the author name and role from `~/.cache/fit/outpost/state/identity.md`.
+- [ ] Footer shows the author name and role from
+      `~/.cache/fit/outpost/state/identity.md`.
 - [ ] Written as if the candidate will read it; no special-category data.
 
 </do_confirm_checklist>
@@ -61,7 +62,7 @@ before deciding whether to invest interview time.
 
 Read whatever exists for the candidate:
 
-```
+```text
 Knowledge/Candidates/{Name}/brief.md        # required
 Knowledge/Candidates/{Name}/screening.md    # if produced by req-screen
 Knowledge/Candidates/{Name}/interview-*.md  # if produced by req-assess
@@ -118,7 +119,7 @@ preview overflows, cut content.
 
 Save the completed HTML to:
 
-```
+```text
 Drafts/{Recipient}-{CandidateSurname}-Report.html
 ```
 

package/templates/.claude/skills/changelog/SKILL.md

@@ -11,8 +11,8 @@ teammates syncing the same filesystem can see what changed and why.
 
 This tracks **graph content** — notes under `Knowledge/People/`,
 `Organizations/`, `Projects/`, `Topics/`, `Candidates/`, `Priorities/`, and the
-other subdirectories. It does **not** track changes to instructions (`CLAUDE.md`,
-agents, skills) — that is the `upstream-instructions` skill's job.
+other subdirectories. It does **not** track changes to instructions
+(`CLAUDE.md`, agents, skills) — that is the `upstream-instructions` skill's job.
 
 ## Trigger
 
@@ -40,16 +40,16 @@ agents, skills) — that is the `upstream-instructions` skill's job.
 
 ## Ethics
 
-`Knowledge/` is shared with the team. Every entry obeys the KB's integrity rules:
-objective and factual, work-relevant, no personal judgments. Assume the person a
-note is about will read its changelog entry. Describe **what changed in the
-graph**, not opinions about the people in it.
+`Knowledge/` is shared with the team. Every entry obeys the KB's integrity
+rules: objective and factual, work-relevant, no personal judgments. Assume the
+person a note is about will read its changelog entry. Describe
+**what changed in the graph**, not opinions about the people in it.
 
 <do_confirm_checklist goal="Verify the changelog is accurate and shareable">
 
 - [ ] Exactly one `Knowledge/CHANGELOG.md`; no stray per-folder changelogs.
-- [ ] Every entry names its **Scope** — the specific note(s) or folder(s) touched,
-      by full path.
+- [ ] Every entry names its **Scope** — the specific note(s) or folder(s)
+      touched, by full path.
 - [ ] Each entry has **Who** (author, from identity), **What**, and **Why**.
 - [ ] Descriptions are specific enough to be useful (not "updated some notes").
 - [ ] Dates are the date the change was actually made, not guessed.
@@ -104,8 +104,8 @@ Scope lists every note touched.
 
 ### 4. Write the changelog
 
-Create or update `Knowledge/CHANGELOG.md` (newest first). Group entries under one
-heading per day; one bullet per logical change:
+Create or update `Knowledge/CHANGELOG.md` (newest first). Group entries under
+one heading per day; one bullet per logical change:
 
 ```markdown
 # Knowledge Changelog