@davmash/bygone 0.9.4 → 0.9.7

package/out/standalone-main.js

@@ -18785,7 +18785,7 @@ var require_package = __commonJS({
       displayName: "Bygone",
       desktopName: "com.davidmashburn.bygone.desktop",
       description: "See how change happened. Visual diff and file history for VS Code.",
-      version: "0.9.4",
+      version: "0.9.7",
       author: "David Mashburn",
       license: "MIT",
       private: false,
@@ -32133,6 +32133,67 @@ ${error.message}`);
         assert.ok(["auto", "scroll"].includes(initial.content.overflowY), "The narrative content uses scrolling");
         assert.equal(initial.activeKeys.length, 1, "Exactly one reading item is active initially");
         assert.equal(initial.activeKeys[0], "title", "The title starts as the active reading item");
+        const originalHeight = await evaluate("document.querySelector('#tour-narrative').getBoundingClientRect().height");
+        const originalPreference = await evaluate("localStorage.getItem('bygone.tourNarrativeHeight')");
+        const resizeKey = async (key) => {
+          await evaluate(`document.querySelector('#tour-narrative-resizer').dispatchEvent(new KeyboardEvent('keydown', { bubbles: true, key: ${JSON.stringify(key)} }))`);
+          await waitForRaf();
+        };
+        const readSplit = () => evaluate(`(() => {
+            const narrative = document.querySelector('#tour-narrative').getBoundingClientRect();
+            const code = document.querySelector('#container').getBoundingClientRect();
+            const resizer = document.querySelector('#tour-narrative-resizer');
+            const handle = resizer.getBoundingClientRect();
+            return { height: narrative.height, codeTop: code.top, codeHeight: code.height,
+                handleY: handle.top + handle.height / 2, handleX: handle.left + handle.width / 2,
+                value: Number(resizer.getAttribute('aria-valuenow')),
+                max: Number(resizer.getAttribute('aria-valuemax')),
+                stored: Number(localStorage.getItem('bygone.tourNarrativeHeight')),
+                cursor: getComputedStyle(resizer).cursor };
+        })()`);
+        const assertSplit = (split) => {
+          assert.ok(Math.abs(split.codeTop - split.height) <= 1, "Code starts at the narrative boundary");
+          assert.ok(Math.abs(split.handleY - split.height) <= 1, "The divider tracks the narrative boundary");
+          assert.equal(split.value, split.height, "The separator exposes its current height");
+          assert.ok(split.codeHeight >= 180, "Resizing preserves room for code");
+        };
+        const dragSplit = async (height) => {
+          const split = await readSplit();
+          const x = Math.round(split.handleX);
+          const y = Math.round(split.handleY);
+          browserContents.sendInputEvent({ type: "mouseMove", x, y });
+          browserContents.sendInputEvent({ type: "mouseDown", button: "left", clickCount: 1, x, y });
+          browserContents.sendInputEvent({ type: "mouseMove", x, y: height });
+          await waitFor(`Number(document.querySelector('#tour-narrative-resizer').getAttribute('aria-valuenow')) === ${height}`, "dragged narrative boundary");
+          browserContents.sendInputEvent({ type: "mouseUp", button: "left", clickCount: 1, x, y: height });
+          await waitFor("!document.body.classList.contains('is-resizing-tour-narrative')", "narrative drag completion");
+          await waitForRaf();
+        };
+        try {
+          assert.equal((await readSplit()).cursor, "row-resize", "The narrative divider is draggable");
+          await resizeKey("Home");
+          let split = await readSplit();
+          assert.equal(split.height, 180, "Home sets the minimum narrative height");
+          assertSplit(split);
+          await resizeKey("End");
+          split = await readSplit();
+          assert.equal(split.height, split.max, "End sets the maximum narrative height");
+          assertSplit(split);
+          await resizeKey("ArrowUp");
+          assert.equal((await readSplit()).height, split.max - 16, "ArrowUp reduces the narrative height");
+          await resizeKey("ArrowDown");
+          assert.equal((await readSplit()).height, split.max, "ArrowDown increases the narrative height");
+          const target = Math.round((180 + split.max) / 2);
+          await dragSplit(target);
+          split = await readSplit();
+          assertSplit(split);
+          assert.equal(split.stored, target, "Dragging saves the narrative height");
+          assert.deepEqual((await read()).activeKeys, initial.activeKeys, "Resizing preserves the selected passage");
+          assert.deepEqual((await read()).url, initial.url, "Resizing preserves the reading URL");
+        } finally {
+          await dragSplit(Math.round(originalHeight));
+          await evaluate(originalPreference === null ? "localStorage.removeItem('bygone.tourNarrativeHeight')" : `localStorage.setItem('bygone.tourNarrativeHeight', ${JSON.stringify(originalPreference)})`);
+        }
         assert.equal(initial.items.filter((item) => item.kind === "title").length, 1, "The title item is unique");
         assert.equal(initial.items.filter((item) => item.kind === "chapter").length, 2, "Each chapter has a reading item");
         assert.equal(initial.items.filter((item) => item.kind === "scene").length, 2, "Each scene has a reading item");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@davmash/bygone",
-  "version": "0.9.4",
+  "version": "0.9.7",
   "description": "See how change happened. Visual diff and file history.",
   "author": "David Mashburn",
   "license": "MIT",

package/skills/pr-tour-guide/SKILL.md

@@ -134,8 +134,50 @@ Then read patches only for likely narrative-bearing files. Account explicitly fo
 
 Compiled tours and context dossiers are large because they embed source snapshots. Inspect them progressively and do not load every patch unless the narrative really needs it.
 
+## Gather ticket and PR framing
+
+When available, read the ticket and PR context supplied by the user or directly
+linked from the change, using accessible read-only sources. Follow relevant
+parent-project or review links when they explain the change; keep discovery
+bounded to this work. Missing metadata should not block a useful code tour.
+
+Capture the facts that help a reader understand the change:
+
+- **Ticket:** identifier, title, problem and requested outcome, relevant details
+  or acceptance criteria, creator/requester and assignee as distinct roles,
+  creation date or relevant timeline, and its place in a parent project, epic,
+  or larger initiative.
+- **PR:** number, title, URL, author, relevant creation/merge dates, associated
+  ticket, and actual review history: who reviewed, when, their recorded outcome,
+  and consequential feedback or resulting changes.
+
+Be explicit about whose ticket it was, who authored the PR, and who reviewed
+it when the sources establish those roles. Credit implementation contributors
+when known; PR authorship alone does not establish sole implementation credit.
+A requested reviewer is not an actual reviewer; a comment is not an approval. Do not assume an earlier review
+covers the current head or an entire multi-PR range. For stacked work, keep
+ticket, author, timing, and review provenance attached to the correct PR.
+
+Link the supporting ticket, PR, and review sources in the tour's narrative.
+Distinguish the ticket's requested outcome and the author's stated intent from
+behavior established by code and tests. Do not invent ownership, dates, project
+relationships, ticket associations, review status, or approval. Briefly disclose
+material gaps or conflicting context where they affect the explanation; omit
+irrelevant unavailable fields rather than filling the tour with placeholders.
+
 ## Plan the explanation
 
+Begin with an opening slide that summarizes the high-level context before the
+implementation: the problem, its place in the larger project, the ticket and
+PR relationship, and what this change contributes. Include relevant people,
+timing, and review status concisely; put detailed provenance beside the later
+claims it explains. If separate authored modes have independent entry points,
+give each enough opening context to stand on its own.
+
+Use the first scene's summary/bullets or equivalent supported narrative fields
+for this opening; do not invent a slide kind or metadata keys. Keep source
+anchors for code claims and source links for external context distinct.
+
 Identify the smallest set of reviewer questions that makes the change understandable. Organize by conceptual dependency rather than filename order. Usually move through:
 
 1. motivation, contract, or invariant;
@@ -294,7 +336,10 @@ After structural validation, check that:
 
 Treat this as a required self-audit, not a claim the validator can prove. For each item, cite concrete evidence you actually opened or mark it not applicable; the hand-off must distinguish verified findings from interpretation.
 
-- the first step establishes enough context for later steps;
+- the opening slide establishes the problem, project context, and available
+  ticket/PR provenance before the first implementation step;
+- ticket ownership, dates, and actual review claims are traceable to opened
+  sources and scoped to the PR/revision they describe;
 - chapter boundaries follow conceptual transitions rather than a fixed count or one-scene-per-chapter pattern;
 - important production behavior is not hidden in the complete Files rail;
 - tests are connected to the behavior they prove;
@@ -361,6 +406,7 @@ Report:
   counts, plus compiled counts when generated complete-change or per-mode
   scenes change them;
 - omitted or unread evidence;
+- ticket/PR context sources used and material unavailable or conflicting context;
 - validation and visual verification performed;
 - whether generated files are temporary, uncommitted, committed, or pushed.
 

package/web/index.html

@@ -137,6 +137,7 @@
         </div>
         <div id="tour-narrative-content" class="tour-narrative-content" tabindex="0" role="region" aria-label="Tour reading flow"></div>
     </section>
+    <div id="tour-narrative-resizer" class="tour-narrative-resizer" role="separator" aria-label="Resize tour text" title="Resize tour text (Up/Down; Home/End)" aria-controls="tour-narrative" aria-orientation="horizontal" aria-valuemin="180" tabindex="0"></div>
     <div class="web-toolbar">
         <div class="web-toolbar-group">
             <button id="web-compare-test" type="button" title="Compare sample files">Compare Test Files</button>

package/web/presenter.css

@@ -398,6 +398,29 @@ body.tour-mode #container {
     display: none;
 }
 
+.tour-narrative-resizer {
+    position: fixed;
+    z-index: 120;
+    top: calc(var(--tour-narrative-height) - 4px);
+    right: 0;
+    left: var(--tour-rail-width);
+    height: 8px;
+    cursor: row-resize;
+    touch-action: none;
+}
+
+.tour-narrative-resizer:hover,
+.tour-narrative-resizer:focus-visible,
+body.is-resizing-tour-narrative .tour-narrative-resizer {
+    background: rgba(169, 159, 255, 0.75);
+    outline: none;
+}
+
+body:not(.tour-mode) .tour-narrative-resizer,
+body.tour-derived-mode .tour-narrative-resizer {
+    display: none;
+}
+
 .tour-narrative-toolbar {
     display: flex;
     min-width: 0;
@@ -1364,6 +1387,7 @@ body.tour-directory-file-open #file-info { display: none; }
     }
 
     .tour-sidebar-resizer { display: none; }
+    .tour-narrative-resizer { left: 0; }
     .tour-narrative { top: 0; left: 0; height: min(38vh, 360px); padding: 10px 14px 12px; }
     .tour-narrative-toolbar { gap: 6px; }
     .tour-narration-controls select { max-width: 150px; }