@forwardimpact/outpost 3.9.0 → 3.11.0

package/templates/.claude/skills/deck-review/assets/slide-annotator.js

@@ -13,6 +13,11 @@
  * (b) resolve each highlight to its SOURCE line/column + context lines by
  * reading the page’s own source file. No build step, no server, no deps.
  *
+ * The connected folder is remembered across reloads (the directory handle is
+ * stored in IndexedDB). On reload it reconnects silently if the browser still
+ * grants permission; otherwise the button reads “Reconnect folder” and one
+ * click re-grants access without re-picking the folder.
+ *
  * Optional host hook: if the page defines `window.deckGoto(index)` the panel’s
  * “Go” buttons will navigate to the right slide. Without it, the tool still
  * works (it falls back to scrollIntoView).
@@ -60,7 +65,8 @@
   /* ----------------------------- state ------------------------------------ */
   var state = loadLocal();        // { version, tool, target, annotations:[] }
   var review = false;
-  var dirHandle = null;           // File System Access directory handle
+  var dirHandle = null;           // File System Access directory handle (active)
+  var rememberedHandle = null;    // handle from a prior session, awaiting re-grant
   var sourceText = null;          // page source (for line/column)
   var pending = null;             // annotation awaiting note + confirm
   var ui = {};                    // DOM refs
@@ -150,6 +156,7 @@
   ui.count = ui.panel.querySelector(".sa-count");
   ui.status = ui.panel.querySelector(".sa-status");
   ui.list = ui.panel.querySelector(".sa-list");
+  ui.connectBtn = ui.panel.querySelector('[data-act="connect"]');
   ui.note = ui.pop.querySelector("textarea");
   var onlyThisSlide = false;
 
@@ -435,28 +442,105 @@
     if (ui.count) ui.count.textContent = state.annotations.length;
   }
 
