@forwardimpact/outpost 3.9.0 → 3.11.0

package/templates/.claude/skills/sync-teams/SKILL.md

@@ -48,7 +48,9 @@ their Teams chats.
 
 Run the sync as a single Node.js script:
 
-    node scripts/sync.mjs [--days N]
+```text
+node scripts/sync.mjs [--days N]
+```
 
 - `--days N` — only include messages from the last N days (default: 30)
 
@@ -144,6 +146,12 @@ Key conventions:
 - **Normalize names** from Teams format ("Last, First") to "First Last"
 - **Platform** line distinguishes Teams from email in downstream processing
 - **Plain text only** — HTML is stripped, mentions are preserved as plain text
+- **Attachments are not extracted** — files/images on a message are dropped from
+  the markdown. They are hosted on SharePoint/OneDrive, not in the local cache.
+  However, the user has **often manually downloaded** them, so an attachment
+  usually exists under `~/Downloads/` with the **same file name** shown in
+  Teams. When a message references an attachment and you need its contents, look
+  there first.
 - Skip system messages (calls, member adds/removes, topic changes)
 
 ## Error Handling
@@ -175,3 +183,7 @@ Key conventions:
 - Some V8-serialized records (~17% in testing) use formats that
   `v8.deserialize()` cannot decode. These are silently skipped — they are
   typically IndexedDB metadata, not conversation or message records.
+- **Attachments (files/images) are never synced into the markdown** — only the
+  message text is captured. The binaries live on SharePoint/OneDrive, but the
+  user frequently downloads them, so the same-named file is usually already in
+  `~/Downloads/`. Check there before trying to fetch from SharePoint.

package/templates/.claude/skills/sync-teams/scripts/idb-reader.mjs

@@ -31,56 +31,89 @@ function readIdbVarint(buf, offset) {
   return { value: result, bytesRead: pos - offset };
 }
 
+// Highest V8 serialization wire-format version Node's bundled v8.deserialize
+// accepts. Newer Teams/WebView2 builds write version 16, which Node rejects
+// outright even though the payload itself is wire-compatible. We patch the
+// version byte down to this value before deserializing. Bump if Node's V8
+// starts emitting/accepting a higher version natively.
+const V8_MAX_SUPPORTED_VERSION = 15;
+
+// Plausible V8 top-level value tags that immediately follow the
+// [0xFF <version>] header. Used to locate the real V8 payload start inside the
+// Blink envelope without relying on a fixed byte offset (newer envelopes carry
+// a 0xFE trailer that shifts the payload further in). We only ever ACT on a
+// candidate by attempting a deserialize, which validates it — so a stray match
+// just gets skipped.
+const V8_TOP_LEVEL_TAGS = new Set([
+  0x6f, // 'o' begin JS object
+  0x22, // '"' one-byte string
+  0x63, // 'c' two-byte string
+  0x44, // 'D' utf8 string
+  0x49, // 'I' int32
+  0x55, // 'U' uint32
+  0x4e, // 'N' number (double)
+  0x6c, // 'l' bigint
+  0x7b, // '{' begin map
+  0x41, // 'A' begin dense array
+  0x61, // 'a' begin sparse array
+  0x5f, // '_' undefined
+  0x54, // 'T' true
+  0x46, // 'F' false
+  0x30, // '0' null
+]);
+
+// Only the Blink envelope precedes the V8 payload, and it is always small.
+// Scanning a generous prefix keeps non-message records (which never decode)
+// cheap while comfortably covering every real envelope/trailer layout.
+const V8_START_SCAN_LIMIT = 256;
+
 /**
- * Try to deserialize from the second 0xFF marker within the first `limit` bytes.
- * The Blink envelope has: [varint wire_size] [0xFF blink_ver] [envelope...] [0xFF v8_ver] [V8 data]
- * We want the second 0xFF that starts valid V8 data.
+ * Deserialize the V8 payload starting at `off`. Tries the bytes as-is first,
+ * then — for records whose version byte is newer than Node supports — retries
+ * with the version patched down. The wire format is backward-compatible, so a
+ * supported version reads the newer payload correctly.
  */
