fdeops 3.7.7 → 3.7.8

package/bin/fde.js

@@ -169,6 +169,45 @@ function sectionBody(md, heading) {
   return body.join('\n').trim()
 }
 
+// Append `entry` as the last line of a "## Heading" section, creating the
+// section at end-of-file if it doesn't exist yet. Plain fs.appendFileSync
+// would land the entry after ANY later section the agent added (e.g. a
+// "## Notes" heading appended after "## Signal history"), silently moving a
+// signal token outside the section the reader scans - this keeps it inside
+// regardless of what follows.
+function appendUnderSection(md, heading, entry) {
+  const lines = md.split('\n')
+  const start = lines.findIndex(l => new RegExp('^#{1,6}\\s+' + heading + '\\b', 'i').test(l.trim()))
+  if (start === -1) {
+    const sep = md.length && !md.endsWith('\n') ? '\n' : ''
+    return `${md}${sep}\n## ${heading}\n\n${entry}\n`
+  }
+  let end = lines.length
+  for (let i = start + 1; i < lines.length; i++) {
+    if (/^#{1,6}\s/.test(lines[i].trim())) { end = i; break }
+  }
+  const before = lines.slice(0, end)
+  const after = lines.slice(end)
+  while (before.length > start + 1 && before[before.length - 1].trim() === '') before.pop()
+  before.push(entry)
+  if (after.length) before.push('')
+  return before.concat(after).join('\n')
+}
+
+// Shared by cmdLog and cmdDebrief so the two writers can't drift (the earlier
+// bug: fde log's format and fde debrief's format both existed, only one of
+// them matched what extractStakeholders actually read). A contact entry
+// carrying a [signal:x] token - however it got there - lands inside
+// "## Signal history"; everything else is a plain end-of-file append.
+function appendLogEntry(eng, type, entry) {
+  const p = path.join(eng, LOG_FILES[type])
+  if (type === 'contact' && /\[signal:(red|amber|green)\]/i.test(entry)) {
+    fs.writeFileSync(p, appendUnderSection(readEng(eng, LOG_FILES[type]), 'Signal history', entry))
+  } else {
+    fs.appendFileSync(p, `\n${entry}\n`)
+  }
+}
+
 // phase / trust / top risk / freshness - identical heuristic for status + dashboard.
 // Trust resolution: structured [signal:red|amber|green] tokens in stakeholders.md
 // (written by `fde log contact --signal` and `fde debrief`) win - the latest dated
@@ -305,9 +344,20 @@ function extractStakeholders(eng) {
   const notesIdx = colIndex(headers, /notes?/i)
 
   const history = []
+  // Format-agnostic on token position: `fde log contact --signal` writes
+  // "[date] [signal:x] text" (token right after the date), but `fde debrief`
+  // appends the token at the END of whatever the agent wrote per the skill's
+  // own contact: convention - "[date] text [signal:x]". Both are subject-first
+  // once the token is stripped, so match the token anywhere on the line rather
+  // than requiring it immediately after the date; a debrief-written signal was
+  // silently invisible to per-stakeholder matching before this.
   sectionBody(md, 'Signal history').split('\n').forEach(l => {
-    const m = l.trim().match(/^-\s*\[(\d{4}-\d{2}-\d{2})\]\s*\[signal:(red|amber|green)\]\s*(.+)$/i)
-    if (m) history.push({ date: m[1], signal: m[2].toLowerCase(), text: m[3] })
+    const dm = l.trim().match(/^-\s*\[(\d{4}-\d{2}-\d{2})\]\s*(.*)$/i)
+    if (!dm) return
+    const sm = dm[2].match(/\[signal:(red|amber|green)\]/i)
+    if (!sm) return
+    const text = dm[2].replace(/\[signal:(red|amber|green)\]/i, '').trim()
+    history.push({ date: dm[1], signal: sm[1].toLowerCase(), text })
   })
 
   return rows.map(cs => {
@@ -620,7 +670,8 @@ function cmdLog(args) {
   const eng = resolveEngagement()
   if (!eng) { console.error('no engagement - run: fde resume --init <name>'); process.exit(2) }
   const date = new Date().toISOString().slice(0, 10)
-  fs.appendFileSync(path.join(eng, LOG_FILES[type]), `\n- [${date}] ${signal ? `[signal:${signal}] ` : ''}${text}\n`)
+  const entry = `- [${date}] ${signal ? `[signal:${signal}] ` : ''}${text}`
+  appendLogEntry(eng, type, entry)
   console.log(`logged → ${LOG_FILES[type]}${signal ? ` (signal:${signal})` : ''}`)
 }
 
@@ -676,8 +727,12 @@ function cmdDebrief(args) {
     const m = bare.match(/^(decision|risk|delivery|contact):\s*(.+)$/i)
     if (m) {
       const type = m[1].toLowerCase()
-      if (dry) console.log(`→ ${LOG_FILES[type]}  - [${date}] ${m[2]}`)
-      else fs.appendFileSync(path.join(eng, LOG_FILES[type]), `\n- [${date}] ${m[2]}\n`)
+      const entry = `- [${date}] ${m[2]}`
+      if (dry) console.log(`→ ${LOG_FILES[type]}  ${entry}`)
+      // appendLogEntry, not a blind append: a contact: line may carry an
+      // inline [signal:x] token (the skill's own convention) and must land
+      // inside "## Signal history" the same way `fde log --signal` does.
+      else appendLogEntry(eng, type, entry)
       counts[type]++
     } else ctxLines.push(line)
   }

package/bin/install.js

@@ -142,6 +142,16 @@ function cmdAdapters(targetDir) {
   console.log(`  fdeops cross-platform adapters → ${dest}`)
   console.log('  One brain (skills/fde/SKILL.md). These are thin pointers per tool.')
   console.log('')
+  // The pointers below all point at ~/.claude/skills/fde/SKILL.md. Only the
+  // default install (bare `npx fdeops` / `node bin/install.js`) used to place
+  // that file - `adapters` alone wrote pointers to a brain that didn't exist
+  // yet, a dangling reference for anyone following the documented Cursor/Codex
+  // path. installSkills() is idempotent (safe to call every run).
+  if (!fs.existsSync(path.join(GLOBAL_SKILLS_DIR, 'fde', 'SKILL.md'))) {
+    installSkills()
+    console.log('  Skills → ~/.claude/skills/  (installed - the pointers below need this)')
+    console.log('')
+  }
   for (const a of ADAPTER_TARGETS) {
     if (!fs.existsSync(a.src)) { console.log(`  skip   ${a.label} (template missing)`); continue }
     placePointer(path.join(dest, a.dest), fs.readFileSync(a.src, 'utf8'), a.label, a.appendable)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops",
-  "version": "3.7.7",
+  "version": "3.7.8",
   "description": "Field kit for engineers embedded in client work - a real CLI (recon, memory, portfolio), one @fde skill with field judgment on top, and hooks that make it automatic. Claude Code plugin and any agent that loads skills.",
   "bin": {
     "fdeops": "bin/install.js",

package/skills/fde/SKILL.md

@@ -28,6 +28,7 @@ This is what makes fdeops a second brain instead of a chat window.
 4. **No invented facts - ever.** People, names, quotes, meetings, and numbers exist only if the FDE said them or the repo shows them. Never invent a stakeholder, a conversation, or a source to make the narrative richer - one fabricated name poisons every real citation around it. A missing fact is written as `unknown - ask: <the question>`, nothing else.
 5. **On exit:** before the session ends, append three lines to `context.md`: where we are, what changed today, the next step. The `session-stop` hook backstops this deterministically (hooks resolve the engagement through the workspace registry - no env var needed), but you write the meaningful version.
 6. **One customer, one folder.** Never merge two engagements into one `.fde/`. Confirm which engagement applies when multiple exist.
+7. **Never delete a code-read section when rewriting an artifact.** `stakeholders.md`'s `## Signal history` holds dated `[signal:...]` tokens that `fde status`/`fde receipts`/the dashboard read verbatim; `risks.md`'s `## Retired` is read the same way. Rewriting either file as an artifact (land, audit, stakeholder-radar) is fine - dropping one of these sections is not. Carry existing entries forward untouched.
 
 ## Data boundary (confirm before touching their code)
 

package/skills/fde/references/land.md

@@ -69,6 +69,7 @@ Before the end of day 1, ship one visible thing: a small bug fix, a cleanup the
 |-----|------|--------|-------|
 | <name> | sponsor / champion / resistor / veto / passed-over | green/amber/red | <evidence, day> |
 ```
+If `stakeholders.md` already has a `## Signal history` section (it does from the template), **never delete or overwrite it** when you rewrite this file - it holds the dated `[signal:...]` tokens `fde log contact --signal` and `fde debrief` write, and `fde status`/`fde receipts`/the dashboard read only from that section. Edit the table above it freely; keep the section below intact.
 
 **`trust-profile.md`** - sacred data (`<private>` tagged), fears heard, AI policy, approval chain. Sensitive: never loaded for status reads, never into subagent prompts.
 

package/templates/.fde/stakeholders.md

@@ -8,3 +8,11 @@
 
 **Trust signal:** green | amber | red  
 **Last trust check:**
+
+## Signal history
+
+<!-- `fde log contact --signal <color>` and `fde debrief` write dated tokens here.
+     fde status/receipts read the LATEST dated [signal:...] token in this section
+     to drive the trust column - do not delete this heading, and if you rewrite
+     this file as an artifact, keep this section's entries intact. -->
+