threadnote 0.6.0 → 0.6.2

package/docs/agent-instructions.md

@@ -21,9 +21,17 @@ At the start of a non-trivial task, recall relevant context before making change
 - the current repo and branch;
 - recent handoffs;
 - durable feature memories for the branch, feature name, project/topic, or issue;
+- seeded project guidance under `viking://resources/repos/<project>` — README, AGENTS.md, CLAUDE.md, SKILL.md, docs/\*\*
+  — for canonical conventions, test commands, release process, on-call runbooks, and anything the team has checked into
+  the repo;
 - task-specific skills or workflow guidance;
 - user or team preferences that may affect the work.
 
+Include the repo or project name as a token in the recall query so the project-guidance pass fires. `recall_context`
+runs a parallel scoped search against `viking://resources/repos/<project>` whenever the query mentions a seeded project
+name, so memories AND project documentation come back in the same response. Treat seeded resources as the canonical
+source for "how does this repo do X" and personal memories as in-flight or per-author context layered on top.
+
 When a recalled handoff describes an active branch or feature, do a second recall for durable memories about that
 feature before coding. The handoff tells you the current work state; durable feature memories tell you the design,
 decisions, invariants, interfaces, and gotchas that should survive beyond one session.

package/docs/index.html

@@ -78,7 +78,11 @@
       body {
         line-height: 1.55;
         font-size: clamp(15px, 1.05vw, 17px);
-        overflow-x: hidden;
+        overflow-x: clip;
+      }
+
+      html {
+        overflow-x: clip;
       }
 
       ::selection {
@@ -117,6 +121,10 @@
         padding: 1em 1.2em;
         overflow-x: auto;
         line-height: 1.55;
+        /* Without this, a single long unbreakable line (curl URLs, etc.)
+           pushes the pre wider than its container and out of the viewport on
+           mobile. With it, the pre scrolls internally instead. */
+        max-width: 100%;
       }
 
       pre code {
@@ -148,6 +156,10 @@
         display: flex;
         flex-direction: column;
         justify-content: center;
+        /* Default flex/block intrinsic min-width is the widest child, which
+           lets long unbreakable mono lines (URLs, MCP calls) make the inner
+           wider than its declared 100%. Hard-cap it. */
+        min-width: 0;
       }
 
       .slide-eyebrow {
@@ -222,29 +234,14 @@
         align-items: flex-start;
       }
 
