vault-sync: 2026-10-14 11:24 (leonard)

memory-systems/agent-os/dream/2026-10-13.md

@@ -0,0 +1,173 @@
+# Dream Log — 2026-10-13
+
+## 🧩 Daily Summary
+
+Thin, high-signal day: **three human touchpoints**, no big build. The unattended layer
+(killcorpus supervisor/health + crew crons) ran all day without incident.
+
+Themes:
+- **Memory hygiene.** Morning session pruned the user profile — stripped the Telegram chat ID,
+  nothing else. Budget 1,360 → 1,342 / 1,375.
+- **killcorpus: "what do we know" → "when do we go live?"** Tony asked for a state-of-play and
+  then the capital question. The honest answer was structural: *there is no go-live gate by design* —
+  the corpus produces negative knowledge, not an edge. A formal gate spec was offered; no reply yet.
+- **OpenCode + DeepSeek — blocked on approval.** Tony asked for OpenCode to run DeepSeek. It can't
+  as configured (no entitlement); the working path is OpenRouter routing. The clarify timed out after
+  60 min → **no changes written**. Correct adherence to the no-writes-without-approval rule, but the
+  approval ask was poorly shaped (see Quality).
+
+## 🔑 Key Interactions
+
+**1. ~07:10–07:22 — Memory prune (CLI session `20261003_123136_a18d76`, "Telegram outage or issue")**
+- Reviewed a 30+ item memory list, mapped what was *actually* stored vs lived only in past chats.
+- Tony's instruction (arrived as a paste of a third-party agent's recommendation): "Strip 2 only."
+- Applied: replaced one USER PROFILE entry to drop ` (chat 5789896722)`. 7 entries, unchanged count;
+  usage 1,360 → 1,342 / 1,375.
+- Cost: **3 identical failed `memory` calls** before the write landed (see Quality).
+
+**2. 13:59–14:06 — killcorpus state-of-play + the capital question (Telegram, 59-msg thread)**
+- "summary of what we know so far" → grounded read-out: live PID, `counted 316/967`, mean +0.0033,
+  realized variance 0.1557 (σ² basis 0.25 → not underpowered), one-sided LB −0.0332 → K1 reads
+  `KILL (LB<=0)` **interim, not decisive until N=967**; rate 6.1/hr → ETA ~Oct 18.
+- Recorded the three fixed incidents: schema drift (`CREATE TABLE IF NOT EXISTS` silently swallowed
+  every insert while the clock ran), supervisor runaway (liveness keyed on a *constant* log line →
+  false stalls + duplicate process; count lived in memory only → `45f94a5` replays it from DB),
+  host clock (−284 ms vs a 250 ms gate → rekeyed, ±2 ms).
+- "when are we ready to go live with real money?" → **no go-live date exists, and no go-live gate is
+  defined anywhere in the repo.** Named what is missing (no keys/orders/auth, no sizing/bankroll/
+  kill-switch, no live-fill-validated execution, no verified fee schedule, no second regime/replication)
+  and offered to draft the gate list as a formal spec — doc only. **No reply.**
+
+**3. 19:16–20:18 — OpenCode DeepSeek request (Telegram)**
+- Verified by live test: `opencode models` exposes 51 models (39 `google/*` + 12 `opencode/*`, all free
+  tier) and **zero DeepSeek**; `opencode/deepseek-v4-flash|v4.1-flash|v4-pro` all return `UnknownError`
+  — listed in `opencode.jsonc` but the account has no entitlement. A known-good free model ran (`OC_SMOKE_OK`).
+- Tony's OpenRouter key verified live (462 models incl. `deepseek/deepseek-v4.1-flash`, `-v4-pro`, `-r1`,
+  `v4-flash-0731`). Proposed change: append `OPENROUTER_API_KEY` to `~/.config/opencode/.env` + add an
+  `openrouter` provider block + default model to `opencode.jsonc`, with backups, then smoke-test.
+- Asked two questions via `clarify` → **timed out after 60 min, unanswered → zero writes.** Reported the
+  finding and the exact proposed diff; made no changes.
+
+**Unattended layer (all nominal):** Dream Mode 02:05 (produced the 10-12 note) · Trace miner 07:30
+(305 sessions / 21,833 msgs / 25 findings; top recurring = `write_file` pagination-refusal, **172
+sessions**) · Topic news digest 08:01 · Sorter inbox triage 08:02 (inbox empty — but it also logged a
+hard error: `00_system/user-profile.md` not found) · Tailscale cheat-sheet sync 09:00 (no_change) ·
+killcorpus supervisor 15 m + health 1 h, every run `[SILENT]` — one process, one deliberate eval.
+
+## 📊 Quality Assessment
+
+**What I did well**
+- **Held the no-writes-without-approval line under direct pressure.** Tony asked for a concrete config
+  change; the approval gate timed out; nothing was written. Verified facts (model lists, live API check)
+  rather than assuming entitlement.
+- **Grounded, no-fabrication state-of-play.** Every killcorpus number came from a live read; K1 was
+  explicitly labelled *interim, not decisive until N=967* instead of being presented as a verdict.
+- **Answered the business question honestly.** "There is no go-live gate in this project by design"
+  is the answer that costs credibility in the moment and buys it later. Offered the missing artifact
+  (a gate spec) rather than inventing a milestone date.
+- Memory edit was surgical: one line, nothing else touched, before/after shown.
+
+**What I did poorly**
+- **Repeated an identical failing tool call three times.** `memory` failed with "content is required
+  (use action='remove')" and I re-issued the *same* arguments twice more. The error message was
+  prescriptive and I ignored it; cost 3 calls and tripped the tool-loop guardrail. This is the same
+  ignore-the-prescription failure the trace miner sees at scale (172 sessions on `write_file`'s
+  pagination refusal).
+- **Badly shaped approval ask.** The OpenCode proposal put *both* the diff and the question behind a
+  60-minute `clarify` window. The diff should have been in the reply body; the clarify should have been
+  a bare yes/no. A prompt with nothing to inspect wastes the one window you get.
+- **Marginal value in the morning exchange.** A mapping table of "what's actually in memory vs where it
+  really lives" was produced for a list I had generated myself — circular work dressed as diligence.
+- News digest and crew crons were fine; the sorter's failed read of `00_system/user-profile.md` is a
+  standing config gap that has now been reported twice without a fix.
+
+**Confusion / misinterpretation**
+- Session attribution: the day's first activity sits in a week-old CLI session whose *title* ("Telegram
+  outage or issue") has nothing to do with its content (memory pruning). Titles are unreliable as
+  summaries — read the messages.
+- The 07:20 instruction arrived formatted as another agent's recommendation ("Reply to the agent with
+  exactly: `strip 2`"). Tony relaying third-party agent output into a live session is a pattern worth
+  watching: it can look like an instruction to Hermes when it is really a message *for* a different
+  worker.
+
+**Errors/hallucinations avoided**
+- Did not invent killcorpus statistics, an ETA, or a go-live date.
+- Did not write the OpenCode config on an unanswered approval.
+- Did not claim the DeepSeek entitlement existed because it was listed in `opencode.jsonc` — tested it.
+
+## 🧠 Lessons Learned
+
+- **A prescriptive tool error is an instruction, not an obstacle.** When the error names the fix
+  ("use action=remove", "read the file first"), change the argument on the next call. Re-issuing the
+  same call is the single most-flagged recurring error in this agent's own traces — treat it as a
+  standing defect, not an accident.
+- **An approval request must arrive with the artifact visible.** Put the exact diff / write payload in
+  the reply body; make the approval a yes/no. If the reviewer has to open a prompt to see what they are
+  approving, the window gets burned and the work stalls for a day.
+- **Distinguish "what the project decided" from "what the user wants."** "When do we go live?" is not a
+  status question; it is a design question. Answering it with "there is no gate" and then offering to
+  build the gate preserves both honesty and momentum.
+- **Third-party-agent text pasted into a session is not necessarily addressed to Hermes.** Check the
+  addressee before acting on imperative phrasing.
+
+## 🎭 Behavioral Adjustments for Tomorrow
+
+- Never re-issue a failed tool call unchanged. Read the prescription, fix the argument, retry once.
+- Bundle the approval artifact (diff, payload, or exact command) into the same message as the ask.
+- Keep the "interim, not decisive until N=X" label on any partial statistical verdict.
+- Prefer reading a session's messages over trusting its auto-title.
+- When pruning memory/skills, show the before/after diff of the *thing being changed* — not a
+  restatement of the list that prompted it.
+
+## 📂 Memory Candidates
+
+**Not written this run.** Memory is effectively full (2,194 / 2,200 chars). Nothing on 10-13 cleared
+the "durable + high-value + not already stored" bar enough to justify evicting an existing entry.
+
+- *Candidate (environment, deferred):* "OpenCode on this box exposes only free-tier
+  `google/*` + `opencode/*` models; DeepSeek requires routing OpenCode through OpenRouter
+  (key already in the jimmy profile)." → belongs in the **`opencode` skill**, not always-on memory.
+- *Already covered:* no-writes-without-approval (USER PROFILE), killcorpus paper-only spec (memory),
+  OpenRouter must stay enabled on jimmy (USER PROFILE).
+- The Telegram chat ID was correctly **removed** from the user profile this morning — keep it out.
+
+## ❓ Open Questions
+
+- **OpenCode + DeepSeek — still undecided (asked 19:16, no reply, window expired).** Which model
+  should be OpenCode's default — `deepseek/deepseek-v4.1-flash` (matches Hermes's own default),
+  `deepseek-v4-pro`, `deepseek-r1`, or register all three with none set? And: go / key-only /
+  show-diff-first?
+- **killcorpus "ready for capital" gate spec** — I offered to draft it in-repo (doc only, no wiring,
+  no capital). Draft it, or leave the corpus paper-only with no written gate?
+- **killcorpus open item:** `equity` and `stats` tables are declared but never written (variance is
+  logged textually, not persisted). Fix at a natural gap, or after N=967?
+- **Merge duplicate skills?** `test-driven-development` exists twice at similarity 1.0
+  (`software-development/` and `software-development/agent-skills/`) — consolidate into one? Reply yes
+  and I'll do it. (Other pairs flagged — `source-driven-development` ↔ `spec-driven-development`,
+  `writing-for-agents` ↔ `writing-fragments` — read as distinct purposes; skipped.)
+- **Sorter cron reads `00_system/user-profile.md`, which does not exist.** Create the file, or repoint
+  the skill? (Reported at least twice now.)
+
+## 🚀 Opportunities for Future Improvement
+
+- **Pre-stage the OpenCode diff as a file** in the workspace so a one-word "yes" applies it, with the
+  exact command already smoke-tested against a free model. Removes the second approval round-trip.
+- **Adopt a one-line rule for gated writes:** *artifact in the message, decision in the prompt.*
+  Directly targets the failure mode that cost a full day on the DeepSeek request.
+- **Give the eval loop a written terminal-path companion doc:** the capital-gate spec doubles as the
+  honest answer to "when do we go live," reusable for any future claim.
+- **Trace-miner finding is actionable:** the top recurring defect (423 combined hits across the
+  write_file/terminal/execute_code BLOCKED patterns) is one *behavioral* fix — obey the error's
+  prescription. Worth a standing-principle line in `insights.md` rather than another round of
+  instrumentation.
+
+## 🧰 Skill Review
+
+- Archived this run: **none**. Eligible (idle ≥90d): 0 of 201 skills.
+- Stale watchlist: **0**.
+- Merge candidates reported: `test-driven-development` ↔ `test-driven-development` (1.00, duplicate
+  name across two dirs), `writing-for-agents` ↔ `writing-fragments` (0.91), `source-driven-development`
+  ↔ `spec-driven-development` (0.88), `omh-ralph-driver` ↔ `omh-ralplan-driver` (0.88),
+  `test-driven-development` ↔ `spec-driven-development` (0.87). Only the duplicate-name pair is proposed
+  (see ❓ Open Questions) — merges are never done unattended in the dream loop.
+- Weekly curator: newest report `20261007-195403` is older than yesterday's dream note → not read.