+  /* Persist the connected directory handle across reloads. FileSystemHandles are
+   * structured-cloneable, so they live in IndexedDB (localStorage is strings
+   * only). Re-granting read/write permission after a reload needs a user
+   * gesture, so a remembered folder reconnects with one click via the same
+   * "Connect folder" button rather than the full directory picker. Keyed by
+   * cfg.target so distinct decks in a folder don't clobber each other. */
+  var IDB_NAME = "slide-annotator", IDB_STORE = "handles";
+  function idbOpen() {
+    return new Promise(function (resolve, reject) {
+      if (!window.indexedDB) { reject(new Error("no-idb")); return; }
+      var req = indexedDB.open(IDB_NAME, 1);
+      req.onupgradeneeded = function () { req.result.createObjectStore(IDB_STORE); };
+      req.onsuccess = function () { resolve(req.result); };
+      req.onerror = function () { reject(req.error); };
+    });
+  }
+  function idbGet(key) {
+    return idbOpen().then(function (db) {
+      return new Promise(function (resolve, reject) {
+        var r = db.transaction(IDB_STORE, "readonly").objectStore(IDB_STORE).get(key);
+        r.onsuccess = function () { resolve(r.result || null); };
+        r.onerror = function () { reject(r.error); };
+      });
+    }).catch(function () { return null; });
+  }
+  function idbSet(key, val) {
+    return idbOpen().then(function (db) {
+      return new Promise(function (resolve, reject) {
+        var tx = db.transaction(IDB_STORE, "readwrite");
+        tx.objectStore(IDB_STORE).put(val, key);
+        tx.oncomplete = function () { resolve(true); };
+        tx.onerror = function () { reject(tx.error); };
+      });
+    }).catch(function () { return false; });
+  }
+
+  function updateConnectLabel() {
+    if (!ui.connectBtn) return;
+    ui.connectBtn.textContent = dirHandle ? "Folder connected"
+      : rememberedHandle ? "Reconnect folder" : "Connect folder";
+  }
+
+  // Adopt a (freshly picked or re-granted) handle: link source, load any
+  // sidecar, and remember it for next time. Shared by connect and restore.
+  async function adoptFolder(handle) {
+    dirHandle = handle;
+    // read page source → enables source line/column resolution
+    try {
+      var fh = await dirHandle.getFileHandle(cfg.target);
+      sourceText = await (await fh.getFile()).text();
+      state.annotations.forEach(function (a) { a.source = locateInSource(a); });
+    } catch (e) { sourceText = null; setStatus("Connected, but '" + cfg.target + "' not found in folder — line numbers unavailable."); }
+    // load an existing sidecar if present
+    try {
+      var sh = await dirHandle.getFileHandle(SIDECAR);
+      mergeLoaded(JSON.parse(await (await sh.getFile()).text()));
+    } catch (e) { /* none yet */ }
+    await idbSet(cfg.target, dirHandle);
+    rememberedHandle = null;
+    updateConnectLabel();
+    persistLocal(); renderPanel(); renderHighlights();
+    setStatus("Connected. Saving to " + SIDECAR + (sourceText ? " · source linked" : ""));
+  }
+
   async function connectFolder() {
+    // Prefer a folder remembered from a prior session: re-granting permission is
+    // a single click (this click IS the required user gesture), no picker.
+    if (rememberedHandle) {
+      try {
+        var perm = await rememberedHandle.requestPermission({ mode: "readwrite" });
+        if (perm === "granted") { await adoptFolder(rememberedHandle); return; }
+      } catch (e) { /* fall through to the picker */ }
+      rememberedHandle = null; updateConnectLabel();
+    }
     if (!window.showDirectoryPicker) { setStatus("Folder access unsupported in this browser. Use Save (downloads the JSON)."); return; }
     try {
-      dirHandle = await window.showDirectoryPicker({ mode: "readwrite" });
-      // read page source → enables source line/column resolution
-      try {
-        var fh = await dirHandle.getFileHandle(cfg.target);
-        sourceText = await (await fh.getFile()).text();
-        state.annotations.forEach(function (a) { a.source = locateInSource(a); });
-      } catch (e) { sourceText = null; setStatus("Connected, but '" + cfg.target + "' not found in folder — line numbers unavailable."); }
-      // load an existing sidecar if present
-      try {
-        var sh = await dirHandle.getFileHandle(SIDECAR);
-        mergeLoaded(JSON.parse(await (await sh.getFile()).text()));
-      } catch (e) { /* none yet */ }
-      persistLocal(); renderPanel(); renderHighlights();
-      setStatus("Connected. Saving to " + SIDECAR + (sourceText ? " · source linked" : ""));
+      await adoptFolder(await window.showDirectoryPicker({ mode: "readwrite" }));
     } catch (e) {
       if (e && e.name !== "AbortError") setStatus("Folder access blocked (" + e.name + "). Use Save to download the JSON instead.");
     }
   }
 
+  // On load, try to restore a previously connected folder. queryPermission needs
+  // no gesture; if it's still "granted" we reconnect silently. If it's "prompt",
+  // we keep the handle so the next "Connect folder" click reconnects with one
+  // grant dialog (no picker). Handles cleared/denied storage are ignored.
+  function restoreFolder() {
+    idbGet(cfg.target).then(function (handle) {
+      if (!handle || typeof handle.queryPermission !== "function") return;
+      handle.queryPermission({ mode: "readwrite" }).then(function (perm) {
+        if (perm === "granted") { adoptFolder(handle); }
+        else {
+          rememberedHandle = handle; updateConnectLabel();
+          if (review) setStatus("Folder '" + cfg.target + "' remembered — click Reconnect folder.");
+        }
+      }).catch(function () {});
+    });
+  }
+
   async function saveDisk() {
     if (sourceText) state.annotations.forEach(function (a) { if (!a.source) a.source = locateInSource(a); });
     var json = JSON.stringify(serialize(), null, 2);
@@ -591,4 +675,5 @@
   };
 
   updateCount();
