@davmash/bygone 0.9.5 → 0.9.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,24 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
+ ## 0.9.8
6
+
7
+ - Rendered Markdown links as clickable links in tour narrative prose
8
+ - Kept Scene context visible at the top of the reading pane while scrolling through each step
9
+ - Updated extension packaging tooling and cache dependencies to resolve high-severity advisories
10
+
11
+ macOS desktop downloads are unsigned and not notarized. If Gatekeeper reports
12
+ the app as damaged, run `xattr -cr /Applications/Bygone.app`, then reopen it.
13
+
14
+ ## 0.9.7
15
+
16
+ - Published the tour text/code resizing fix and expanded ticket, project, and PR context guidance introduced in 0.9.6
17
+
18
+ ## 0.9.6
19
+
20
+ - Restored dragging and keyboard resizing between tour text and code, with a saved height preference
21
+ - Added ticket, project, PR authorship, and review context guidance to the bundled tour skill
22
+
5
23
  ## 0.9.5
6
24
 
7
25
  - Restored the full commit message, author and email, date, full SHA, and parents in tour and comparison commit details
@@ -205,6 +205,8 @@ including why the focused code matters and any rationale or tradeoff that the
205
205
  source supports. Keeping that explanation beside `focus` lets the reader assess
206
206
  the claim while the code is visible and avoids repeating it in scene framing.
207
207
 
208
+ Narrative text supports inline Markdown links such as `[ticket](https://example.com/ticket)`. HTTP and HTTPS destinations open outside the tour; link labels remain visible and clickable during narration highlighting. Authored HTML, other URL schemes, and local-file destinations are treated as plain text. This is link support, not a general Markdown renderer.
209
+
208
210
  The source schema has no ad hoc `notes` field. In v3, use the top-level `review`
209
211
  block below for evidence-linked review observations and unresolved questions;
210
212
  do not present those questions as settled step rationale.