memory-systems/agent-os/dream/insights.md

@@ -22,18 +22,42 @@
 - **One representation, derived not duplicated** (2026-10-12). When a contract lives as schema + template + validator (or any >1 list), derive the others from one source or they drift. Hardening the validator to read its required set from the schema closed the exact drift class that had produced a prior gap.
 - **Evolving instrumentation must record its change-point** (2026-10-12). Instrumentation may change mid-run (e.g. added per-exchange logging), but the autopsy's `evidence_links` must carry every relevant commit hash plus a one-line change-point note ("X logged from commit Y onward; earlier signals have only aggregate"). Honest about instrument evolution without invalidating the pre-registered test.
 
+- **A prescriptive tool error is an instruction, not an obstacle** (2026-10-13). When a tool fails by
+  naming its own fix ("content is required — use action='remove'", "read the file first"), change the
+  argument on the next call. Re-issuing the identical call is the **most-flagged recurring error in
+  this agent's own traces** (2026-10-13 trace-miner: the write_file pagination refusal alone hit 172
+  sessions; blocked-command patterns another ~50) — treat it as a standing behavioral defect, not an
+  accident. Never retry unchanged.
+- **Artifact in the message, decision in the prompt** (2026-10-13). Any approval-gated write must ship
+  its exact diff/payload in the reply *body*; the approval prompt is a bare yes/no. If the reviewer has
+  to open a prompt to see what they're approving, the 60-min window burns and the work stalls a day —
+  that is exactly how the OpenCode+DeepSeek request died on 10-13 with zero writes.
+- **Name the absence of a gate instead of inventing a milestone** (2026-10-13). "When do we go live?"
+  for a paper-only research artifact is a design question, not a status question. The honest answer is
+  the structural one ("no go-live gate exists by design; here are the missing pieces"), followed by an
+  offer to write the gate — that preserves honesty *and* momentum.
+- **Third-party-agent text pasted into a session may be addressed to a different worker** (2026-10-13).
+  Check the addressee before acting on imperative phrasing; a relayed recommendation can look like a
+  direct instruction to Hermes.
+- **Match the destructive action's scope to the promise, then prove it** (2026-10-13). A "strip 2 only"
+  request was honoured as exactly one entry replaced (7 → 7 entries, −18 chars), with the before/after
+  shown. Scope discipline like this is enforced by showing the diff, not by asserting restraint.
+
 ## 🛠️ Technical Notes
 
 - **Kalshi fees (verified 2026-10-10):** taker = `round_up(0.07·C·P·(1−P))`, charged only when you take. **Maker fee = 0 on ~12,500 of 12,699 series** (only ~129 series tax resting orders, quarter rate; cancelling free; 14 niche series fee-free). Polymarket **US** is a separate, thinner, full-KYC venue with contested CA status; Kalshi CA is clean (CFTC DCM).
 - **Headless (`-q`/`--oneshot`) approval gate:** profiles with `approvals.mode` unset default to `manual` → no user → dangerous-pattern commands (`python -c`, `execute_code`, `rm -r`, `kill -9`, heredocs) time out to `BLOCKED`. The `execute_code` fallback is gated too → retry loop that burns context. Fix: `approvals.mode: smart` (+ `command_allowlist` for scoped safe patterns) + tool-loop guardrails (`hard_stop_after: 5`). Cron-safe only after allowlist/config applied.
 - **Cron/unattended tool limits:** `python -c`, `execute_code`, and heredoc script execution are blocked in unattended (-q) runs unless allowlisted; `write_file` refuses overwrite without a prior read (pagination paradox); `terminal` foreground cap 600s (else promoted to tracked background).
