Add summary: to character templates; fix two bugs that were hiding it
Add a summary: field (with a short explanatory comment) to
01_character_template.md, and fill the field in on the two shipped
examples, 01_protagonist.md and 02_antagonist.md. Documented in the
Story Bible README's "Adding a New Character" example and its new
"Automatic Linking in the Draft" section, and in the main README's
Story Bible docs.
While wiring this up against the real bundled template rather than a
hand-written test fixture, found two bugs that were silently defeating
last session's auto-linking feature for every project made from that
template:
- extract_from_frontmatter() only read a title: field for an item's
name, but every bundled Story Bible template — character, location,
lore, object, all of them — writes name:, never title:. Every real
item's display name (and therefore everything matched against it in
prose) was falling back to a garbled, uncapitalized filename guess
instead. Now name: is read (title: still works too, for a sheet that
uses that word instead).
- build_editor_job()'s fast path skipped straight to an unformatted
run whenever there were no grammar/spelling issues and no active
search — without checking whether there was a Story Bible reference
to highlight. A name with no spelling issue of its own (which is
most of them) never got its purple background, and with it no visible
way to find the hover card that depends on it.
Both were invisible in the unit tests added last session because they
exercised find_references() directly against a hand-built index, never
through StoryBibleIndex::build() against real files, and the manual
smoke test happened to use a name ("Bixby") that the spell checker
flagged anyway — which incidentally kept the fast path from short-
circuiting. Added a disk-built-index test and a fast-path regression
test so both stay caught.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -75,6 +75,7 @@ The Story Bible is a comprehensive reference system that helps you maintain cons
|
||||
---
|
||||
id: unique_id
|
||||
name: Character Name
|
||||
summary: "One line the app can show in a hover card"
|
||||
slug: character-name
|
||||
type: protagonist|antagonist|ally|enemy|mentor
|
||||
status: active|draft|deceased|retired
|
||||
@@ -142,6 +143,17 @@ Use `[[Link Text|file-name]]` or `[[file-name]]` to create cross-references:
|
||||
- **Related Event:** [[The War of Ashes|history/war_of_ashes]]
|
||||
```
|
||||
|
||||
### Automatic Linking in the Draft
|
||||
The app does not require `[[wiki-links]]` to connect a draft to the Story
|
||||
Bible — a name written in ordinary prose ("**Bixby** stood at the door") is
|
||||
matched automatically against every entry's `name:` and `aliases:`, as long
|
||||
as it's spelled and capitalized the same way in both places. Hovering a
|
||||
matched name shows a card with the entry's `summary:` field and a link that
|
||||
opens the full sheet; `[[wiki-links]]` and `@mentions` still work too, and
|
||||
take priority if they ever land on the same word. A character sheet with no
|
||||
`summary:` still gets matched and links open fine — the card just says so
|
||||
and lets you add one.
|
||||
|
||||
### Mermaid Diagrams
|
||||
Create visual relationship maps and timelines:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user