johns-harness 2026.9.25 → 2026.9.26

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 2026.9.26
+
+- Family 73: the `content-story`, `dashboard` and `cold-outreach` skills are removed from the bundled set on request, leaving eight generic bundled skills (`code-ops`, `web-research`, `plan-archival`, `todos`, `arch-viz`, `gcp-logs`, `activity-logging`, `outlook`). They load by description match exactly as before, workspace copies override them, and `enabled: false` and `allowBundled` still apply. Nothing else changes from 2026.9.25.
+- Roll back with `npm i -g johns-harness@2026.9.25`.
+
 ## 2026.9.25
 
 - Family 72: eleven generic skills from the author's workspace ship as bundled skills (`code-ops`, `web-research`, `plan-archival`, `todos`, `dashboard`, `arch-viz`, `content-story`, `cold-outreach`, `gcp-logs`, `activity-logging`, `outlook`), converted to fully generic wording first: no owner names, paths, repos, accounts, or products. They load by description match like every other bundled skill (none is always-on), workspace copies override them, and `enabled: false` and `allowBundled` still apply. `RULES.md` lists all of them.

package/README.md

@@ -86,7 +86,7 @@ node johnness.mjs --help
 
 ```bash
 npm test                        # 914 tests against the installed dependency tree
-bash scripts/verify-patches.sh  # 458 checks across every patch family
+bash scripts/verify-patches.sh  # 455 checks across every patch family
 ```
 
 ## Launch a swarm with one command
@@ -132,7 +132,7 @@ Coding agents today run as isolated processes. Two agents on the same repository
 - **Memory built for production.** Tiered recall that traces from consolidated reflections down to the verbatim record, surviving compaction and shared across the swarm. Installed and enabled by default.
 - **Production authority per commit.** Promotion is granted to an exact SHA, never to a branch name, so one worker's authorization never covers another worker's commits.
 - **An append-only action log.** Agents record every consequential action to `ACTION_LOG.md` and read it before acting.
-- **A fixed runtime surface.** The core does not grow on a schedule. New mechanisms enter only to solve a demonstrated production failure, one narrow, tested, reversible patch at a time: 72 patch families, each with a regression test and a rollback path.
+- **A fixed runtime surface.** The core does not grow on a schedule. New mechanisms enter only to solve a demonstrated production failure, one narrow, tested, reversible patch at a time: 73 patch families, each with a regression test and a rollback path.
 - **Reliability with a definition.** Bounded retries, explicit failure states, exact-once continuation, context-pressure recovery, durable delivery, and supervised gateway recovery.
 - **Coding first, phone optional.** Direct the work at a high level from a chat channel while agents plan, implement, test, coordinate, and stage releases unattended.
 - **Local voice.** Optional native Whisper transcription of inbound audio, entirely on your machine. Off by default. [Setup](docs/NATIVE-WHISPER-MUSE.md).
@@ -199,7 +199,7 @@ The log is a [`RULES.md`](RULES.md) workspace convention enforced through the ac
 
 ## Patch families
 
-The runtime carries 72 patch families plus the 65.1 safe-update amendment. Each is a production fix applied at the source with a regression test, a durable patch marker, and a rollback path. A verifier runs 458 checks against the package tree and installed dependencies, and 914 tests run against the installed dependency tree.
+The runtime carries 73 patch families plus the 65.1 safe-update amendment. Each is a production fix applied at the source with a regression test, a durable patch marker, and a rollback path. A verifier runs 455 checks against the package tree and installed dependencies, and 914 tests run against the installed dependency tree.
 
 Every family follows the same six steps: reproduce the failure, trace the exact runtime path, make the smallest source-level change that restores the invariant, add a regression test and a patch marker, run the verifier, and retain rollback artifacts. The full index: [`docs/PATCHES.md`](docs/PATCHES.md).
 