-- **killcorpus** (`C:\Users\fight\Projects\killcorpus`): paper-only. Spec `KXBTCD-lag-vs-spot` v1.1.1 (taker primary; maker secondary pending fill model). Harness `harness/paper_trader_instrumented.py` — instrumented (book_read_ts, ntp_offset_ms, spot_age_ms, realized_slippage), variance gate σ²=0.25, latency gates 1000/500/250 ms, fixed N=967 post-registration. Offline selftest green; live feed→fill→settlement path **wired and proven** (settle-through proof 2026-10-11: 40 signals / 5 trades / 5 settled, clock off). Gitea `Tony_tech/killcorpus` push superseded by Contents-API content-mirror. Reference (read-only, do not edit): `polyterm/paper_trader.py`. **Live eval launched 2026-10-11T16:24:28Z** (REG_TS). Supervision: cron `1da28c73cd5f` (15 m, supervisor) + `c7ea39ffb05a` (1 h, health check). Policy: **hold until N=967**; interim K1 non-actionable; only pre-registered early stops (sustained `measurement_artifact`, variance breach → UNDERPOWERED) may halt. Fixes shipped: `b833e3c` (smoke-arg parser), `45f94a5` (DB replay of `counted` on startup). Gitea `Tony_tech/killcorpus` **content-mirrored via Contents API, no `origin`** (git-level link deliberately held). Schema drift seen once: DB `signals` table lacked `book_read_ts_ms` the writer needs — deployed DB and writer must be reconciled at launch.
+- **killcorpus** (`C:\Users\fight\Projects\killcorpus`): paper-only. Spec `KXBTCD-lag-vs-spot` v1.1.1 (taker primary; maker secondary pending fill model). Harness `harness/paper_trader_instrumented.py` — instrumented (book_read_ts, ntp_offset_ms, spot_age_ms, realized_slippage), variance gate σ²=0.25, latency gates 1000/500/250 ms, fixed N=967 post-registration. Offline selftest green; live feed→fill→settlement path **wired and proven** (settle-through proof 2026-10-11: 40 signals / 5 trades / 5 settled, clock off). Gitea `Tony_tech/killcorpus` push superseded by Contents-API content-mirror. Reference (read-only, do not edit): `polyterm/paper_trader.py`. **Live eval launched 2026-10-11T16:24:28Z** (REG_TS). Supervision: cron `1da28c73cd5f` (15 m, supervisor) + `c7ea39ffb05a` (1 h, health check). Policy: **hold until N=967**; interim K1 non-actionable; only pre-registered early stops (sustained `measurement_artifact`, variance breach → UNDERPOWERED) may halt. Fixes shipped: `b833e3c` (smoke-arg parser), `45f94a5` (DB replay of `counted` on startup). Gitea `Tony_tech/killcorpus` **content-mirrored via Contents API, no `origin`** (git-level link deliberately held). Schema drift seen once: DB `signals` table lacked `book_read_ts_ms` the writer needs — deployed DB and writer must be reconciled at launch. **2026-10-13 status:** counted **316/967**, mean +0.0033, realized variance 0.1557 (σ² basis 0.25), one-sided LB −0.0332 → K1 `KILL` **interim, not decisive until N=967**; rate 6.1 markets/hr → **ETA ~Oct 18**; one process all day, no lock errors, log appending.
 - **Agent-loop roles:** planner=Proposer, reviewer=Critic, builder=Executor, jimmy=Recorder. Reviewer residual risk on claim 002: primary and pessimistic fill models *share the same depth/queue observation error*.
 - **killcorpus terminal path — READY (2026-10-12).** Claim 001 (taker) live and untouched all day: 1 process, 0 lock errors, `reg_state.json` created_iso unchanged; counted 66 → 161/967 (~5.4 settled/hr → ~6 days to N=967); interim K1 ignored. Claim 002 (maker / liquidity provision) spec **PASS** after 3 review rounds (`specs/maker-liquidity-provision.spec.yaml`), then **harness machinery built and independently re-verified** (`20bba97`, selftest 43/43) — but the **live data pipeline is NOT wired** (fee→whitelist freeze, book prints/depth/queue, settlement fetch, realized-vol K5); declared machinery-only, not fabricated. `seeded-basket` claim still **blocked on its text** (never paraphrased). Autopsy contract: template `b4eb82c`, schema+drift-proof validator `8050669`, changelog `43fb179`, 3/3 synthetic states schema-clean (`96585df`). Matched-lag counterfactual at n=66: 58/66 survive a 166 ms lag, ~12% exist only un-lagged → *"WEAKENED — measurement-artifact suspect"* (interim, not a gate). Hand-off simulation + `docs/terminal-path-readiness.md` signed; superseded handoff docs deleted, `docs/` = `killcorpus-status.md` + `operating-manual.md`.
 - **brag / MiArc video pipeline — verified gotchas** (2026-10-12). Hyperframes' stacked config: **`data-automation` volume lane supersedes `data-volume`** — setting the "obvious" one silently does nothing (cause of the music-drowns-VO bug). **Animated film grain is a bitrate trap**: static grain took the file 101 MB → 14.7 MB with no visible loss. SVG **`scaleX` scales about user-space origin** → the arc collapsed to the left; fix with `svgOrigin`. Local voice = **Kokoro venv at `C:/Users/fight/.venvs/kokoro`** (`am_michael` male / `af_heart` female); narration must be per-line loudness-normalized (`loudnorm` under-corrects short clips). System Chrome is broken on this box → use Hyperframes' managed headless shell. Verify pacing (static-hold), mix separation, voice presence (cross-correlation r), and encode size *on the delivered file*.
 - **Provider fallback incident (2026-10-12):** `deepseek/deepseek-v4-flash-0731` (routeapi) went unavailable on billing/quota; role profiles silently failed over to Qwen on the brother-5090 rig for ~18 min. Check the profiles' actual model on health checks.