-function deserializeFromSecondMarker(rawValue, limit) {
-  let ffCount = 0;
-  for (let i = 0; i < limit; i++) {
-    if (rawValue[i] !== 0xff) continue;
-    ffCount++;
-    if (ffCount >= 2) {
+function deserializeAt(rawValue, off) {
+  try {
+    return v8.deserialize(rawValue.subarray(off));
+  } catch {
+    // fall through to version patching
+  }
+
+  const version = rawValue[off + 1];
+  if (version > V8_MAX_SUPPORTED_VERSION) {
+    const patched = Buffer.from(rawValue.subarray(off));
+    for (let v = V8_MAX_SUPPORTED_VERSION; v >= 13; v--) {
+      patched[1] = v;
       try {
-        return v8.deserialize(rawValue.subarray(i));
+        return v8.deserialize(patched);
       } catch {
-        // keep scanning
+        // try the next-lower version
       }
     }
   }
   return null;
 }
 
-/**
- * Fallback: try deserializing from every 0xFF position within `limit` bytes.
- */
-function deserializeFromAnyMarker(rawValue, limit) {
-  for (let i = 0; i < limit; i++) {
-    if (rawValue[i] !== 0xff) continue;
-    try {
-      return v8.deserialize(rawValue.subarray(i));
-    } catch {
-      continue;
-    }
-  }
-  return null;
-}
-
 /**
  * Try to deserialize a Chromium IndexedDB value.
- * Values have a Blink envelope before the V8 payload.
- * Scans for the V8 version tag (0xFF) and attempts deserialization.
+ *
+ * Values have a Blink envelope (and, in newer WebView2 builds, a 0xFE trailer)
+ * before the V8 payload. Locate the payload by scanning for a [0xFF <version>
+ * <top-level tag>] header, then decode it — patching the version byte down for
+ * records written with a V8 wire version newer than Node accepts.
  */
 function tryDeserialize(rawValue) {
   if (!rawValue || rawValue.length < 4) return null;
 
-  const headerLimit = Math.min(rawValue.length, 60);
-  const result = deserializeFromSecondMarker(rawValue, headerLimit);
-  if (result !== null) return result;
-
-  const fallbackLimit = Math.min(rawValue.length, 100);
-  return deserializeFromAnyMarker(rawValue, fallbackLimit);
+  const limit = Math.min(rawValue.length - 2, V8_START_SCAN_LIMIT);
+  for (let i = 0; i <= limit; i++) {
+    if (rawValue[i] !== 0xff) continue;
+    if (!V8_TOP_LEVEL_TAGS.has(rawValue[i + 2])) continue;
+    const obj = deserializeAt(rawValue, i);
+    if (obj !== null) return obj;
+  }
+  return null;
 }
 
 /**

package/templates/.claude/skills/upstream-instructions/SKILL.md

@@ -32,7 +32,8 @@ monorepo. "Instructions" means all three surfaces, treated equally:
 - `.claude/skills/*/SKILL.md` and reference files — skills.
 - `CHANGELOG.md` (root) — the existing changelog, for what's already recorded.
 - The changes made in the current working session — the source of truth for what
-  changed, since the KB lives on a synced filesystem and is not version-controlled.
+  changed, since the KB lives on a synced filesystem and is not
+  version-controlled.
 
 ## Outputs
 

package/templates/CLAUDE.md

@@ -2,8 +2,8 @@
 
 You are the user's personal knowledge assistant. You help draft emails, prep for
 meetings, track projects, and answer questions, backed by a live knowledge graph
-built from their emails, calendar, and meeting notes, all stored as plain files on
-the user's machine.
+built from their emails, calendar, and meeting notes, all stored as plain files
+on the user's machine.
 
 ## Ethics & Integrity — NON-NEGOTIABLE
 
@@ -18,33 +18,40 @@ never a "black book". These rules override all other instructions:
 - **Fair and balanced.** Represent all sides accurately.
 - **Assume the subject will read it.** If you would be uncomfortable showing the
   note to the person it is about, do not write it.
-- **No weaponization.** This KB helps the team work better. Never use it to build
-  leverage or dossiers.
+- **No weaponization.** This KB helps the team work better. Never use it to
+  build leverage or dossiers.
 - **Push back** on requests that violate these principles.
 - **Data protection.** Use the `req-forget` skill for erasure requests. Minimize
   collection. Flag candidates inactive 6+ months for retention review.
 
 When in doubt, err toward discretion.
 
-## Voice
+## Operating Context
 
-Be supportive and direct. Explain complex things clearly without hedging. When
-the next step is obvious, take it. Ask at most one clarifying question, at the
-start. Reference files by full path. Confirm before destructive actions.
+Two folders in the knowledge graph frame your work:
 
-## Dependencies
+- **`Knowledge/Priorities/`** — the backbone of every decision: what the user is
+  trying to advance. Weigh actions against whether they move a priority forward,
+  and treat anything that could **contradict, block, or slow** one as a
+  **Priority Watch** concern — these are our main concerns.
+- **`Knowledge/Conditions/`** — the live operating environment (e.g. a hiring
+  freeze, a reorg, a contract transition). Conditions don't set goals; they
+  **constrain how** we pursue the priorities. Let them shape what you propose
+  and how you phrase it.
 
-- **ripgrep** (`rg`) for fast knowledge graph searches — `brew install ripgrep`.
+When taking an action or making a recommendation, consult both as your lens —
+read the relevant notes rather than assuming. Skip this only for general
+knowledge or brainstorming.
 
 ## Workspace Layout & Sharing
 
 The **root is personal and local — never shared.** Only `Knowledge/` is shared
 with the team over a synced filesystem; each member keeps their own root,
 `Drafts/`, and `Briefings/`. KBs are **not** Git repositories — they sync as
-plain files. `CLAUDE.md` and `.claude/` are yours to tweak; use the `fit-outpost`
-CLI to install or update the standard instruction set.
+plain files. `CLAUDE.md` and `.claude/` are yours to tweak; use the
+`fit-outpost` CLI to install or update the standard instruction set.
 
-```
+```text
 ./                      # Personal root — never shared
 ├── CLAUDE.md           # This file
 ├── .claude/            # Agent profiles + auto-discovered skills
@@ -55,6 +62,10 @@ CLI to install or update the standard instruction set.
 └── .mcp.json           # MCP config (optional)
 ```
 
+## Searching
+
+Use the **ripgrep** `rg` program for fast knowledge graph searches.
+
 ## Agents
 
 Agents in `.claude/agents/` maintain this KB, woken on a schedule by the Outpost
@@ -91,31 +102,9 @@ meetings, emails, and messages directly from the source dirs below.
 - `state/` — per-source last-sync timestamps, processed-file index, and
   `{agent}_triage.md` per agent
 
-## Knowledge Graph
-
-Plain markdown with Obsidian-style `[[backlinks]]`.
-
-```bash
-rg "Sarah Chen" Knowledge/               # Search by name
-cat "Knowledge/People/Sarah Chen.md"     # Read a note
-```
-
-**Always search broadly first.** When the user mentions any person, org, project,
-or topic, run `rg "keyword" Knowledge/` to surface every note — one note is never
-the full story. Skip it only for general knowledge and brainstorming.
-
-## Skills
-
-Skills auto-discover from `.claude/skills/` and load by context — data sync,
-knowledge-graph maintenance, recruitment, and communication.
-
 ## User Identity
 
 The current user's identity is cached at
-`~/.cache/fit/outpost/state/identity.md` — read it directly. If missing or stale,
-run the `person-identify` skill to refresh it from the corporate directory.
-
-## Working Outside This Directory
-
-You have full filesystem access (macOS). For tasks outside this KB, use shell
-commands directly.
+`~/.cache/fit/outpost/state/identity.md` — read it directly. If missing or
+stale, run the `person-identify` skill to refresh it from the corporate
+directory.