johns-harness 2026.9.23 → 2026.9.25

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 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.
+- The Family 71 packed-artifact gate now also proves all eleven bundled generic skills are inside every tarball, and verifier checks 72.1 through 72.5 enforce presence, frontmatter, the generic wording contract, and no em dashes.
+- Roll back with `npm i -g johns-harness@2026.9.24`.
+
+## 2026.9.24
+
+- Family 71: native-first Jiti plugin loading (Family 68) is now standard on `latest`. The `extended` dist-tag moves to this same version, so both lines converge at 2026.9.24. Node loads already-built JavaScript plugin code natively first and keeps Babel only for TypeScript plugin entries; `JITI_TRY_NATIVE` is no longer needed and is harmless if set.
+- New packed-artifact gate `scripts/check-packed-artifact.mjs` inspects the real `npm pack` output (and registry tarballs) and fails closed unless all ten plugin-loader copies carry the Family 68 option. Releases 2026.9.22 and 2026.9.23 were cut from the pre-68 base, so their tarballs lacked it while main carried it; this gate makes that impossible to repeat.
+- Roll back with `npm i -g johns-harness@2026.9.23`.
+
 ## 2026.9.23
 
 - Family 70: ship the `orchestrator` skill as a bundled, always-eligible skill so every harness install loads the delegation and briefing protocol implicitly (pass the user's words through when they are clear, expand when they are vague, keep briefings brief). Workspace overrides, `enabled: false` and `allowBundled` still apply. `RULES.md` points at the bundled copy.
@@ -8,6 +20,11 @@
 
 - Family 69: enforce the latest DeepSeek Flash/Pro, Muse and Gemini Lite alias targets across all 14 shipped copies; document `/model deepseek` and retain Family 68 on the separate `extended` release line.
 
+## 2026.9.21-extended.1
+
+- Family 68: bake `tryNative: true` into every plugin-loader `createJiti` options object so Node loads already-built JavaScript natively first and keeps Babel only as fallback for TypeScript plugin entries. This is the Path-1 1 GiB cold-start fix; Telegram, WhatsApp and memory stay enabled.
+- Published on the `extended` dist-tag only. `latest` remains `2026.9.20`.
+
 ## 2026.9.20
 
 - Family 67: native DeepSeek V4.1 Flash/V4 Pro catalog, environment auth, aliases, model-specific effort mapping and tool/reasoning replay through the supported Chat Completions transport.

package/README.md

@@ -85,8 +85,8 @@ node johnness.mjs --help
 ### Verify
 
 ```bash
-npm test                        # 887 tests against the installed dependency tree
-bash scripts/verify-patches.sh  # 437 checks across every patch family
+npm test                        # 914 tests against the installed dependency tree
+bash scripts/verify-patches.sh  # 458 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: 68 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: 72 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 68 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 437 checks against the package tree and installed dependencies, and 887 tests run against the installed dependency tree.
+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.
 
 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,11 +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. |
 
 ## 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 68 patch families, one record each.
+- [`docs/PATCHES.md`](docs/PATCHES.md): the 72 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/dist/compact-B247y5Qt.js

@@ -92823,6 +92823,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/pi-embedded-C6ITuRXf.js

@@ -91543,6 +91543,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/pi-embedded-DoQsYfIY.js

@@ -91533,6 +91533,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/plugin-sdk/dispatch-BP0viZiL.js

@@ -59018,6 +59018,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/plugin-sdk/dispatch-CQsjmw7g.js

@@ -59018,6 +59018,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/plugin-sdk/dispatch-Cerq29sy.js

@@ -59420,6 +59420,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/plugin-sdk/dispatch-Cndjtt0g.js

@@ -59059,6 +59059,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/plugin-sdk/dispatch-UogiJYul.js

@@ -59018,6 +59018,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/plugin-sdk/reply-DbZnH8-h.js

@@ -63115,6 +63115,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/dist/reply-C5LKjXcC.js

@@ -55779,6 +55779,7 @@ function loadJohnnessPlugins(options = {}) {
 			...resolvePluginSdkScopedAliasMap()
 		};
 		jitiLoader = createJiti(import.meta.url, {
+			tryNative: true, // JOHNNESS_PATCH_JITI_TRY_NATIVE_68
 			interopDefault: true,
 			extensions: [
 				".ts",

package/docs/MR-MEMORY-DOCTOR-SAFETY.md

@@ -0,0 +1,31 @@
+# MemoryRouter doctor reconciliation safety
+
+Verified on John's Harness 2026.9.23 for the mr-memory 3.13.3 read-only boot change.
+
+## Finding: no runtime patch needed
+
+`doctor --fix` does **not** prune or disable `plugins.entries.mr-memory` in the current harness. Removing mr-memory's old boot-time config rewrite does not remove a required harness safeguard.
+
+- Both `dist/doctor-config-flow-*.js` variants run `loadAndMaybeMigrateDoctorConfig` and `stripUnknownConfigKeys` against the host schema. The plugin entries schema is a string-keyed record, and a plugin's `config` is itself an open record. An entry is not an unknown schema property merely because its ID is not a built-in channel.
+- Plugin-aware validation obtains IDs and schemas from the manifest registry. The harness ships `extensions/mr-memory/johnness.plugin.json`, so mr-memory is known even without a separately installed external copy.
+- `validateConfigObjectWithPlugins` treats an unavailable plugin entry as a warning, not an instruction to delete its configuration. It validates an installed plugin's own config using its manifest.
+- `applyPluginAutoEnable` can enable eligible plugins; it does not disable mr-memory. Explicitly disabled entries remain disabled. Doctor should not override an intentional user opt-out.
+- Patch 59's mr-memory installation adapter remains useful for native namespace adoption, but doctor safety does not depend on plugin entrypoint execution or that plugin writing config at startup.
+
+## Regression evidence
+
+`node --test tests/mr-memory-doctor.test.mjs`
+
+Eight isolated tests execute both real bundled doctor config flows, then the real host config writer and validator, twice each. They cover enabled and intentionally disabled memory, with and without an installed external mr-memory manifest. The external plugin entrypoint deliberately throws if loaded: no test can pass because boot-time self-healing put a removed entry back.
+
+Each fixture includes an invalid top-level key, forcing the actual `--fix` unknown-key reconciliation path. Tests assert that this key is removed while mr-memory's complete configuration (fixture key, per-agent keys, density, endpoint), enabled state, allowlist and memory slot survive. Native search stays disabled, native memory flush stays enabled, unrelated plugin entries survive, the persisted config validates, and the second doctor pass is idempotent.
+
+Child processes have isolated HOME/state/config/temp paths. Node's permission model grants filesystem writes only inside the disposable fixture directory and denies child processes. No live gateway, service, fleet config, or real credentials are used.
+
+Additional release-artifact verification:
+
+- The two doctor entrypoint bundles, two config-flow bundles, and two config/validation bundles in the published `johns-harness@2026.9.23` tarball are byte-identical to the tested checkout.
+- A fresh Docker container installed the published harness tarball, then the exact candidate `mr-memory@3.13.3` tarball through `johnness plugins install`. With a fixture key and an invalid top-level property, two complete `johnness doctor --fix --non-interactive` runs preserved the full mr-memory entry and memory slot, kept native search disabled and memory flush enabled, and removed only the invalid property. No `.openclaw/openclaw.json` was created. The run ended `HARNESS_DOCTOR_CLI_MEMORY_PRESERVED`.
+- Full checkout test suite: **900 pass, 0 fail** (including the eight new tests). Patch verifier: **440 pass, 0 fail**.
+
+Because no real gap was found, there is no new patch family and no 2026.9.24 runtime release for this investigation. `latest` and `extended` are unchanged.

package/docs/PATCHES.md

@@ -17,7 +17,7 @@ they predate ~2026-06-06).
 
 ## Index
 
-Family 01 is retired. Families 02 through 41, 43 through 67, 69 and 70, including the 65.1 amendment, are live on `main`; Family 68 ships on the `extended` release line. Family 42 is omitted; native Codex OAuth ownership is Family 58.
+Family 01 is retired. Families 02 through 41, 43 through 72, including the 65.1 amendment, are live on `main`; the `latest` and `extended` release lines converged at 2026.9.24. Family 42 is omitted; native Codex OAuth ownership is Family 58.
 
 1. **01, announce queue TTL, retired:** Removed the five-minute age filter that could discard delayed sub-agent completion announcements. [Details](#01--announce-ttl-retired-2026-07-30)
 2. **02, failover rotation:** Returns model selection to the highest-priority profile after its cooldown ends. [Details](#02--failover-rotation-undocumented)
@@ -95,6 +95,10 @@ Family 01 is retired. Families 02 through 41, 43 through 67, 69 and 70, includin
 
 70. **70, bundled orchestrator skill:** The delegation and briefing protocol ships as an always-eligible bundled skill; every install loads it implicitly and a workspace copy still overrides it. [Details](#family-70-bundled-orchestrator-skill)
 
+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)
+
 ---
 
 ## 01 - announce-ttl (RETIRED 2026-07-30)
@@ -2567,7 +2571,21 @@ The 65.1 updater budgets fresh installs from the old dependency size. A very ful
 
 ## Family 67: native DeepSeek and current provider catalog
 
-Verified September 13, 2026 against official provider catalogs and harmless live API probes. Adds DeepSeek V4.1 Flash/V4 Pro via the existing supported Chat Completions adapter, Gemini Flash-Lite, current prices and Claude xhigh mappings. Preserves all legacy IDs, configured selection, deliberate context budgets and provider-default omission. [Full source/evidence/limits](PROVIDER-CATALOG.md). Canonical adapters live in the version-checked pi-ai overlay; `patch-provider-catalog.py --check` validates exact registry/auth/alias/adapter snapshots without network or secrets. Historical reconstruction retains exact byte comparisons through the Family 67 helper.
+Verified September 13, 2026 against official provider catalogs and harmless live API probes. Adds DeepSeek V4.1 Flash/V4 Pro via the existing supported Chat Completions adapter, Gemini Flash-Lite, current prices and Claude xhigh mappings. Preserves all legacy IDs, configured selection, deliberate context budgets and provider-default omission. [Full source/evidence/limits](PROVIDER-CATALOG.md). Canonical adapters live in the version-checked pi-ai overlay; `patch-provider-catalog.py --check` validates exact registry/auth/alias/adapter snapshots without network or secrets. Historical reconstruction retains exact byte comparisons through the Family 67 helper. Family 68 later adds one native-Jiti options line in the ten loader copies; Family 67 hash checks compare the Family-67 surface (that line stripped) so the reviewed catalog snapshot stays fail-closed.
+
+## 68 Native-first Jiti plugin load
+
+**Marker:** `JOHNNESS_PATCH_JITI_TRY_NATIVE_68`
+**Release:** `johns-harness@2026.9.21-extended.1` (`extended` dist-tag; `latest` stays `2026.9.20`)
+**Patcher:** `scripts/patch-jiti-try-native.py [root] [--check] [--present-only]`. Plans all ten plugin-loader copies before writing, rejects missing/ambiguous `createJiti` anchors, and is byte-idempotent.
+
+Jiti 2.x defaults `tryNative` on only for Bun. On Node the plugin loader Babel-transforms already-built JavaScript, including Telegram's pull of `dist/plugin-sdk/dispatch-Cerq29sy.js` (~3.84M chars). Family 68 bakes `tryNative: true` into every live `createJiti(import.meta.url, { interopDefault, extensions, alias })` options object used by the plugin loader. Existing options stay. Babel fallback remains for TypeScript plugin entries. Telegram, WhatsApp, and memory are not disabled.
+
+Isolated 1 GiB lab (env-only predecessor): three cold VM/cache starts plus one warm restart, peak RSS 312–327 MiB, health plus mock tool turn passed. This family makes that behavior the shipped default instead of an operator env flag.
+
+**Tests:** `tests/jiti-try-native.test.mjs` covers presence of the option in all ten copies, `--check` cleanliness, idempotent replay, and fail-closed preflight. Historical family reconstructions apply Family 68 after Family 67 so byte-exact comparisons keep working. Verifier checks the marker, `tryNative: true`, and exact read-only replay.
+
+Roll back the package with `npm i -g johns-harness@2026.9.20`. This extended release does not move `latest`.
 
 ## Family 69: DeepSeek alias contract
 
@@ -2577,7 +2595,7 @@ Release: `johns-harness@2026.9.22` (`latest`). Extends the release gate, not the
 All 14 alias copies must match these exact targets, agree with each other, and resolve every shipped alias in the catalog.
 Verifier checks 69.1 and 69.2 enforce the contract and exactly one DeepSeek Flash alias per copy.
 Future catalog releases must move the matching contract targets; user-configured aliases still win.
-Family 68 remains on the `extended` release line and is not included in this `latest` artifact.
+Family 68 remains on the `extended` release line and is not included in this `latest` artifact. (Superseded by Family 71: from `2026.9.24` Family 68 ships on `latest` as well.)
 
 ## Family 70: bundled orchestrator skill
 
@@ -2586,3 +2604,57 @@ The skill is the delegation protocol: orchestrate rather than work; pass the use
 It is marked `always: true` so no bin, env or config gate hides it. The ordinary precedence still applies: a workspace `skills/orchestrator` or managed copy overrides it, `skills.entries.orchestrator.enabled: false` turns it off, and an `allowBundled` allowlist that omits it is respected.
 `RULES.md` section 5 and its skill table point at the bundled skill. No runtime code changes. Verifier checks 70.1 through 70.5 cover presence, the always flag, the briefing rule, the generic wording and the RULES pointer; `tests/orchestrator-skill.test.mjs` proves every skills chunk loads it from an empty workspace, into the prompt snapshot, and that the override and disable paths still work.
 Family 68 remains on the `extended` release line and is not included in this `latest` artifact.
+
+## Family 71: native-first Jiti standard on latest
+
+**Marker:** `JOHNNESS_PATCH_NATIVE_JITI_STANDARD_71` (gate and tests; the runtime change is Family 68's own marker in the ten loader copies)
+**Release:** `johns-harness@2026.9.24`. Published as `latest` and the `extended` dist-tag is moved to the same version, so the two lines converge here.
+**Gate:** `scripts/check-packed-artifact.mjs [root] | --tarball <file.tgz> [--expect-version <v>]`
+
+What had been excluding Family 68 from `latest`: not a build step or a strip pass, a branch point. Releases `2026.9.22` and `2026.9.23` were cut from `6427b26` (the pre-68 base of `2026.9.20`), packed and published from that tree, and only then no-ff merged into main. Main carried Family 68 the whole time; the tarballs never did. Every check ran against a working tree, so nothing could notice that the artifact differed from the tree.
+
+Family 71 closes that gap from the artifact side. The gate runs `npm pack --ignore-scripts`, extracts the tarball, and fails closed unless every one of the ten plugin-loader copies inside it carries exactly one `JOHNNESS_PATCH_JITI_TRY_NATIVE_68` marker and exactly one `tryNative: true`, the tarball version equals the tree version, and no loader copy is missing. The same module inspects a tarball fetched from the registry, which is how the published artifact is proven after `npm publish`. On an installed target the verifier applies the same ten-copy rule to the installed tree.
+
+Effect: Node loads already-built JavaScript plugin code natively first on every install, with Babel kept only as the fallback for TypeScript plugin entries. Measured on the fleet before this release: gateway RSS 464 MB and 446 MB on `latest` (2026.9.23 and 2026.9.19) against 355 MB on `extended`; isolated 1 GiB lab peak RSS 312 to 327 MiB. The `JITI_TRY_NATIVE=1` environment variable is no longer needed and is harmless if still set. Telegram, WhatsApp and memory stay enabled.
+
+Family 67 hash checks continue to compare the Family-67 surface with the Family 68 line stripped, unchanged from `2026.9.21-extended.1`; no further adjustment was needed because the loader bytes on main were already the released bytes.
+
+**Tests:** `tests/native-jiti-standard.test.mjs` proves the gate passes a complete tarball, fails a tarball packed without Family 68 (the 2026.9.22 and 2026.9.23 shape), fails when one copy lacks the option or is absent, fails on a version mismatch, exits non-zero from the CLI, and that the real `npm pack` output of this tree carries the marker in all ten copies. Verifier checks 71.1 through 71.3 cover the shipped gate, the packed or installed artifact, and the absence of a separate extended pin in `package.json`.
+
+Roll back with `npm i -g johns-harness@2026.9.23` (no native-first Jiti) or `npm i -g johns-harness@2026.9.21-extended.1` (Family 68 without Families 69 and 70).
+
+## Family 72: bundled generic skills
+
+**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.
+
+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).
+
+Decision table:
+
+| Skill | Decision | Reason |
+|---|---|---|
+| code-ops | ship, converted | generic protocol, anecdote generalized |
+| 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 |
+| 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 |
+| 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 |
+| hq-ops | drop | personal repo and GitHub links |
+| brain-backup | drop | personal restic bucket and paths |
+| provider-stats | drop | personal auth profiles |
+| anthropic-sub-proxy | drop | specific deployed proxy setup |
+| reddit-posting | drop | product marketing workflow |
+| comms-identity, email-format, dri-reimbursement, johns-amex-login, insyte, willow, x-original-post, memoryrouter-listings, memoryrouter-seo | drop | owner-only skills |
+| 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.
+
+Roll back with `npm i -g johns-harness@2026.9.24`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "johns-harness",
-  "version": "2026.9.23",
+  "version": "2026.9.25",
   "description": "John's Harness: a production agent harness that runs autonomous coding agents as one cooperative swarm.",
   "keywords": [
     "ai-agents",
@@ -42,6 +42,7 @@
     "scripts/postinstall.mjs",
     "scripts/prepare-slim-bundles.mjs",
     "scripts/strip-sourcemaps.mjs",
+    "scripts/check-packed-artifact.mjs",
     "scripts/slim-bundles.json",
     "!extensions/**/node_modules/.ignored*/**",
     "!extensions/**/node_modules/.bin/**",

package/scripts/check-packed-artifact.mjs

@@ -0,0 +1,148 @@
+#!/usr/bin/env node
+// JOHNNESS_PATCH_NATIVE_JITI_STANDARD_71
+// Family 71: native-first Jiti is standard on every artifact.
+//
+// Family 68 bakes `tryNative: true` into the ten plugin-loader copies. Releases 2026.9.22 and
+// 2026.9.23 were branched from the pre-68 base and packed from that tree, so the `latest`
+// tarballs shipped without it while the working tree on main carried it. Working-tree checks
+// cannot catch that. This gate inspects the real packed artifact: it runs `npm pack` (or takes
+// an existing tarball), extracts it, and fails closed unless every loader copy in the tarball
+// carries exactly one Family 68 marker and exactly one `tryNative: true`, the tarball version
+// matches the tree version, and no copy is missing.
+//
+// Family 72: the bundled generic skills are also part of the artifact contract. Every one of
+// the Family 72 skills must be present in the tarball with a `name` and a `description` in its
+// frontmatter. The same inspection runs on installed trees.
+//
+// Usage:
+//   node scripts/check-packed-artifact.mjs [package root]        pack the tree, then inspect
+//   node scripts/check-packed-artifact.mjs --tarball <file.tgz>  inspect a tarball (for example
+//                                                                one fetched from the registry)
+//   --expect-version <v>  require this package.json version inside the tarball
+
+import fs from "node:fs";
+import os from "node:os";
+import path from "node:path";
+import { execFileSync } from "node:child_process";
+import { fileURLToPath } from "node:url";
+
+export const MARKER_68 = "JOHNNESS_PATCH_JITI_TRY_NATIVE_68";
+export const OPTION_68 = "tryNative: true";
+// Mirrors ALL_FILES in scripts/patch-jiti-try-native.py.
+export const LOADERS10 = [
+  "dist/compact-B247y5Qt.js",
+  "dist/pi-embedded-C6ITuRXf.js",
+  "dist/pi-embedded-DoQsYfIY.js",
+  "dist/plugin-sdk/dispatch-BP0viZiL.js",
+  "dist/plugin-sdk/dispatch-CQsjmw7g.js",
+  "dist/plugin-sdk/dispatch-Cerq29sy.js",
+  "dist/plugin-sdk/dispatch-Cndjtt0g.js",
+  "dist/plugin-sdk/dispatch-UogiJYul.js",
+  "dist/plugin-sdk/reply-DbZnH8-h.js",
+  "dist/reply-C5LKjXcC.js",
+];
+
+const count = (text, needle) => text.split(needle).length - 1;
+
+// Family 72: the generic skills shipped as bundled skills. Each must be inside the artifact
+// with valid frontmatter (a `name:` and a `description:` line).
+export const F72_SKILLS = [
+  "activity-logging",
+  "arch-viz",
+  "code-ops",
+  "cold-outreach",
+  "content-story",
+  "dashboard",
+  "gcp-logs",
+  "outlook",
+  "plan-archival",
+  "todos",
+  "web-research",
+];
+
+/** Family 72: verify every bundled generic skill is present with frontmatter. Returns the count. */
+export function inspectSkills72(pkgDir) {
+  const problems = [];
+  for (const name of F72_SKILLS) {
+    const file = path.join(pkgDir, "skills", name, "SKILL.md");
+    if (!fs.existsSync(file)) { problems.push(`${name}: skills/${name}/SKILL.md missing from artifact`); continue; }
+    const text = fs.readFileSync(file, "utf8");
+    if (!/^name: [a-z0-9-]+$/m.test(text)) problems.push(`${name}: frontmatter has no name line`);
+    if (!/^description: .+$/m.test(text)) problems.push(`${name}: frontmatter has no description line`);
+  }
+  if (problems.length) throw new Error(`Family 72: packed artifact is missing bundled generic skills:\n  ${problems.join("\n  ")}`);
+  return F72_SKILLS.length;
+}
+
+/** Inspect an extracted package directory (the `package/` folder of a tarball). Throws on any gap. */
+export function inspectExtracted71(pkgDir, { expectVersion } = {}) {
+  const manifestPath = path.join(pkgDir, "package.json");
+  if (!fs.existsSync(manifestPath)) throw new Error(`Family 71: tarball has no package.json at ${manifestPath}`);
+  const manifest = JSON.parse(fs.readFileSync(manifestPath, "utf8"));
+  if (manifest.name !== "johns-harness") throw new Error(`Family 71: tarball is ${manifest.name}, expected johns-harness`);
+  if (expectVersion && manifest.version !== expectVersion) {
+    throw new Error(`Family 71: tarball version ${manifest.version} does not match expected ${expectVersion}`);
+  }
+  const problems = [];
+  let markers = 0;
+  for (const rel of LOADERS10) {
+    const file = path.join(pkgDir, rel);
+    if (!fs.existsSync(file)) { problems.push(`${rel}: missing from artifact`); continue; }
+    const text = fs.readFileSync(file, "utf8");
+    const m = count(text, MARKER_68);
+    const o = count(text, OPTION_68);
+    if (m !== 1) problems.push(`${rel}: ${m} Family 68 markers (expected 1)`);
+    if (o !== 1) problems.push(`${rel}: ${o} tryNative: true (expected 1)`);
+    if (m === 1 && o === 1) markers += 1;
+  }
+  if (problems.length) throw new Error(`Family 71: packed artifact lacks native-first Jiti:\n  ${problems.join("\n  ")}`);
+  const skills = inspectSkills72(pkgDir);
+  return { version: manifest.version, loaders: LOADERS10.length, markers, skills };
+}
+
+/** Extract a tarball into a temp dir and inspect it. */
+export function inspectTarball71(tarball, options = {}) {
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), "johnness-f71-"));
+  try {
+    execFileSync("tar", ["-xzf", path.resolve(tarball), "-C", tmp], { stdio: ["ignore", "pipe", "pipe"] });
+    return { tarball: path.resolve(tarball), ...inspectExtracted71(path.join(tmp, "package"), options) };
+  } finally {
+    fs.rmSync(tmp, { recursive: true, force: true });
+  }
+}
+
+/** Pack the tree with npm (scripts ignored; same method as the Family 66 Linux gate) and inspect the result. */
+export function packAndInspect71(root) {
+  const tree = JSON.parse(fs.readFileSync(path.join(root, "package.json"), "utf8"));
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), "johnness-f71-pack-"));
+  try {
+    const pack = JSON.parse(execFileSync("npm", ["pack", "--json", "--ignore-scripts", "--pack-destination", tmp], {
+      cwd: root, encoding: "utf8", maxBuffer: 20e6, stdio: ["ignore", "pipe", "pipe"],
+    }))[0];
+    const result = inspectTarball71(path.join(tmp, pack.filename), { expectVersion: tree.version });
+    return { ...result, tarball: pack.filename, bytes: pack.size, entries: pack.entryCount };
+  } finally {
+    fs.rmSync(tmp, { recursive: true, force: true });
+  }
+}
+
+if (process.argv[1] && path.resolve(process.argv[1]) === fileURLToPath(import.meta.url)) {
+  const args = process.argv.slice(2);
+  const flag = (name) => { const i = args.indexOf(name); return i >= 0 ? args[i + 1] : undefined; };
+  const tarball = flag("--tarball");
+  const expectVersion = flag("--expect-version");
+  try {
+    let result;
+    if (tarball) {
+      result = inspectTarball71(tarball, { expectVersion });
+    } else {
+      const positional = args.filter((a, i) => !a.startsWith("--") && args[i - 1] !== "--tarball" && args[i - 1] !== "--expect-version");
+      const root = path.resolve(positional[0] || path.join(path.dirname(fileURLToPath(import.meta.url)), ".."));
+      result = packAndInspect71(root);
+    }
+    console.log(`Family 71: ${result.markers}/${result.loaders} loader copies carry native-first Jiti in ${path.basename(result.tarball)} (version ${result.version}); Family 72: ${result.skills} bundled generic skills present`);
+  } catch (error) {
+    console.error(error.message);
+    process.exit(1);
+  }
+}

package/skills/activity-logging/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: activity-logging
+description: Activity and action logging to the workspace. Load when logging work outcomes or recording actions to ACTION_LOG.md.
+---
+
+# Activity & Action Logging
+
+## Activity Logging: Log Outcomes, Not Tasks
+
+### What to Log
+- Features built or meaningfully improved
+- Process/rule changes with real impact
+- Decisions that matter
+- Problems encountered and how they were resolved (if interesting)
+
+### What NOT to Log
+- Fixing your own mistakes (type errors, build failures, typos)
+- Minor tweaks or implementation details
+- Each tiny step of a larger task: consolidate into one entry
+- Routine maintenance
+
+### How to Decide
+Ask: *"Would the user care about this in a weekly review?"*
+- If it's an **outcome** that delivered value, log it
+- If it's **busywork** or cleanup, skip it
+- If multiple items are related, **consolidate** into one entry
+
+### Format
+- **Bold the specific outcome**: then explain what/how/why
+- Entry should make sense in 3 months without extra context
+- Ask: *"What can the user or I do now that we couldn't before?"*
+- Bad: "Improved chart system"
+- Good: "Pie charts now show percentages on slices: added data labels, mobile scroll, theme colors"
+
+### Process
+1. Update today's log: `memory/logs/YYYY-MM-DD.md`
+2. Mirror on the dashboard if one exists
+3. Push to git:
+```bash
+cd <workspace>
+git add -A && git commit -m "Update log" && git push
+```
+
+---
+
+## Action Log (Real-Time Action Tracking)
+
+**Log every action as it happens.**
+
+### Location
+`ACTION_LOG.md` in the workspace root
+
+### What to Log
+Every action you take: simple one-liner titles:
+- Spawned sub-agent for X
+- Generated image for Y
+- Fixed Z in repo
+- Created skill for W
+- Sent message to user about V
+
+### Format
+```markdown
+## YYYY-MM-DD
+
+- Action 1
+- Action 2
+- Action 3
+```
+
+### Rules
+1. **Log immediately**: after completing any action, add a one-liner
+2. **Keep it simple**: title-level, not detailed
+3. **New date section**: start each day with a new `## YYYY-MM-DD` header
+4. **Don't overthink**: if you did something, log it
+
+### Daily Recap (Scheduled Job)
+A daily scheduled job can create `memory/YYYY-MM-DD.md` from:
+1. **Conversation history**: the full journey of what was discussed, decided, built
+2. **Action Log**: the action entries
+
+Format:
+```markdown
+# YYYY-MM-DD: [Creative title capturing the day's vibe]
+
+## The Story
+[2-4 paragraph narrative, journal entry style, captures the day's energy]
+
+## Key Accomplishments
+- Major wins and shipped items
+- Decisions made
+
+## Actions Log
+[Actions from ACTION_LOG.md]
+```
+
+This captures the journey over time: both the story AND the specifics.