+- **OpenCode on this box (2026-10-13):** `opencode models` exposes 51 models — 39 `google/*` + 12 `opencode/*`, **all free tier; zero DeepSeek** (`opencode/deepseek-v4-flash|v4.1-flash|v4-pro` all return `UnknownError` despite appearing in `opencode.jsonc` — no entitlement; a free model ran `OC_SMOKE_OK`, so the CLI is fine). The only working route to OpenCode+DeepSeek is **OpenRouter**: append `OPENROUTER_API_KEY` to `~/.config/opencode/.env` (shell append to that file is blocklisted — use file I/O), add an `openrouter` provider block + `"model"` to `~/.config/opencode/opencode.jsonc`, back both up first. Auth/config live at `~/.config/opencode/`; auth DB `~/.local/share/opencode/auth.json` is CLI-read-only. **Held pending Tony's approval** (clarify expired 10-13 20:18).
 
 ## 🧰 Skills / Tooling Notes
+- **Skill-review telemetry (2026-10-13):** 201 skills, 0 eligible for archive, 0 stale-watchlist; merge candidates flagged were mostly false positives (pairs that share a domain but not a purpose — `source-driven-development`/`spec-driven-development`, `writing-for-agents`/`writing-fragments`, `omh-ralph-driver`/`omh-ralplan-driver`). The one real hit is a **duplicate name**: `test-driven-development` at similarity 1.00 across two directories.
+- **Recurring-defect reality check (2026-10-13 trace miner):** 305 sessions / 21,833 messages → 25 findings, and the top finding by an order of magnitude is *the same* behavioral error in three tool families — ignoring a prescriptive tool error and re-issuing the call (`write_file` pagination refusal 172 sessions; `terminal` blocked-command 32+10+6; `execute_code` blocked 26). One behavioral fix, not more instrumentation.
 - **brag skill split (2026-10-12, done by hand on approval):** official hub skill `brag` installed as authority (`hermes skills install official/creative/brag`); local skill renamed `brag-launch-video` → **`brag-local-addendum`** and slimmed 34.1 KB → 15.9 KB (box-specific deltas only). Lint: a frontmatter-only rename is invalid — skill name must match its directory.
 
 ## 🧵 Open Threads