+  restoreFolder();
 })();

package/templates/.claude/skills/doc-create/SKILL.md

@@ -34,22 +34,23 @@ submission, brief, or any multi-page PDF that is not a slide deck.
 
 ## Workflow
 
-1.  Check `Knowledge/` for relevant context about the company, product, team,
-    projects, or people mentioned.
-2.  Ensure Playwright is installed:
-    `bun install playwright && bunx playwright install chromium`
-3.  Create a self-contained HTML file with all CSS inlined. The HTML must handle
-    its own page layout — see **HTML Document Rules** below.
-4.  Run the conversion script:
-
-        node .claude/skills/doc-create/scripts/convert-to-pdf.mjs <input.html> [output.pdf]
-
-    If output is omitted, the PDF is written alongside the HTML file with the
-    same name.
-
-5.  Read the PDF back to visually verify it renders correctly. Check each page
-    for overflow, clipped content, and correct page breaks. Fix and re-render if
-    needed.
+1. Check `Knowledge/` for relevant context about the company, product, team,
+   projects, or people mentioned.
+2. Ensure Playwright is installed:
+   `bun install playwright && bunx playwright install chromium`
+3. Create a self-contained HTML file with all CSS inlined. The HTML must handle
+   its own page layout — see **HTML Document Rules** below.
+4. Run the conversion script:
+
+   ```text
+    node .claude/skills/doc-create/scripts/convert-to-pdf.mjs <input.html> [output.pdf]
+   ```
+
+   If output is omitted, the PDF is written alongside the HTML file with the
+   same name.
+5. Read the PDF back to visually verify it renders correctly. Check each page
+   for overflow, clipped content, and correct page breaks. Fix and re-render if
+   needed.
 
 **Do NOT show HTML code to the user. Just create the PDF and deliver it.**
 

package/templates/.claude/skills/extract-entities/SKILL.md

@@ -41,8 +41,9 @@ under `Knowledge/`. The core knowledge-graph builder.
   auto-created.
 - `Knowledge/Conditions/` — created when cross-cutting patterns are detected, or
   updated.
-- `Knowledge/Roles/`, `Knowledge/Candidates/*/brief.md` — enriched with inferred
-  metadata.
+- `Knowledge/Roles/*.md`, `Knowledge/Candidates/*/brief.md` — enriched with
+  inferred metadata. New role stubs created with `**Status:** open`; update to
+  `**Status:** closed` when a role closes.
 - `~/.cache/fit/outpost/state/graph_processed` — updated.
 
 <do_confirm_checklist goal="Verify the batch produced clean, linked,
@@ -76,7 +77,8 @@ writes.
 ### 0. Load context and pick the batch
 
 Read the user's identity from `~/.cache/fit/outpost/state/identity.md` (run the