-      .page-logo {
-        position: fixed;
-        top: 1.5rem;
-        left: 1.5rem;
-        width: 220px;
-        height: 220px;
-        z-index: 40;
-        pointer-events: none;
-      }
-
-      .page-logo img {
-        width: 100%;
-        height: 100%;
+      .hero-logo {
         display: block;
-      }
-
-      @media (max-width: 720px) {
-        .page-logo {
-          width: 120px;
-          height: 120px;
-          top: 1rem;
-          left: 1rem;
-        }
+        width: clamp(140px, 18vw, 220px);
+        height: auto;
+        margin-bottom: 1.5rem;
+        /* Override `#hero .slide-inner { align-items: flex-start }` for just
+           this child so the logo sits centered above the left-aligned title. */
+        align-self: center;
       }
 
       .hero-title-gradient {
@@ -504,35 +501,89 @@
         border-radius: var(--radius-lg);
         padding: 1.5rem;
         display: grid;
-        gap: 0.6rem;
+        gap: 0.75rem;
         transition: border-color 0.2s ease;
+        /* Let the grid track shrink to its container width rather than to the
+           widest mono child. Without this, long MCP call/response lines push
+           the grid item past viewport and the page scrolls horizontally on
+           mobile. */
+        min-width: 0;
       }
 
       .vignette:hover {
         border-color: var(--accent-line);
       }
 
-      .vignette .v-prompt {
+      .vignette .v-say {
         font-style: italic;
+        font-size: 0.96rem;
         color: var(--text);
-        font-size: 1rem;
+        background: rgba(255, 255, 255, 0.03);
+        border-left: 3px solid var(--accent);
+        border-radius: 4px;
+        padding: 0.55rem 0.85rem;
       }
 
-      .vignette .v-answer {
+      .vignette .v-auto {
+        font-style: italic;
         color: var(--muted);
-        font-size: 0.95rem;
       }
 
-      .vignette .v-cmd {
+      .vignette pre.v-call,
+      .vignette pre.v-response {
         font-family: var(--font-mono);
-        font-size: 0.82rem;
-        color: var(--accent);
-        padding: 0.45rem 0.75rem;
+        font-size: 0.78rem;
         background: var(--code-bg);
+        padding: 0.55rem 0.75rem;
         border-radius: 6px;
         border: 1px solid var(--line);
-        white-space: nowrap;
+        border-left: 1px solid var(--line);
+        white-space: pre-wrap;
+        word-break: break-word;
         overflow-x: auto;
+        max-width: 100%;
+        line-height: 1.45;
+        margin: 0;
+      }
+
+      .vignette .v-call {
+        color: var(--accent);
+      }
+
+      .vignette .v-response {
+        color: var(--muted);
+      }
+
+      .vignette .v-say::before,
+      .vignette .v-call::before,
+      .vignette .v-response::before {
+        display: block;
+        font-family: var(--font-mono);
+        font-size: 0.68rem;
+        letter-spacing: 0.12em;
+        text-transform: uppercase;
+        color: var(--muted);
+        font-style: normal;
+        margin-bottom: 0.35rem;
+      }
+
+      .vignette .v-say::before {
+        content: 'You ask';
+        color: var(--accent);
+      }
+
+      .vignette .v-call::before {
+        content: 'Agent calls';
+      }
+
+      .vignette .v-response::before {
+        content: 'MCP returns';
+      }
+
+      .vignette .v-answer {
+        color: var(--muted);
+        font-size: 0.95rem;
+        margin-top: 0.25rem;
       }
 
       /* side nav dots */
@@ -695,10 +746,6 @@
   <body>
     <div class="progress"><div class="progress-bar" id="progressBar"></div></div>
 
-    <div class="page-logo" aria-hidden="true">
-      <img src="threadnote-logo-inverted.svg" alt="" />
-    </div>
-
     <nav class="deck-nav" aria-label="Section progress">
       <a href="#hero" data-label="Intro"><span>Intro</span></a>
       <a href="#problem" data-label="Problem"><span>Problem</span></a>
@@ -710,8 +757,8 @@
       <a href="#seed" data-label="Seed"><span>Seed</span></a>
       <a href="#update" data-label="Update"><span>Update</span></a>
       <a href="#lifecycle" data-label="Lifecycle"><span>Lifecycle</span></a>
-      <a href="#use-cases" data-label="Use cases"><span>Use cases</span></a>
       <a href="#share" data-label="Share"><span>Share</span></a>
+      <a href="#use-cases" data-label="Use cases"><span>Use cases</span></a>
       <a href="#close" data-label="Get started"><span>Start</span></a>
     </nav>
 
@@ -719,6 +766,7 @@
       <!-- 1. HERO -->
       <section id="hero" class="slide">
         <div class="slide-inner">
+          <img class="hero-logo" src="threadnote-logo-inverted.svg" alt="" aria-hidden="true" />
           <h1 class="hero-title-gradient">
             Shared local context<br />for <em class="hero-accent">development agents</em>.
           </h1>
@@ -727,7 +775,7 @@
             team-shared decisions — recallable from any session, on any agent, in any worktree.
           </p>
           <div class="cta-row">
-            <span class="pill">v0.5.0 · local-first · MIT</span>
+            <span class="pill"><span id="version-tag">v0.6.1</span> · local-first · MIT</span>
           </div>
         </div>
         <div class="scroll-cue">scroll ↓ &nbsp;·&nbsp; <span class="kbd">↓</span> / <span class="kbd">j</span></div>
@@ -1254,75 +1302,10 @@ threadnote remember \
         </div>
       </section>
 
-      <!-- 11. USE CASES -->
-      <section id="use-cases" class="slide">
-        <div class="slide-inner">
-          <span class="slide-eyebrow">10 · Real-world use cases</span>
-          <h2>Where it actually pays off.</h2>
-
-          <div class="vignettes">
-            <div class="vignette reveal">
-              <div class="v-prompt">"Continue the feature from yesterday."</div>
-              <div class="v-answer">
-                Fresh session, fresh agent. Threadnote recalls the active handoff for the branch plus the durable
-                feature memory: design decisions, the open PR, what's left, what just failed in CI. No re-explaining.
-              </div>
-              <div class="v-cmd">threadnote recall --query "&lt;branch&gt; latest handoff"</div>
-            </div>
-
-            <div class="vignette reveal">
-              <div class="v-prompt">"What did we conclude about that prod-on-call thing?"</div>
-              <div class="v-answer">
-                The sanitized handoff from the on-call escalation is still there. Re-open the same Slack thread three
-                weeks later; the durable feature memory points your agent at the right files and the resolution.
-              </div>
-              <div class="v-cmd">threadnote recall --query "export workflow timeout on-call findings"</div>
-            </div>
-
-            <div class="vignette reveal">
-              <div class="v-prompt">"Switch from Codex to Claude mid-task."</div>
-              <div class="v-answer">
-                Codex stores a handoff before pausing. Claude opens the same MCP layer, recalls the handoff plus the
-                durable memory, picks up the test command and the open blocker without you typing them again.
-              </div>
-              <div class="v-cmd">threadnote handoff --task "..." --next-step "..."</div>
-            </div>
-
-            <div class="vignette reveal">
-              <div class="v-prompt">"Onboard a new teammate to a feature."</div>
-              <div class="v-answer">
-                Publish the feature's durable memory to the team repo with <code>share publish</code>. Their agent
-                pulls it on the next <code>share sync</code> and recall surfaces it alongside their own personal
-                memories — no DM forwarding, no PDF dumping.
-              </div>
-              <div class="v-cmd">threadnote share publish viking://user/&lt;you&gt;/memories/durable/...</div>
-            </div>
-
-            <div class="vignette reveal">
-              <div class="v-prompt">"Compaction is about to nuke the context."</div>
-              <div class="v-answer">
-                Before context fills up, the agent stores a handoff. The next turn after compaction recalls it — the
-                summary covers the conversation arc, threadnote covers the durable facts the summary couldn't keep.
-              </div>
-              <div class="v-cmd">threadnote handoff --project &lt;repo&gt; --topic &lt;feature&gt; ...</div>
-            </div>
-
-            <div class="vignette reveal">
-              <div class="v-prompt">"Where does this repo run its release notes?"</div>
-              <div class="v-answer">
-                You discovered it the hard way last time. Tell your agent to <code>remember</code> the fact. Next time
-                anyone asks, the agent finds it in two seconds without grepping the wiki.
-              </div>
-              <div class="v-cmd">threadnote remember --kind durable --topic release-process ...</div>
-            </div>
-          </div>
-        </div>
-      </section>
-
-      <!-- 12. SHARE -->
+      <!-- 11. SHARE -->
       <section id="share" class="slide">
         <div class="slide-inner">
-          <span class="slide-eyebrow">11 · Sharing across the team</span>
+          <span class="slide-eyebrow">10 · Sharing across the team</span>
           <h2>Curated memories. Yours to push. Theirs to pull.</h2>
           <p class="lead">
             <code>threadnote share</code> publishes a subset of durable memories into a git repo so other engineers'
@@ -1409,6 +1392,81 @@ threadnote remember \
         </div>
       </section>
 
+      <!-- 12. USE CASES -->
+      <section id="use-cases" class="slide">
+        <div class="slide-inner">
+          <span class="slide-eyebrow">11 · Real-world use cases</span>
+          <h2>What you say. What the agent does.</h2>
+          <p class="lead">
+            You don't run threadnote commands yourself. You talk to your agent the way you already do; the agent calls
+            the MCP layer and the memory stays in sync across sessions, agents, and teammates.
+          </p>
+
+          <div class="vignettes">
+            <div class="vignette reveal">
+              <div class="v-say">Continue where we left off on this branch.</div>
+              <pre class="v-call">recall_context({query: "&lt;branch&gt; latest handoff durable feature memory"})</pre>
+              <pre class="v-response">→ viking://user/you/memories/handoffs/active/&lt;branch&gt;/auto-precompact.md
+→ viking://user/you/memories/durable/projects/&lt;repo&gt;/&lt;feature&gt;.md</pre>
+              <div class="v-answer">
+                Fresh session, fresh agent. It reads both pointers, picks up the design decisions, the open PR, what's
+                left to test, and what just failed in CI. No re-explaining.
+              </div>
+            </div>
+
+            <div class="vignette reveal">
+              <div class="v-say">Save where we are — I'm switching to another agent.</div>
+              <pre class="v-call">remember_context({kind: "handoff", project: "&lt;repo&gt;", topic: "&lt;feature&gt;", text: "..."})</pre>
+              <pre class="v-response">Stored: viking://user/you/memories/handoffs/active/&lt;repo&gt;/&lt;feature&gt;.md</pre>
+              <div class="v-answer">
+                Open the next agent — the SessionStart hook recalls the same handoff and the durable memory. It picks
+                up the test command and the open blocker without you retyping them.
+              </div>
+            </div>
+
+            <div class="vignette reveal">
+              <div class="v-say">Share this feature's design memory with the team.</div>
+              <pre class="v-call">share_publish({uri: "viking://user/you/memories/durable/projects/&lt;repo&gt;/&lt;feature&gt;.md"})</pre>
+              <pre class="v-response">Published → shared/&lt;team&gt;/durable/projects/&lt;repo&gt;/&lt;feature&gt;.md
+git push: ok</pre>
+              <div class="v-answer">
+                The memory lands in the team git repo. A teammate's next <code>share sync</code> pulls it; their
+                recall surfaces it alongside their own memories — no DM forwarding, no PDF dumping.
+              </div>
+            </div>
+
+            <div class="vignette reveal">
+              <div class="v-say v-auto">(automatic — the PreCompact hook fires before context compaction)</div>
+              <pre class="v-call">remember_context({kind: "handoff", project: "&lt;repo&gt;", topic: "auto-precompact", text: "..."})</pre>
+              <pre class="v-response">Stored: viking://user/you/memories/handoffs/active/&lt;repo&gt;/auto-precompact.md</pre>
+              <div class="v-answer">
+                Compaction summarizes the conversation arc but loses the durable facts. Threadnote's hook captures them
+                first; the post-compaction turn recalls them and resumes without amnesia.
+              </div>
+            </div>
+
+            <div class="vignette reveal">
+              <div class="v-say">Remember that this repo cuts release notes from CI via gh release create.</div>
+              <pre class="v-call">remember_context({kind: "durable", project: "&lt;repo&gt;", topic: "release-process", text: "..."})</pre>
+              <pre class="v-response">Stored: viking://user/you/memories/durable/projects/&lt;repo&gt;/release-process.md</pre>
+              <div class="v-answer">
+                Next time anyone asks where releases happen, the agent finds it in two seconds. No grepping the wiki.
+              </div>
+            </div>
+
+            <div class="vignette reveal">
+              <div class="v-say">What did we conclude about the export-workflow timeout?</div>
+              <pre class="v-call">recall_context({query: "export workflow timeout findings"})</pre>
+              <pre class="v-response">→ viking://user/you/memories/durable/projects/&lt;repo&gt;/export-timeout.md (score 0.71)</pre>
+              <div class="v-answer">
+                Re-open the same investigation three weeks later; the durable memory points your agent at the right
+                files and the resolution. The trail doesn't decay.
+              </div>
+            </div>
+          </div>
+        </div>
+      </section>
+
       <!-- 13. CLOSE -->
       <section id="close" class="slide">
         <div class="slide-inner">
@@ -1538,6 +1596,27 @@ threadnote doctor --dry-run</code></pre>
           }
         });
       })();
+
+      // Replace the hardcoded version pill with whatever npm currently
+      // serves as latest. Fails silently and keeps the fallback text on any
+      // network or registry error — the deck must render even offline.
+      (async () => {
+        const tag = document.getElementById('version-tag');
+        if (!tag) return;
+        try {
+          const response = await fetch('https://registry.npmjs.org/threadnote/latest', {
+            headers: {accept: 'application/json'},
+            signal: AbortSignal.timeout(3000),
+          });
+          if (!response.ok) return;
+          const data = await response.json();
+          if (typeof data.version === 'string' && data.version.length > 0) {
+            tag.textContent = 'v' + data.version;
+          }
+        } catch {
+          // Keep the static fallback.
+        }
+      })();
     </script>
   </body>
 </html>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "threadnote",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "type": "commonjs",
   "main": "dist/threadnote.cjs",
   "description": "Shared local context and handoffs for development agents",