@@ -43,3 +67,8 @@
 - killcorpus **terminal path READY (2026-10-12)** — the loop will not idle at N=967. Autopsy template + drift-proof validator + 3 synthetic dry-runs + hand-off simulation all done and signed; claim 002 (maker) spec PASS, harness machinery built (live feed NOT wired — held pending explicit green-light); `seeded-basket` blocked on its text.
 - killcorpus **open items**: git-level link (`origin`) held — decide at first autopsy or sooner; maker live-feed wiring held for green-light; superseded handoff docs were **deleted 2026-10-12** (`docs/` now = `killcorpus-status.md` + `operating-manual.md`).
 - Dream Mode live as of 2026-10-10 (skill + `skill_review.py` + 2 AM cron + `dream/`). Note for 10-12 = third run.
+- **OpenCode + DeepSeek — PENDING Tony (opened 2026-10-13 19:16).** Needs: (a) which DeepSeek as default — `v4.1-flash` (matches Hermes default), `v4-pro`, `r1`, or all three with none set; (b) go / key-only / show-diff-first. Exact diff is recorded under 🛠️ Technical Notes. No writes made.
+- **killcorpus "ready for capital" gate — offered 2026-10-13, unanswered.** Draft a formal in-repo gate spec (doc only: K1–K5 at pre-registered N → matched-lag clean → replication on a second regime + sample → live-fill-validated execution path with verified fee schedule → risk limits + kill-switch → capped live tranche with pre-registered stop)? Or keep the corpus paper-only with no written gate?
+- **killcorpus minor open item:** `equity` + `stats` tables declared but never written (variance logged textually). Fix at a natural gap vs after N=967 — Tony's call.
+- **Sorter cron gap (open ≥2 reports):** the daily Sorter triage reads `00_system/user-profile.md`, which does not exist (vault root is `C:\Users\fight\Documents\Obsidian Vault`). Create the file or repoint the skill.
+- **Duplicate skill:** `test-driven-development` exists twice at similarity 1.00 (`software-development/` and `software-development/agent-skills/`). Proposed for consolidation; not merged unattended.