-`person-identify` skill first if it is missing or stale). Find new/changed files:
+`person-identify` skill first if it is missing or stale). Find new/changed
+files:
 
 ```bash
 node scripts/state.mjs check
@@ -151,7 +153,8 @@ filler or meta-commentary.
   domain-lead inference):
   [references/recruitment.md](references/recruitment.md).
 - **Priority links** (Step 7c): rules in
-  [references/links.md](references/links.md#priorities-step-7c). **Never auto-create.**
+  [references/links.md](references/links.md#priorities-step-7c).
+  **Never auto-create.**
 - **Conditions** (cross-cutting states affecting ≥ 3 entities):
   [references/conditions.md](references/conditions.md).
 

package/templates/.claude/skills/extract-entities/references/recruitment.md

@@ -3,6 +3,13 @@
 Reference for `extract-entities` Step 7b. Enrich `Knowledge/Roles/` and
 `Knowledge/Candidates/` with metadata that no single source carries.
 
+All Role files are flat in `Knowledge/Roles/`. The `**Status:**` field
+distinguishes:
+
+- **`Status: open`** — active openings (use for new candidates and table
+  rebuilds).
+- **`Status: closed`** — completed/withdrawn roles (read-only).
+
 ## Requisition number detection
 
 Scan email subjects and bodies for requisition numbers (e.g. 7-digit Workday
@@ -10,9 +17,12 @@ IDs).
 
 1. `ls Knowledge/Roles/ | grep "{req_number}"` — does a Role file exist?
 2. **No file:** create a stub using the Role-stub template in `req-track` Step
-   0b. Search `rg "{req_number}" Knowledge/` for context to enrich it.
-3. **File exists:** check whether the email provides new metadata (hiring
-   manager, recruiter, locations) and update the Role file.
+   0b, with `**Status:** open`. Search `rg "{req_number}" Knowledge/` for
+   context to enrich it.
+3. **File exists:** check the `**Status:**` field. If `open`, check whether the
+   email provides new metadata (hiring manager, recruiter, locations) and update
+   the Role file. If `closed`, link for historical reference only; do not add
+   new candidates or rebuild tables.
 
 ## Hiring manager — calendar inference
 

package/templates/.claude/skills/meeting-prep/SKILL.md

@@ -25,9 +25,11 @@ meetings.
 - `Knowledge/People/*.md` — attendee context
 - `Knowledge/Organizations/*.md` — company context
 - `Knowledge/Projects/*.md` — project context
-- `Knowledge/Priorities/*.md` — active priorities and strategic context for framing
+- `Knowledge/Priorities/*.md` — active priorities and strategic context for
+  framing
 - `Knowledge/Candidates/*/brief.md` — candidate context (for interview meetings)
-- `Knowledge/Roles/*.md` — role/requisition context (for interview meetings)
+- `Knowledge/Roles/*.md` — role/requisition context (for interview meetings);
+  check the `**Status:**` field to distinguish active from historical reqs
 
 ## Outputs
 
@@ -144,7 +146,7 @@ When preparing for interview meetings (title contains "Interview", "Screening",
 
 1. **Read the candidate brief:** `Knowledge/Candidates/{Name}/brief.md`
 2. **Read the Role file:** Look up the `Req` field and read the corresponding
-   `Knowledge/Roles/*.md` file.
+   `Knowledge/Roles/*.md` file; check the `**Status:**` field for context.
 3. **Include in the briefing:**
    - Candidate's current status, skills, and screening recommendation
    - Role context: hiring manager, domain lead, remaining positions

package/templates/.claude/skills/organize-files/SKILL.md

@@ -61,7 +61,9 @@ Run when the user asks to find, organize, clean up, or tidy files on their Mac.
 
 Get an overview of both directories:
 
-    node scripts/summarize.mjs
+```text
+node scripts/summarize.mjs
+```
 
 ## Finding Files
 
@@ -79,8 +81,10 @@ find ~/Desktop -maxdepth 1 \( -name "Screenshot*" -o -name "Screen Shot*" \)
 Organize a directory into type-based subdirectories (Documents, Images,
 Archives, Installers, Screenshots):
 
-    node scripts/organize-by-type.mjs ~/Downloads
-    node scripts/organize-by-type.mjs ~/Desktop
+```text
+node scripts/organize-by-type.mjs ~/Downloads
+node scripts/organize-by-type.mjs ~/Desktop
+```
 
 The script creates subdirectories and moves matching files. It does NOT delete
 anything.
@@ -106,7 +110,7 @@ After organizing, collect the paths of document files and invoke the
 
 **Plan:**
 
-```
+```text
 Organization Plan: Desktop & Downloads Cleanup
 
 Found 47 files to organize:
@@ -123,7 +127,7 @@ Should I proceed?
 
 **Results:**
 
-```
+```text
 Organization Complete
 
 Moved 47 files:

package/templates/.claude/skills/person-identify/SKILL.md

@@ -98,7 +98,7 @@ Key attributes returned (names per Active Directory schema):
 
 - To look up **someone else**, use the sibling `person-lookup` skill — it takes
   free-text input (email or name), searches the Global Catalog forest-wide
-  (`ldap://$dc:3268 -b ''`), handles multiple matches, and does **not** touch the
-  identity cache.
+  (`ldap://$dc:3268 -b ''`), handles multiple matches, and does **not** touch
+  the identity cache.
 - Not Active Directory? The same `ldapsearch -Y GSSAPI` shape works against any
   Kerberos-backed LDAP directory; only the attribute names differ.

package/templates/.claude/skills/person-lookup/SKILL.md

@@ -86,9 +86,9 @@ The argument is free text: an email, a full name, or just a surname.
   since the OU convention is organization-specific. Narrow with an email for an
   exact hit.
 - **Silent partial results.** Under load the directory occasionally returns an
-  entry's DN with no attributes (exit 0, no error). Every attribute fetch retries
-  with backoff, so a throttled response never masquerades as a person with a
-  blank title or email.
+  entry's DN with no attributes (exit 0, no error). Every attribute fetch
+  retries with backoff, so a throttled response never masquerades as a person
+  with a blank title or email.
 - **No cache.** This skill prints and exits. It never touches
   `~/.cache/fit/outpost/state/identity.md` — that file is owned solely by
   `person-identify`.

package/templates/.claude/skills/req-decide/SKILL.md

@@ -39,7 +39,8 @@ This is **Stage 3** of the three-stage pipeline:
 - Standard data via `fit-pathway`.
 - `Knowledge/Candidates/Insights.md` — cross-candidate context.
 - `Knowledge/Roles/*.md` — the candidate's requisition (positions, hiring
-  manager, domain lead).
+  manager, domain lead). Check the `**Status:**` field to distinguish active
+  from historical reqs.
 - `Knowledge/Priorities/*.md` — strategic context.
 - Other active candidates at the same level — relative positioning.
 
@@ -118,7 +119,8 @@ ls Knowledge/Roles/ | grep "{req_number}"
 cat "Knowledge/Roles/{matching file}"
 ```
 
-Capture remaining positions, hiring manager, domain lead, goal alignment, other
+Check the `**Status:**` field. Capture remaining positions, hiring manager,
+domain lead, goal alignment, other
 candidates on the same req, and channel (hr / vendor). Frame the recommendation
 in terms of strategic impact.
 

package/templates/.claude/skills/req-forget/references/report-template.md

@@ -62,6 +62,6 @@ rg "{Name}" Knowledge/ ~/.cache/fit/outpost/
 
 Expected: no matches except this erasure report.
 
-```
+```text
 
 ```

package/templates/.claude/skills/req-scan/references/fallbacks.md

@@ -18,7 +18,7 @@ limits.
 
 Search by skill + availability:
 
-```
+```text
 WebFetch URL: https://api.github.com/search/users?q=%22data+engineering%22+%22open+to+work%22&per_page=30&sort=joined&order=desc
 WebFetch URL: https://api.github.com/search/users?q=%22full+stack%22+%22available+for+hire%22&per_page=30&sort=joined&order=desc
 WebFetch URL: https://api.github.com/search/users?q=%22devops%22+%22looking+for%22&per_page=30&sort=joined&order=desc
@@ -26,7 +26,7 @@ WebFetch URL: https://api.github.com/search/users?q=%22devops%22+%22looking+for%
 
 Search repos with README signals:
 
-```
+```text
 WebFetch URL: https://api.github.com/search/repositories?q=%22hire+me%22+in:readme&sort=updated&order=desc&per_page=10
 ```
 
@@ -38,7 +38,7 @@ Manchester, Edinburgh.
 Try broader tags: `jobsearch`, `career`, `remotework`, `job`, `hiring`. Or pull
 from a tag and filter by title/description:
 
-```
+```text
 WebFetch URL: https://dev.to/api/articles?tag=career&per_page=25
 ```
 

package/templates/.claude/skills/req-scan/references/sources.md

@@ -6,14 +6,14 @@ Reference for `req-scan` Step 2 (fetch & scan). One source per wake cycle.
 
 Monthly thread, posted on the 1st.
 
-```
+```text
 WebFetch URL: https://hn.algolia.com/api/v1/search?query=%22Who+wants+to+be+hired%22&tags=ask_hn&hitsPerPage=5
 ```
 
 The first hit whose title matches "Who wants to be hired?" with `created_at` in
 the current or previous month is the target thread.
 
-```
+```text
 WebFetch URL: https://hn.algolia.com/api/v1/items/{objectID}
 ```
 
@@ -34,7 +34,7 @@ WebFetch URL: https://hn.algolia.com/api/v1/items/{objectID}
 
 Search by location (rotate one query per wake):
 
-```
+```text
 WebFetch URL: https://api.github.com/search/users?q=%22open+to+work%22+location:UK&per_page=30&sort=joined&order=desc
 WebFetch URL: https://api.github.com/search/users?q=%22open+to+work%22+location:Europe&per_page=30&sort=joined&order=desc
 WebFetch URL: https://api.github.com/search/users?q=%22looking+for+work%22+location:remote&per_page=30&sort=joined&order=desc
@@ -47,7 +47,7 @@ Alternate bio phrases to rotate across wakes: `"available for hire"`,
 
 Fetch each promising candidate's full profile:
 
-```
+```text
 WebFetch URL: https://api.github.com/users/{login}
 ```
 
@@ -60,7 +60,7 @@ profiles per wake (1 search + 5 profile fetches = 6 requests).
 
 ## 3. dev.to
 
-```
+```text
 WebFetch URL: https://dev.to/api/articles?tag=opentowork&per_page=25
 WebFetch URL: https://dev.to/api/articles?tag=lookingforwork&per_page=25
 ```

package/templates/.claude/skills/req-screen/SKILL.md

@@ -39,7 +39,8 @@ This is **Stage 1** of a three-stage hiring pipeline:
 - Target role (optional).
 - Existing `Knowledge/Candidates/{Name}/brief.md`, if any.
 - `Knowledge/Roles/*.md` matching the candidate's `Req` (provides `Level`,
-  `Discipline`, `Hiring manager`, `Domain lead`).
+  `Discipline`, `Hiring manager`, `Domain lead`, and the `**Status:**` field).
+  Look up by Req number or filename substring.
 
 ## Outputs
 
@@ -82,7 +83,8 @@ cat "Knowledge/Roles/{matching file}"
 
 Use the Role's `Level` and `Discipline` as the target unless the user specified
 a different target. Capture `Hiring manager` and `Domain lead` for the screening
-header.
+header. Note the `**Status:**` field, but don't let historical (`closed`) roles
+block screening of still-active candidates.
 
 If no target is available, estimate one using the level heuristics in
 [references/rubric.md](references/rubric.md#level-estimation-heuristics).

package/templates/.claude/skills/req-track/SKILL.md

@@ -29,7 +29,8 @@ pipeline from scattered email threads.
 - `~/.cache/fit/outpost/apple_mail/attachments/` — CV/resume attachments.
 - `~/.cache/fit/outpost/apple_calendar/*.json` — calendar events (for
   cross-source inference).
-- `Knowledge/Roles/*.md` — open role/requisition files (metadata inheritance).
+- `Knowledge/Roles/*.md` — role/requisition files (check the `**Status:**`
+  field: `open` for active roles, `closed` for historical).
 - `~/.cache/fit/outpost/state/graph_processed` — processed-file index (shared
   with `extract-entities`).
 - `~/.cache/fit/outpost/state/identity.md` — user identity for self-exclusion
@@ -40,8 +41,8 @@ pipeline from scattered email threads.
 - `Knowledge/Candidates/{Full Name}/brief.md` — candidate profile note.
 - `Knowledge/Candidates/{Full Name}/CV.pdf` (or `CV.docx`) — local CV copy.
 - `Knowledge/Candidates/{Full Name}/headshot.jpeg` — candidate photo.
-- `Knowledge/Roles/*.md` — created/updated role files (Candidates tables
-  rebuilt).
+- `Knowledge/Roles/*.md` — role files created/updated; the `**Status:**` field
+  determines visibility (open/closed).
 - `~/.cache/fit/outpost/state/graph_processed` — updated with processed threads.
 
 <do_confirm_checklist goal="Verify candidate processing batch is complete and
@@ -71,8 +72,8 @@ Process **10 files per run**.
 ### 1. Load context and pick the batch
 
 Read the user's name, email, and domain from
-`~/.cache/fit/outpost/state/identity.md` (run the `person-identify` skill first if
-it is missing or stale). List new or changed source files:
+`~/.cache/fit/outpost/state/identity.md` (run the `person-identify` skill first
+if it is missing or stale). List new or changed source files:
 
 ```bash
 node .claude/skills/extract-entities/scripts/state.mjs check
@@ -94,21 +95,24 @@ links.
 
 ### 3. Sync `Knowledge/Roles/`
 
-This keeps role metadata current and enables inheritance.
+Role files are flat here; the `**Status:**` field is `open` or `closed`.
 
 1. Read each Role file's Info block to map Req → Role file path, Hiring manager,
-   Domain lead, recruiter, Channel.
-2. Find Reqs referenced by candidate briefs but missing a Role file:
-   `rg "^\*\*Req:\*\*" Knowledge/Candidates/*/brief.md`. For each missing Req,
-   create a stub using the **Role file stub** in
-   [references/templates.md](references/templates.md), then enrich by searching
-   the graph: `rg "{req_number}" Knowledge/`.
-3. Rebuild each Role file's `## Candidates` table by scanning briefs:
+   Domain lead, recruiter, Channel. Look up by filename substring so a req-less
+   role stays findable: `ls Knowledge/Roles/ | grep "{partial_name_or_req}"`.
+2. Find Reqs in candidate briefs missing a Role file:
+   `rg "^\*\*Req:\*\*" Knowledge/Candidates/*/brief.md`. Check all Role files
+   first; for a genuinely missing open role, create a stub with `**Status:**
+   open` using the **Role file stub** in
+   [references/templates.md](references/templates.md), then enrich:
+   `rg "{req_number}" Knowledge/`.
+3. Rebuild each **open** Role file's `## Candidates` table by scanning briefs:
    `rg -l "Req:.*{req_number}" Knowledge/Candidates/*/brief.md`. Use the **Role