@@ -213,12 +213,12 @@ Every family follows the same six steps: reproduce the failure, trace the exact
 | `--dev` | Dev profile under `~/.johnness-dev` with its own gateway port and shifted derived ports |
 | Rules | [`RULES.md`](RULES.md) ships 19 operating-policy sections injected on every call. Fill in the placeholders; keep long procedures in skills. |
 | Orchestrator skill | Bundled and loaded implicitly on every install. Decide whether to pass the user's words through or expand them, then keep the briefing brief. Override with a workspace `skills/orchestrator/SKILL.md`. |
-| Bundled generic skills | Eleven generic skills ship in `skills/` and load by description match: `code-ops`, `web-research`, `plan-archival`, `todos`, `dashboard`, `arch-viz`, `content-story`, `cold-outreach`, `gcp-logs`, `activity-logging`, `outlook`. Workspace copies override; `enabled: false` and `allowBundled` still apply. |
+| Bundled generic skills | Eight generic skills ship in `skills/` and load by description match: `code-ops`, `web-research`, `plan-archival`, `todos`, `arch-viz`, `gcp-logs`, `activity-logging`, `outlook`. Workspace copies override; `enabled: false` and `allowBundled` still apply. |
 
 ## Documentation
 
 - [`docs/index.md`](docs/index.md): runtime docs, from gateway and channels to plugins, nodes, and CLI reference.
-- [`docs/PATCHES.md`](docs/PATCHES.md): the 72 patch families, one record each.
+- [`docs/PATCHES.md`](docs/PATCHES.md): the 73 patch families, one record each.
 - [`docs/NATIVE-WHISPER-MUSE.md`](docs/NATIVE-WHISPER-MUSE.md): local Whisper transcription setup.
 - [`RULES.md`](RULES.md): the default operating rules, including Rule Zero on production authorization.
 

package/docs/PATCHES.md