-   Candidates table** format from `references/templates.md`. Sort by First seen,
-   newest first.
+   Candidates table** format from `references/templates.md`, newest first.
 4. If a Role file has a hiring manager but no domain lead, walk the
    `**Reports to:**` chain in `Knowledge/People/` to a VP or senior leader.
+5. When a role closes (filled, cancelled, or frozen 6+ months), set its
+   `**Status:**` field to `closed` — only on a clear signal.
 
 ### 4. Identify recruitment threads
 

package/templates/.claude/skills/req-track/references/fields.md

@@ -43,8 +43,10 @@ Field map and resolution rules for Step 2 of `req-track`.
 
 Stop at the first match:
 
-1. **Req-first inheritance** — look up `Knowledge/Roles/*.md` for the matching
-   Req; inherit Hiring manager and Domain lead from the Role file.
+1. **Req-first inheritance** — search `Knowledge/Roles/` for a file matching the
+   Req number or role description (use filename substring lookup for req-less
+   roles); check the `**Status:**` field (open/closed), then inherit Hiring
+   manager and Domain lead from the Role file.
 2. **Calendar inference** —
    `rg -l "{Candidate Name}" ~/.cache/fit/outpost/apple_calendar/`. The non-user
    organizer of an interview event is likely the hiring manager.

package/templates/.claude/skills/req-workday/SKILL.md

@@ -38,7 +38,8 @@ integrate with the `req-track` pipeline format.
 
 - `Knowledge/Candidates/{Clean Name}/brief.md` — candidate profile.
 - `Knowledge/Candidates/{Clean Name}/CV.md` — resume text as markdown.
-- `Knowledge/Roles/{Req ID} — {Title}.md` — created or updated.
+- `Knowledge/Roles/{Req ID} — {Title}.md` — created or updated with
+  `**Status:** open`. Update to `**Status:** closed` when the role closes.
 - Updated existing briefs when a candidate already exists.
 
 <do_confirm_checklist goal="Verify the Workday import is consistent with
@@ -96,7 +97,8 @@ header indices, name annotations) are in
 ls Knowledge/Roles/ | grep "{Req ID}"
 ```
 
-Use the **Role file stub** in
+New role files go in `Knowledge/Roles/` with `**Status:** open`. Use the
+**Role file stub** in
 [references/templates.md](references/templates.md). Resolve the domain lead by:
 
 1. `rg "{Req ID}" Knowledge/` — look in project timelines, People notes, Topics

package/templates/.claude/skills/req-workday/references/status-mapping.md

@@ -30,7 +30,7 @@ Empty or unrecognized step → default to `new`.
 The raw `step` value is always preserved in the parser's JSON output and must be
 stored in the candidate brief's `## Pipeline` section, e.g.
 