@@ -97,7 +97,8 @@ Family 01 is retired. Families 02 through 41, 43 through 72, including the 65.1
 
 71. **71, native-first Jiti standard on latest:** The Family 68 native-first loader option ships on every artifact, the `latest` and `extended` lines converge, and a packed-artifact gate proves the tarball carries it. [Details](#family-71-native-first-jiti-standard-on-latest)
 
-72. **72, bundled generic skills:** Eleven workspace skills (code operations, research, todos, dashboard, planning, content, outreach, logs, and more) ship as generic bundled skills that load by description match, with no owner names or personal paths. [Details](#family-72-bundled-generic-skills)
+72. **72, bundled generic skills:** Eight workspace skills (code operations, research, todos, planning, logs, and more) ship as generic bundled skills that load by description match, with no owner names or personal paths. [Details](#family-72-bundled-generic-skills)
+73. **73, prune bundled skills:** `content-story`, `dashboard` and `cold-outreach` are removed from the Family 72 bundled set on request after `2026.9.25`; the remaining eight ship unchanged. [Details](#family-73-prune-bundled-skills)
 
 ---
 
@@ -2627,9 +2628,9 @@ Roll back with `npm i -g johns-harness@2026.9.23` (no native-first Jiti) or `npm
 
 **Release:** `johns-harness@2026.9.25`. Published as `latest` and the `extended` dist-tag moves to it (the two lines converged at 2026.9.24).
 
-Eleven skills from the author's personal workspace ship as bundled skills in `skills/<name>/SKILL.md`, made fully generic first: no owner names, no personal paths, repos, accounts, or products. Every one loads by description match like the other bundled skills (none is `always`-on, unlike the Family 70 orchestrator), a workspace or managed copy overrides it, `skills.entries.<name>.enabled: false` turns it off, and an `allowBundled` allowlist that omits it is respected.
+Eight skills from the author's personal workspace ship as bundled skills in `skills/<name>/SKILL.md`, made fully generic first: no owner names, no personal paths, repos, accounts, or products. Every one loads by description match like the other bundled skills (none is `always`-on, unlike the Family 70 orchestrator), a workspace or managed copy overrides it, `skills.entries.<name>.enabled: false` turns it off, and an `allowBundled` allowlist that omits it is respected. (Superseded by Family 73: from `2026.9.26` `dashboard`, `content-story` and `cold-outreach` are removed from the bundle.)
 
-Shipped skills: `code-ops` (learnings protocol, config tracing, publishing safety), `web-research` (never give up deep research method), `plan-archival` (move finished plans to plans/archive and memory/completed-plans), `todos` (workspace memory/todos protocol), `dashboard` (command center updated after every action), `arch-viz` (sub-agent generated architecture visualization), `content-story` (Story, Concept, Drop framework), `cold-outreach` (Four Pillars cold DM framework), `gcp-logs` (Cloud Run log debugging via gcloud, placeholder service names), `activity-logging` (log outcomes, not tasks, plus the ACTION_LOG), `outlook` (outlook tool quick reference).
+Shipped skills: `code-ops` (learnings protocol, config tracing, publishing safety), `web-research` (never give up deep research method), `plan-archival` (move finished plans to plans/archive and memory/completed-plans), `todos` (workspace memory/todos protocol), `arch-viz` (sub-agent generated architecture visualization), `gcp-logs` (Cloud Run log debugging via gcloud, placeholder service names), `activity-logging` (log outcomes, not tasks, plus the ACTION_LOG), `outlook` (outlook tool quick reference).
 
 Decision table:
 
@@ -2639,10 +2640,10 @@ Decision table:
 | web-research | ship, converted | generic method, em dashes stripped |
 | plan-archival | ship, converted | personal paths replaced with workspace-relative |
 | todos | ship, converted | owner name and paths replaced |
-| dashboard | ship, converted | names, projects and paths scrubbed |
+| dashboard | dropped | removed on request after 2026.9.25 |
 | arch-viz | ship, converted | personal paths and projects scrubbed |
-| content-story | ship, converted | frontmatter added, em dashes stripped |
-| cold-outreach | ship, converted | frontmatter added, product names scrubbed |
+| content-story | dropped | removed on request after 2026.9.25 |
+| cold-outreach | dropped | removed on request after 2026.9.25 |
 | gcp-logs | ship, converted | baked-in service names replaced with placeholders |
 | activity-logging | ship, converted | log names and paths made workspace-relative |
 | outlook | ship, converted | account domain scrubbed |
@@ -2655,6 +2656,16 @@ Decision table:
 | hyperframes, hyperframes-cli, hyperframes-media, website-to-hyperframes, impeccable | exclude | third-party vendored skills |
 | orchestrator | already shipped | Family 70 |
 
-Verifier checks 72.1 through 72.5 cover presence with frontmatter, the generic wording contract (no owner, product or personal names and no `always` flag), no em dashes, the RULES.md skill table, and the packed artifact (the Family 71 gate now also proves all eleven skills are inside the tarball). `tests/bundled-skills.test.mjs` proves every skills chunk loads all eleven from an empty workspace, a workspace copy overrides, `enabled: false` disables, and the `allowBundled` allowlist still wins. `RULES.md` section 5 lists every bundled skill.
+Verifier checks 72.1 through 72.5 cover presence with frontmatter, the generic wording contract (no owner, product or personal names and no `always` flag), no em dashes, the RULES.md skill table, and the packed artifact (the Family 71 gate now also proves all eight skills are inside the tarball). `tests/bundled-skills.test.mjs` proves every skills chunk loads all eight from an empty workspace, a workspace copy overrides, `enabled: false` disables, and the `allowBundled` allowlist still wins. `RULES.md` section 5 lists every bundled skill.
 
 Roll back with `npm i -g johns-harness@2026.9.24`.
+
+## Family 73: prune bundled skills
+
+**Release:** `johns-harness@2026.9.26`. Published as `latest` and the `extended` dist-tag moves to it.
+
+Three of the Family 72 bundled skills are removed from the bundled set on request after `2026.9.25`: `content-story`, `dashboard` and `cold-outreach`. The remaining eight (`activity-logging`, `arch-viz`, `code-ops`, `gcp-logs`, `outlook`, `plan-archival`, `todos`, `web-research`) are unchanged, and a workspace or managed copy of a removed skill still overrides and loads as it always did. Nothing else differs from `2026.9.25`.
+
+The counters move with the set: the verifier emits one check per remaining skill through the same 72.1 loop (455 checks in total), `tests/bundled-skills.test.mjs` asserts exactly eight bundled skills, `scripts/check-packed-artifact.mjs` fails closed unless a tarball carries all eight with frontmatter, and `README.md` and the pinned copy in `patches/59-migrate-cli.patch` carry the new counts together so check 59c stays green. `RULES.md` section 5 drops the three rows.
+
+Roll back with `npm i -g johns-harness@2026.9.25`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "johns-harness",
-  "version": "2026.9.25",
+  "version": "2026.9.26",
   "description": "John's Harness: a production agent harness that runs autonomous coding agents as one cooperative swarm.",
   "keywords": [
     "ai-agents",

package/scripts/check-packed-artifact.mjs

@@ -50,9 +50,6 @@ export const F72_SKILLS = [
   "activity-logging",
   "arch-viz",
   "code-ops",
-  "cold-outreach",
-  "content-story",
-  "dashboard",
   "gcp-logs",
   "outlook",
   "plan-archival",

package/skills/cold-outreach/SKILL.md

@@ -1,99 +0,0 @@
----
-name: cold-outreach
-description: Write cold DMs that get responses using the Four Pillars framework. Use when drafting outreach messages, direct messages, or connection requests for the user.
----
-
-# Cold Outreach / DM Skill
-
-Write cold DMs that get responses. Uses the Four Pillars framework.
-
-## Required Reading
-
-Before ANY outreach, read the full playbook if one exists:
-- `memory/outreach-playbook.md` in the workspace
-
-## The Four Pillars
-
-Every message must hit all 4:
-
-1. **PERSONAL**: their thesis/worldview (what they REALLY believe)
-2. **RELEVANT**: their current mission (what they're building NOW)
-3. **TIMELY**: recent content (what's top of mind TODAY)
-4. **POWERFUL**: peer energy (you're a collaborator, not a fan)
-
-## The DM Flow
-
-| Step | What to Say | Goal |
-|------|-------------|------|
-| 1. Opener | React to THEIR thing + ask question | Start conversation |
-| 2. Listen | Let them share their pain | Understand their words |
-| 3. "Same" | "yeah same, I built something" | Create curiosity |
-| 4. Wait | They ask "what is it?" | Make them pull |
-| 5. Share | Now give them the product | Favor, not pitch |
-
-## Opener Formula
-
-```
-"[reaction to specific content]. [establish same problem]. [ask what they did about it]"
-```
-
-**Example:**
-> "yo that piece on agents forgetting everything hit hard. been banging my head on the same problem. curious what you ended up doing about it"
-
-## Anti-Patterns (NEVER)
-
-- ❌ Product name in opener
-- ❌ Install commands
-- ❌ "Your audience would love..."
-- ❌ Flattery ("love your content!")
-- ❌ Fan energy ("would you check out...")
-- ❌ Offering before they ask
-
-## Good vs Bad
-
-**Bad (ad energy):**
-> "Hey [name] - been watching your agent coverage. I built [our product], a plugin that gives agents persistent memory. One-liner install. Think your audience would love it."
-
-**Good (peer energy):**
-> "yo that piece on agents forgetting everything hit hard. been banging my head on the same problem. curious what you ended up doing about it"
-
-## Research Requirements
-
-Before writing ANY outreach:
-1. Watch 2-3 recent videos: find their THESIS
-2. Read social presence: what identity are they building?
-3. Find ONE specific thing to react to
-4. Know what they'll likely respond (from research)
-5. Plan your step 3 response
-
-## Output Format
-
-For each creator, produce:
-
-```markdown
-## [Creator Name]
-
-### Research
-- **Thesis:** [what they really believe]
-- **Current mission:** [what they're building now]
-- **Recent content:** [specific thing to reference]
-- **Their solution:** [what they're currently doing about the problem]
-
-### Opener
-> [the DM]
-
-### Expected Response
-> [what they'll likely say]
-
-### Step 3 Response
-> [our "same, I built something" response]
-
-### Step 5 Share
-> [product share if they ask]
-```
-
-## Key Insight
-
-**Make them ask. Never offer first.**
-
-The goal is to create curiosity so strong that THEY pull the product out of you. Then sharing feels like a favor, not a pitch.

package/skills/content-story/SKILL.md

@@ -1,77 +0,0 @@
----
-name: content-story
-description: Generate content ideas using the Story, Concept, Drop framework. Use when brainstorming short-form video content, social posts, or creative concepts that need a hook and a payoff.
----
-
-# Content Story Skill
-
-Generate content ideas using the Story → Concept → Drop framework.
-
-## The Framework
-
-Every piece of content needs three things:
-
-### 1. The Story
-The journey. Beginning → destination. A problem that's relatable and a resolution that's satisfying.
-- The problem doesn't need to be big
-- The resolution doesn't need to be inspiring
-- But there MUST be a journey: something changes from start to finish
-
-### 2. The Concept
-The viral component. What's on screen that makes someone WATCH?
-- A beautiful person
-- Something unexpected just happened
-- You need to see what comes next
-- A visual that stops the scroll
-- Curiosity gap: "wait, what?"
-
-### 3. The Drop
-The climax. The moment the video makes sense. The payoff.
-- This is what people REWATCH for
-- Rewatches = algorithm fuel
-- The drop should feel earned: the story builds to it
-- Can be visual (reveal), emotional (surprise), or both
-
-## Rules
-
-- **Would YOU watch it?** If no, don't post it
-- **15-30 seconds max** for reels: tight, no fat
-- **Music matters**: the right song makes or breaks the drop
-- **Film 10x more than you post**: capture everything, curate ruthlessly
-- **No talking heads, no "5 tips", no corporate energy**
-- **Raw + cinematic > polished + corporate**
-- **Not looking at the lens > looking at the lens**: candid energy even when staged
-- **Daily posting beats perfect posting**: consistency wins
-
-## How to Use
-
-When brainstorming content, fill in:
-
-```
-STORY: [the journey: what changes?]
-CONCEPT: [the hook: why do they watch?]
-DROP: [the payoff: what's the climax?]
-```
-
-Then figure out:
-- What do you need to film?
-- What song fits?
-- What's the edit style? (slow-mo, transition, split screen, etc.)
-
-## Content Types That Hit
-
-- **Main character POV**: walking, arriving, living. Viewer projects themselves into it
-- **Transitions**: before/after, location swap, outfit change, time shift
-- **Silent storytelling**: music + visuals + text overlay. Works sound on AND off
-- **Candid energy**: looks unplanned but isn't. Natural > posed
-- **Reveals**: camera pulls back or cuts to show something unexpected
-- **Contrast**: old life vs new life, morning vs night, alone vs crowd
-
-## The Test
-
-Before posting, ask:
-1. Does it have all three? (Story, Concept, Drop)
-2. Would I stop scrolling for this?
-3. Would I rewatch it?
-
-If yes to all three → post it.

package/skills/dashboard/SKILL.md

@@ -1,129 +0,0 @@
----
-name: dashboard
-description: Maintain the user's command center dashboard in memory/dashboard.md. Update after any action (email sent, reply received, task completed, status change). Use when tracking pending items, project status, or giving the user a view of what's happening. The dashboard is the user's starting point; keep it current and useful.
----
-
-# The Dashboard
-
-The user's command center. Updated constantly. Shows what matters RIGHT NOW.
-
-## Location
-
-- **File:** `memory/dashboard.md` in the workspace
-- If the workspace is a git repo, commit and push after every update so the user can view it from anywhere.
-
-## Philosophy
-
-**Dynamic, not rigid.** Include what's relevant today. Sections appear/disappear based on what matters.
-
-**Curated, not comprehensive.** This is not a todo list dump. It is the user's "here's what you need to know right now."
-
-**Work AND life.** Personal stuff belongs here too if it is on the user's mind.
-
-## Sections (Use What's Relevant)
-
-```markdown
-# The Dashboard
-**Updated:** [timestamp in the user's timezone]
-
-## Right Now
-[Most urgent/relevant thing: meeting in 30 min, decision needed, blocker resolved]
-
-## Waiting On
-[People who owe the user something: name, what, how long]
-
-## Today
-[What's on deck: meetings, tasks, deadlines]
-
-## Hot Projects
-[Active projects with one-liner status + next action]
-
-## Notes
-[Context, reminders, thoughts worth capturing]
-```
-
-Not every section every day. Just what matters.
-
-## When to Update
-
-| Trigger | Action |
-|---------|--------|
-| Email sent | Add to "Waiting On" with timestamp |
-| Reply received | Update or remove from "Waiting On" |
-| Task completed | Remove from "Today" or note completion |
-| Meeting coming up | Add to "Right Now" if within 1 hour |
-| Status change | Update "Hot Projects" |
-| New blocker | Add to "Right Now" or "Waiting On" |
-| Something resolved | Remove or celebrate in "Notes" |
-
-## Prioritization (What Goes in "Right Now")
-
-1. **Time-sensitive**: meeting in < 1 hour, deadline today
-2. **Blocking**: something the user needs to unblock others
-3. **Waiting too long**: pending response > 3 days
-4. **Big news**: reply that changes things, win worth noting
-
-## Format Rules
-
-- **Timestamps:** always in the user's timezone, 12-hour format (e.g., "1:45 PM")
-- **People:** name + company/context (e.g., "Alex (vendor)")
-- **Projects:** link to the project folder if one exists
-- **Keep it scannable:** tables for lists, bullets for notes
-
-## After Every Update
-
-```bash
-cd <workspace>
-git add -A && git commit -m "Update dashboard" && git push
-```
-
-(If the workspace is not a git repo, skip the push.)
-
-## Automated Monitoring
-
-A scheduled job can check the user's inbox, compare against "Waiting On" and "Hot Projects", message the user if anything relevant, and stay silent if nothing important. Manual updates still happen after interactions.
-
-## Calendar Integration
-
-Pull from the calendar tool when relevant. Add meetings to "Today" with times in the user's timezone.
-
-## Examples
-
-**Busy day with meetings:**
-```markdown
-## Right Now
-📅 Team meeting in 25 min (11:00 AM)
-
-## Today
-- 11:00 AM - Team meeting
-- 12:00 PM - Vendor call
-- 2:00 PM - Project check-in
-
-## Waiting On
-- Alex (vendor) - server config fix (sent 1:42 PM)
-```
-
-**Quiet day, project focus:**
-```markdown
-## Right Now
-Nothing urgent. Good day to ship.
-
-## Hot Projects
-- **Project A** - building the configurator (from this morning's meeting)
-- **Project B** - blocked on a vendor fix
-
-## Notes
-The user should have their password synced by end of day.
-```
-
-**Personal stuff mixed in:**
-```markdown
-## Today
-- 10:00 AM - Dentist
-- 2:00 PM - Demo with a client
-- Pick up dry cleaning
-
-## Waiting On
-- Alex (vendor) - server fix
-- Online order - package arriving today
-```