-```
+```text
 - **2026-02-10**: Applied via LinkedIn — Step: Manager Request to Move Forward (HS)
 ```
 

package/templates/.claude/skills/req-workday/references/templates.md

@@ -5,13 +5,15 @@ Reference templates for `req-workday` Steps 1b, 4, and 5.
 ## Role file stub
 
 Use when no Role file exists for the requisition. Filename:
-`Knowledge/Roles/{Req ID} — {Short Title}.md`.
+`Knowledge/Roles/{Req ID} — {Short Title}.md`. The `**Status:**` field
+(`open`/`closed`) is updated in place — never move files.
 
 ```markdown
 # {Requisition Title}
 
 ## Info
 **Req:** {Req ID}
+**Status:** open
 **Title:** {Full title from export}
 **Level:** {Infer from title: "Principal" → J100, "Staff" → J090, "Director" → J100 M-track, "Senior" → J070}
 **Track:** {P-track for IC roles, M-track for Director/Manager roles}

package/templates/.claude/skills/sync-apple-calendar/SKILL.md

@@ -41,7 +41,9 @@ Run the sync as a single Node.js script with embedded SQLite. This avoids N+1
 process invocations (one per event for attendees) and handles all data
 transformation in one pass:
 
-    node scripts/sync.mjs [--days N]
+```text
+node scripts/sync.mjs [--days N]
+```
 
 - `--days N` — how many days back to sync (default: 30)
 
@@ -101,7 +103,9 @@ Each `{event_id}.json` file:
 After syncing, use the query script to filter events by date or time window.
 **Agents should use this script instead of writing bespoke calendar parsers.**
 
-    node scripts/query.mjs [options]
+```text
+node scripts/query.mjs [options]
+```
 
 ### Time filters (combinable)
 

package/templates/.claude/skills/sync-apple-mail/SKILL.md

@@ -48,7 +48,9 @@ their email.
 Run the sync as a single Node.js script with embedded SQLite. This avoids N+1
 process invocations and handles all data transformation in one pass:
 
-    node scripts/sync.mjs [--days N]
+```text
+node scripts/sync.mjs [--days N]
+```
 
 - `--days N` — how many days back to look on first sync (default: 30)
 

package/templates/.claude/skills/sync-apple-mail/references/SCHEMA.md

@@ -106,7 +106,7 @@ used by the `recipients` table.
 
 Attachment files on disk follow this path structure:
 
-```
+```text
 ~/Library/Mail/V10/.../Attachments/{message_ROWID}/{attachment_id}/{filename}
 ```