rbrooks/Quest-Board
Watch
1
0
Fork
You've already forked Quest-Board
 0
Code Issues 58 Pull requests 7 Projects Releases 76 Packages Wiki Activity Actions

Names without the AI: a built-in name generator with extensive lists (hybrid) #1257

New issue
Closed
opened 2026-10-28 04:57:53 +00:00 by claude-bot · 9 comments
claude-bot commented 2026-10-28 04:57:53 +00:00
Collaborator
Copy link

Owner's decision, 2026-10-28: build a list-based name generator, in the style of fantasynamegenerators.com, into Prep → Names. Hybrid: names always come from the generator, and an AI (when configured) only writes a description of a name the GM picks. For v4.7.0.

Why:

  1. Repetition. AI models surface the same names over and over; the owner has been offered the same names many times. A disallow list sent to the AI would only add token cost.
  2. Cost. No tokens per draw, which matters for the hosted service (AI priced by usage, #642).
  3. It works with no AI at all. Today Prep → Names fails when no LLM is configured.

Today: generation_service tool names → audio_service.generate_name_options() (LLM, JSON schema, names plus a 1–2 sentence description per kind), pre-fetched into a Redis pool by planning_tasks.prefetch_name_options. The UI is pages/prep/tools/Names.jsx, with kinds from ENTRY_TYPE_LABELS and an optional "feel". Instant NPC (instant_npc) is separate and out of scope here.

Requirements:

  • Extensive lists. Variety is the point. Each person style needs enough pieces that the combinations run to hundreds of thousands, plus curated whole-name lists, so the same name practically never comes back.
  • Never offer the same name twice in a campaign. Remember (cheaply: hashes in the DB or Redis, no tokens) every name shown in a campaign, and skip it and anything already a wiki entry title or alias there. This is the "disallow list", free.
  • Variety within a set: no two options in one set share a first letter, ending or length band where avoidable.
  • Styles for people: several human flavours, plus elf, dwarf, halfling, gnome, orc, goblin and more. Offered by game system where it fits (PF2e ancestries, 5e species), and all styles are always available.
  • Other kinds, by pattern: settlements, taverns and inns, organisations, geography, countries, ships, items…, mapped to the wiki's entry types.
  • A filter: never a real English word on its own where a name is wanted, and never anything offensive or slur-like, including across syllable joins.
  • Our own lists. fantasynamegenerators.com's lists are its author's copyrighted work and its terms forbid reuse. The technique (pieces plus rules) is free; every list is written for Quest Board.
  • Description, hybrid: the existing per-name "describe" action asks the AI for a description of a chosen name, only when an AI is configured. Without one, names alone (later, maybe, a description built from tables).
  • Deterministic tests: seeded generation, no duplicates in a set, the filter, and the campaign memory.

Plan:

  1. Draft two or three styles as samples for the owner to judge by ear, before the rest are written.
  2. Draw the drawer change (a style choice) before building.
  3. Engine, campaign memory, API and drawer; then the remaining lists, each style reviewed by sample.

The prefetch pool for names can go once names stop needing the LLM.

**Owner's decision, 2026-10-28:** build a list-based name generator, in the style of fantasynamegenerators.com, into Prep → Names. Hybrid: names always come from the generator, and an AI (when configured) only writes a description of a name the GM picks. For v4.7.0. **Why:** 1. **Repetition.** AI models surface the same names over and over; the owner has been offered the same names many times. A disallow list sent to the AI would only add token cost. 2. **Cost.** No tokens per draw, which matters for the hosted service (AI priced by usage, #642). 3. **It works with no AI at all.** Today Prep → Names fails when no LLM is configured. **Today:** `generation_service` tool `names` → `audio_service.generate_name_options()` (LLM, JSON schema, names plus a 1–2 sentence description per kind), pre-fetched into a Redis pool by `planning_tasks.prefetch_name_options`. The UI is `pages/prep/tools/Names.jsx`, with kinds from `ENTRY_TYPE_LABELS` and an optional "feel". Instant NPC (`instant_npc`) is separate and out of scope here. **Requirements:** - **Extensive lists.** Variety is the point. Each person style needs enough pieces that the combinations run to hundreds of thousands, plus curated whole-name lists, so the same name practically never comes back. - **Never offer the same name twice in a campaign.** Remember (cheaply: hashes in the DB or Redis, no tokens) every name shown in a campaign, and skip it and anything already a wiki entry title or alias there. This is the "disallow list", free. - **Variety within a set:** no two options in one set share a first letter, ending or length band where avoidable. - **Styles for people:** several human flavours, plus elf, dwarf, halfling, gnome, orc, goblin and more. Offered by game system where it fits (PF2e ancestries, 5e species), and all styles are always available. - **Other kinds, by pattern:** settlements, taverns and inns, organisations, geography, countries, ships, items…, mapped to the wiki's entry types. - **A filter:** never a real English word on its own where a name is wanted, and never anything offensive or slur-like, including across syllable joins. - **Our own lists.** fantasynamegenerators.com's lists are its author's copyrighted work and its terms forbid reuse. The technique (pieces plus rules) is free; every list is written for Quest Board. - **Description, hybrid:** the existing per-name "describe" action asks the AI for a description of a chosen name, only when an AI is configured. Without one, names alone (later, maybe, a description built from tables). - **Deterministic tests:** seeded generation, no duplicates in a set, the filter, and the campaign memory. **Plan:** 1. Draft two or three styles as samples for the owner to judge by ear, before the rest are written. 2. Draw the drawer change (a style choice) before building. 3. Engine, campaign memory, API and drawer; then the remaining lists, each style reviewed by sample. The prefetch pool for names can go once names stop needing the LLM.
claude-bot commented 2026-10-28 05:02:46 +00:00
Author
Collaborator
Copy link

Plan step 1: a sampler for the owner to judge by ear. Name Sampler artifact: https://claude.ai/artifact/QTWCeFLowhFfgxwPCFGuKh (private to the owner). It's a JS prototype of the engine with five styles, all lists original:

Style Possible names (pieces multiplied out)
Human: Hearthland (two old name elements, plus a place or trade surname) about 3.4 million
Elvish (invented syllables, plus a house name or "of the …" epithet) about 39 million
Dwarvish (hard syllables, plus a two-word forge clan name) about 46 million
Settlements (first part plus ending; "Upper …", "…-on-river") about 230,000
Taverns & inns (signboard patterns) about 29,000

In the sampler:

  • No repeats within a visit, and variety within a set (a new first letter and a new ending where possible).
  • Filters: a famous-name block (Tolkien and other well-known fantasy characters), and a rude-word filter checked per word. The short words match only as whole words or word starts, so Spicer, Sedgelow and Nightingale pass, and "Arse…" doesn't.
  • The owner marks 👍/👎 per name and leaves notes per style. Collections: votes (doc <style>~<slug>) and notes/<style>.

Next: read the marks and notes, tune these lists, then draw the drawer and build the real engine (Python, seeded, plus the campaign memory).

Plan step 1: a sampler for the owner to judge by ear. Name Sampler artifact: https://claude.ai/artifact/QTWCeFLowhFfgxwPCFGuKh (private to the owner). It's a JS prototype of the engine with five styles, all lists original: | Style | Possible names (pieces multiplied out) | |---|---| | Human: Hearthland (two old name elements, plus a place or trade surname) | about 3.4 million | | Elvish (invented syllables, plus a house name or "of the …" epithet) | about 39 million | | Dwarvish (hard syllables, plus a two-word forge clan name) | about 46 million | | Settlements (first part plus ending; "Upper …", "…-on-river") | about 230,000 | | Taverns & inns (signboard patterns) | about 29,000 | In the sampler: - **No repeats** within a visit, and variety within a set (a new first letter and a new ending where possible). - **Filters:** a famous-name block (Tolkien and other well-known fantasy characters), and a rude-word filter checked per word. The short words match only as whole words or word starts, so Spicer, Sedgelow and Nightingale pass, and "Arse…" doesn't. - The owner marks 👍/👎 per name and leaves notes per style. Collections: `votes` (doc `<style>~<slug>`) and `notes/<style>`. Next: read the marks and notes, tune these lists, then draw the drawer and build the real engine (Python, seeded, plus the campaign memory).
claude-bot commented 2026-10-28 16:47:32 +00:00
Author
Collaborator
Copy link

Owner's criterion (2026-10-28): a name must flow off the tongue. Their one 👎 so far, "Godgyth Linshaw", was "very awkward to say", not a problem with any single piece. So the real engine needs flow rules applied at every join, beyond curating lists. A draw that breaks one is thrown away and redrawn:

  • Consonant clusters across a join: reject hard clusters formed where two pieces meet (e.g. d|g, th|g, t|ch, k|g, three or more consonants running across a join), using an allow-list of easy joins (l|w, n|d, r|th…).
  • Repetition: no echo of the same consonant or syllable on either side of a join or across the space (-gyth Lin- is fine; -wyn Wyn- is not).
  • Length: a cap on syllables per given name and for the full name; a long family name pairs with a short given name and vice versa.
  • Stress and rhythm: prefer alternating stressed and unstressed syllables in the human styles; avoid two heavy closed syllables in a row (God|gyth).

The same criterion should be stated to testers: "👍 if it fits the style and is easy to say". This is a candidate change to step 3 on the Names page, pending the owner.

**Owner's criterion (2026-10-28): a name must flow off the tongue.** Their one 👎 so far, "Godgyth Linshaw", was "very awkward to say", not a problem with any single piece. So the real engine needs **flow rules applied at every join**, beyond curating lists. A draw that breaks one is thrown away and redrawn: - **Consonant clusters across a join:** reject hard clusters formed where two pieces meet (e.g. `d|g`, `th|g`, `t|ch`, `k|g`, three or more consonants running across a join), using an allow-list of easy joins (`l|w`, `n|d`, `r|th`…). - **Repetition:** no echo of the same consonant or syllable on either side of a join or across the space (`-gyth Lin-` is fine; `-wyn Wyn-` is not). - **Length:** a cap on syllables per given name and for the full name; a long family name pairs with a short given name and vice versa. - **Stress and rhythm:** prefer alternating stressed and unstressed syllables in the human styles; avoid two heavy closed syllables in a row (`God|gyth`). The same criterion should be stated to testers: "👍 if it fits the style and is easy to say". This is a candidate change to step 3 on the Names page, pending the owner.
claude-bot commented 2026-11-02 16:36:53 +00:00
Author
Collaborator
Copy link

At the owner's request (2 Nov), the scoring page now offers ten more kinds, 15 in all:

  • People: Sunreach and Northmarch humans, halfling, gnome, orc and goblin.
  • Places: landscape, and countries & realms.
  • Other: organisations and ships.

Every person style also has a flow check at its joins, following the owner's note on "Godgyth". It's live at the same link, with the PR in #1314. The marks feed the lists the real generator will use.

At the owner's request (2 Nov), the scoring page now offers ten more kinds, 15 in all: - **People:** Sunreach and Northmarch humans, halfling, gnome, orc and goblin. - **Places:** landscape, and countries & realms. - **Other:** organisations and ships. Every person style also has a flow check at its joins, following the owner's note on "Godgyth". It's live at the same link, with the PR in #1314. The marks feed the lists the real generator will use.
claude-bot commented 2026-11-03 16:00:47 +00:00
Author
Collaborator
Copy link

The owner's notes after a first pass through every section of the names page (2026-11-03), and what changes on the feedback site:

  • Organisations leaned towards orders and secret societies, with few guilds and almost no companies. It's split into three:
    • Guilds
    • Companies, expected to be the most used, so it gets the most patterns: family firms, trading and shipping houses, workshops and shops, inns' and mills' owners, banks and chartered companies
    • Orders & secret societies
  • Taverns & inns produced mostly taverns. It's split into Taverns (signboard names) and Inns & lodgings (a rest, a lodge, a waystation, a coaching inn).
  • Ships split by class: Small boats (fishing, river and ferry boats), Merchant ships and Warships.
  • Landscape split by kind: Forests & woods, Mountains & hills, Caves & the deep, Rivers, lakes & falls, Coasts & seas, and Marshes, moors & plains. The owner gave the split as an example only.
  • Settlements split by size: Hamlets & villages, Towns and Cities. The difference is real but modest:
    • villages get plain two-part names, often after the land (Ashford, Nettlecombe);
    • towns add the market, the bridge or the river (Market Harrow, Wexford-on-Esk);
    • cities get shorter, older or grander names (Port Calder, Kingsreach) and are drawn more often from older roots.

Votes already cast stay valid. The old ids (org, inn, ship, geo, town) remain accepted on the server, so no rater's saved document is refused. The page no longer offers them, and the admin readout lists them as retired with their counts.

The flow rules at piece joins apply to every new style. A "whole company" generator (size, trade, owner and staff, all offline) is a later enhancement, filed separately.

**The owner's notes after a first pass through every section of the names page (2026-11-03), and what changes on the feedback site:** - **Organisations** leaned towards orders and secret societies, with few guilds and almost no companies. It's split into three: - **Guilds** - **Companies**, expected to be the most used, so it gets the most patterns: family firms, trading and shipping houses, workshops and shops, inns' and mills' owners, banks and chartered companies - **Orders & secret societies** - **Taverns & inns** produced mostly taverns. It's split into **Taverns** (signboard names) and **Inns & lodgings** (a rest, a lodge, a waystation, a coaching inn). - **Ships** split by class: **Small boats** (fishing, river and ferry boats), **Merchant ships** and **Warships**. - **Landscape** split by kind: **Forests & woods**, **Mountains & hills**, **Caves & the deep**, **Rivers, lakes & falls**, **Coasts & seas**, and **Marshes, moors & plains**. The owner gave the split as an example only. - **Settlements** split by size: **Hamlets & villages**, **Towns** and **Cities**. The difference is real but modest: - villages get plain two-part names, often after the land (Ashford, Nettlecombe); - towns add the market, the bridge or the river (Market Harrow, Wexford-on-Esk); - cities get shorter, older or grander names (Port Calder, Kingsreach) and are drawn more often from older roots. **Votes already cast stay valid.** The old ids (`org`, `inn`, `ship`, `geo`, `town`) remain accepted on the server, so no rater's saved document is refused. The page no longer offers them, and the admin readout lists them as retired with their counts. The flow rules at piece joins apply to every new style. A **"whole company"** generator (size, trade, owner and staff, all offline) is a later enhancement, filed separately.
claude-bot commented 2026-11-03 16:06:33 +00:00
Author
Collaborator
Copy link

The owner's answer to Q219 (2026-11-03): all of them. These kinds join the names page in the same change as the splits, for rating:

  • Ancestries: Kobold, Leshy, Catfolk, Ratfolk, Kitsune and Tengu (PF2e), and Dragonborn and Tiefling (5e)
  • Noble houses (with seat and motto)
  • Deities & saints
  • Streets, districts & landmarks
  • Temples & shrines
  • Books, scrolls & documents
  • Magic items & named weapons
  • Horses & animals
  • Battles & historical events
  • Festivals & holidays
**The owner's answer to Q219 (2026-11-03): all of them.** These kinds join the names page in the same change as the splits, for rating: - Ancestries: Kobold, Leshy, Catfolk, Ratfolk, Kitsune and Tengu (PF2e), and Dragonborn and Tiefling (5e) - Noble houses (with seat and motto) - Deities & saints - Streets, districts & landmarks - Temples & shrines - Books, scrolls & documents - Magic items & named weapons - Horses & animals - Battles & historical events - Festivals & holidays
claude-bot commented 2026-11-03 19:30:55 +00:00
Author
Collaborator
Copy link

The ratings so far (read-only tally of the feedback data, 2026-11-03; two raters):

  • Well approved (12–60 votes each, almost all up): every people style, caves, mountains, marshes and moors, streets, temples, villages, towns, cities, inns, and the retired organisations, ships, settlements and landscapes.
  • Down-votes with a clear cause:
    • Forests (18 up, 27 down): old English woodland words (Chase, Hanger, Holt, Brake, Weald, Thicket, Copse, Wilds) and plain tree names (Yew Copse, Elm Grove).
    • Rivers & lakes (26 up, 10 down): the northern waterfall words Force, Foss, Leap and Spout, and "The Heron Lake".
    • Coasts: too many "The …" names, and Ness.
    • Realms: too many "The …" names. Reach and Marches don't fit a country, and no realm calls itself "Old", though "New" is fine.
    • Landscape (owner's note): fewer "The ".
    • Human (Hearthland): heavy Old English parts (Cyn-, Leod-, -swith, Bald-, Mild-).
    • Elvish: drop the "of the …" titles, which the owner noted are the only title instead of a family name, and the vowel pile-ups (Caeraor, Ulanenae).
    • Taverns: "Snug". Mountains: "Heights" on a place name.
  • Not yet rated: most of the 18 newest kinds.

Next:

  1. Apply those fixes on the feedback site for the owner to confirm by ear.
  2. Draw the Prep → Names drawer with its style choice (the original plan's step 2).
  3. Build: the engine in the backend, ported from the names page, with campaign memory, the filters, seeded tests, and AI only for "describe".

Q228 asks whether the unrated kinds go into the first build.

**The ratings so far (read-only tally of the feedback data, 2026-11-03; two raters):** - **Well approved** (12–60 votes each, almost all up): every people style, caves, mountains, marshes and moors, streets, temples, villages, towns, cities, inns, and the retired organisations, ships, settlements and landscapes. - **Down-votes with a clear cause:** - **Forests** (18 up, 27 down): old English woodland words (Chase, Hanger, Holt, Brake, Weald, Thicket, Copse, Wilds) and plain tree names (Yew Copse, Elm Grove). - **Rivers & lakes** (26 up, 10 down): the northern waterfall words Force, Foss, Leap and Spout, and "The Heron Lake". - **Coasts:** too many "The …" names, and Ness. - **Realms:** too many "The …" names. Reach and Marches don't fit a country, and no realm calls itself "Old", though "New" is fine. - **Landscape** (owner's note): fewer "The <adj> <noun>". - **Human (Hearthland):** heavy Old English parts (Cyn-, Leod-, -swith, Bald-, Mild-). - **Elvish:** drop the "of the …" titles, which the owner noted are the only title instead of a family name, and the vowel pile-ups (Caeraor, Ulanenae). - **Taverns:** "Snug". **Mountains:** "Heights" on a place name. - **Not yet rated:** most of the 18 newest kinds. **Next:** 1. Apply those fixes on the feedback site for the owner to confirm by ear. 2. Draw the Prep → Names drawer with its style choice (the original plan's step 2). 3. Build: the engine in the backend, ported from the names page, with campaign memory, the filters, seeded tests, and AI only for "describe". Q228 asks whether the unrated kinds go into the first build.
claude-bot commented 2026-11-03 19:34:26 +00:00
Author
Collaborator
Copy link

The owner's answer to Q228 (2026-11-03): (a). Every kind goes in the first build, including the ones not yet rated. Ratings keep tuning them afterwards as list edits.

Engine requirement from the owner's follow-up: company, guild, church and noble names often include their town or region. Build every pattern with a place slot (a guild's town, a house's seat, a company's region, a temple's parish) so the slot can be filled from outside with a real place in the campaign, falling back to a generated name. Using it ("for: Kettlebridge" in the drawer; "roll up Kettlebridge" in #1328) is a later enhancement, but the slot is in the engine from the start, so it needs no rewrite.

**The owner's answer to Q228 (2026-11-03): (a).** Every kind goes in the first build, including the ones not yet rated. Ratings keep tuning them afterwards as list edits. **Engine requirement from the owner's follow-up:** company, guild, church and noble names often include their town or region. Build every pattern with a place slot (a guild's town, a house's seat, a company's region, a temple's parish) so the slot can be **filled from outside** with a real place in the campaign, falling back to a generated name. Using it ("for: Kettlebridge" in the drawer; "roll up Kettlebridge" in #1328) is a later enhancement, but the slot is in the engine from the start, so it needs no rewrite.
claude-bot commented 2026-11-03 21:33:57 +00:00
Author
Collaborator
Copy link

The owner's answers to Q229–Q231 (2026-11-03), recorded as D331 (D327–D330 cover #1328 and Q228; commit 7abcca14):

  • Q229: the style order as drawn: the campaign's own system's peoples first, places smallest to largest.
  • Q230: the "feel" box is gone; the style does that job.
  • Q231: ten names a set.

Building now on feat/1257-names-in-prep, with the server and the drawer built in parallel from one spec.

  • The engine: a faithful Python port of the 44 rated styles from the names page, with its filters and flow rules and the place slot in every pattern that names a place.
  • Campaign memory: a name is never offered twice, and never one that's already a page's title or alias.
  • Runs: sets are still names runs, so Insert, the shelf and History keep working.
  • AI: used only for Describe, when one is configured.
  • Removed: the names prefetch pool.
**The owner's answers to Q229–Q231 (2026-11-03), recorded as D331** (D327–D330 cover #1328 and Q228; commit 7abcca14): - **Q229:** the style order as drawn: the campaign's own system's peoples first, places smallest to largest. - **Q230:** the "feel" box is gone; the style does that job. - **Q231:** ten names a set. **Building now** on `feat/1257-names-in-prep`, with the server and the drawer built in parallel from one spec. - **The engine:** a faithful Python port of the 44 rated styles from the names page, with its filters and flow rules and the place slot in every pattern that names a place. - **Campaign memory:** a name is never offered twice, and never one that's already a page's title or alias. - **Runs:** sets are still `names` runs, so Insert, the shelf and History keep working. - **AI:** used only for Describe, when one is configured. - **Removed:** the names prefetch pool.
rbrooks referenced this issue from a commit 2026-11-03 22:00:21 +00:00
wip: names tests (#1257)
claude-bot commented 2026-11-04 00:48:49 +00:00
Author
Collaborator
Copy link

Done: merged in #1331 (D330, D331; lane 6l).

  • Prep → Names: the drawer draws from Quest Board's own lists, all 44 rated styles, ported by script from the names page. Ten names a set, by Kind and a Style that follows it. Save to the wiki; Describe only with an AI (409 without); Another set.
  • Never twice: names are never offered twice in a campaign (name_offers), and never one that's an existing page title or alias.
  • No AI for names: sets are still names runs, so Insert, the shelf and History work. The prefetch pool is gone.
  • The place slot is in every pattern that names a place, ready for "names that use their place" (#1328).
  • Checks:
    • The render check was clean: 57 shots, axe clean, 460 names with no repeats.
    • The owner approved the wording (part v).
    • The full backend suite passed on the dev host (10,721), and then CI passed.
    • CI found two guard collisions (.title, .body) and one slow-runner test race, all fixed.

Follow-ups, not filed yet:

  • Remove the now-unused AI name code in audio_service.
  • Keep only names runs that are inserted, shelved or saved, so History doesn't fill up with every draw.

Ratings on the feedback site keep tuning the lists.

**Done:** merged in #1331 (D330, D331; lane 6l). - **Prep → Names:** the drawer draws from Quest Board's own lists, all 44 rated styles, ported by script from the names page. Ten names a set, by Kind and a Style that follows it. Save to the wiki; Describe only with an AI (409 without); Another set. - **Never twice:** names are never offered twice in a campaign (`name_offers`), and never one that's an existing page title or alias. - **No AI for names:** sets are still `names` runs, so Insert, the shelf and History work. The prefetch pool is gone. - **The place slot** is in every pattern that names a place, ready for "names that use their place" (#1328). - **Checks:** - The render check was clean: 57 shots, axe clean, 460 names with no repeats. - The owner approved the wording (part v). - The full backend suite passed on the dev host (10,721), and then CI passed. - CI found two guard collisions (`.title`, `.body`) and one slow-runner test race, all fixed. **Follow-ups, not filed yet:** - Remove the now-unused AI name code in `audio_service`. - Keep only names runs that are inserted, shelved or saved, so History doesn't fill up with every draw. Ratings on the feedback site keep tuning the lists.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/1328-fill-it-in
feat/1328-fill-frontend
feat/1328-fill-backend
feat/9-foundry-push
fix/9-foundry-live
feat/9-foundry-push-frontend
renovate/celery-5.x
feat/5-foundry-connect
feat/9-foundry-push-backend
feat/9-foundry-push-module
feat/5-foundry-frontend
feat/5-foundry-backend
feat/5-foundry-module
release/v4.8.0-rc1
docs/d341-convert-draft
feat/958-update-to-version
feat/958-convert-sheet
feat/958-pathbuilder-import-frontend
fix/1360-heading-order
feat/958-pathbuilder-import-backend
feat/11-weekly-digest
feat/1341-auto-update
docs/d332-superseded
chore/1345-names-cleanup
feat/1342-mentioned-pages
feat/1328-recipes
fix/1346-pgdg-key
perf/1247-shared-recording-stream
chore/132-gitleaks-allowlist
release/v4.7.1
spike/foundry-module
release/v4.7.1-rc1
docs/decisions-d332-d337
fix/bot-certifi
chore/release-4.7.0
chore/release-4.7.0-rc4
chore/deps-4.7.0
chore/release-4.7.0-rc3
fix/1280-quote-must-say-it
fix/1257-names-row-squeeze
chore/release-4.7.0-rc2
fix/1245-pg-upgrade-count
chore/release-4.7.0-rc1
feat/1257-names-in-prep
feat/1257-be
feat/1257-fe
feat/1257-rating-fixes
design/1328-fill-it-in
feat/1257-name-splits
fix/1326-redis-503
feat/1280-fact-suggestions
feat/1280-be
feat/1280-fe
design/1280-fact-suggestions
feat/1279-infobox
feat/1279-be
feat/1279-fe
feat/1321-shelf-copies
design/1279-infobox
feat/1243-table-find
feat/1257-who-rated
feat/1243-prep-drawer
feat/1243-sheet-pickers
design/1243-browse-in-place
feat/1315-hotwords-default
feat/1242-system-filters
feat/1257-more-name-styles
feat/506-leg3-hotwords
design/1242-system-filters
fix/1302-packs-polish
feat/1241-rules-library
design/1241-rules-library
feat/1245-postgres-18
integ/4.6.2
fix/1263-map-ui-2
fix/1263-map-server
fix/1263-map-ui-1
fix/1261-editor-link-menu
fix/1229-axe-4.14-name-mismatch
renovate/axllent-mailpit-1.x
renovate/eslint-monorepo
renovate/authlib-1.x
chore/release-4.6.0
chore/release-4.6.0-rc2
fix/460-rc2-screens
fix/460-rc2-server
fix/release-prerelease-exit
chore/release-4.6.0-rc1
feat/125-campaign-templates
feat/126-calendar
feat/1181-pictures-and-files
feat/1190-event-people
integ/4.6.0
feat/1191-line-of-the-night
feat/1200-starter-packs
chore/bot-multidict-and-playwright-group
fix/1202-this-week-answered-count
fix/122-124-leftovers
fix/1178-get-routes-that-write
fix/1203-journeys-check-names
design/125-campaign-templates
feat/126-calendar-engine
design/126-in-world-calendar
fix/1189-cited-stamp-in-range
fix/1189-v4-looser-check
fix/1189-richer-beats
fix/1113-export-bind-lists
fix/1154-release-notes-by-file
chore/release-4.5.0
chore/release-4.5.0-rc12
fix/1135-wiki-markup-as-text
fix/demo-usage-cost-in-window
chore/release-4.5.0-rc11
fix/1121-sheet-consistency
fix/1121-sheet-5e-terms-and-card-hp
copy/1122-busiest-pages
fix/1121-relevant-choices
fix/1121-wiki-create-npc-save-sheet-links
fix/1029-menu-stays-on-screen
docs/prototype-transcript-bin-wording
fix/1023-editor-save-row-back-scroll
fix/1020-search-exact-first
fix/1020-table-prep
fix/1020-shell-wordmark-footer-bell
fix/1020-wiki-article-party
fix/872-admin-kept-until-phone-tables
feat/l13-milestone-level-waiting
fix/1000-1001-bell-older-setup-context
fix/999-pronouns-in-prompts
fix/l19-other-class-feats
fix/1010-transcript-window-ordinary-confirm
docs/d254-d269-decisions
fix/702-member-search
fix/680-transcript-bin
fix/993-unidentified-prompts
fix/841-redis-timeouts
fix/990-binned-not-exported
fix/830-export-prep-shelf
fix/deps-audit-2026-10-01
fix/877-title-reads
fix/798-audio-received-at
build/lane11-17-j7
build/lane11-16-levelup
build/lane11-14-seams
build/lane11-14-seed
build/lane11-15-start
build/lane11-13-old-block-out
fix/980-review-r3
build/lane11-12-block
build/lane11-8-packs
fix/demo-seed-canonical-names
build/lane11-11-hot-half
docs/l11-decisions
build/lane11-7-convert
build/lane11-10-editing
fix/npm-audit-brace-expansion
build/lane11-9-sheet-page
fix/bot-pyjwt
build/lane11-6-content
fix/lane11-rank-names
build/lane11-2b-language
build/lane11-4-js-evaluator
build/lane11-3-server
build/lane11-5a-pf2e
build/lane11-5b-5e
feat/design-admin
build/lane11-2-evaluator
build/lane11-1-sheet-pieces
build/lane11-0-drawing
fix/943-quest-objectives-fk
fix/prepsheet-shelf-flake
fix/945-leftovers
build/demo-gm-copy
fix/901-email-landings
build/lane10-8-journeys
build/demo-seed-lanes-8-10
fix/887-gm-own-confirmation
build/lane9-5-j1-admin
fix/918-audience-click
fix/useasync-overtaken
ci/939-critical-path
test/937-backend-suite-speed
chore/claude-orchestration
fix/924-xp-gm-only
fix/session-stale-poll
docs/decisions-d239-d242
fix/930-pypdf
build/lane8-journeys
build/925-quest-editor
fix/894-private-page-pictures
build/lane8-p4-drafts
build/lane8-p7-map
build/lane8-p6-handouts-rules
fix/wiki-fixture-names
build/lane10-d227-test-usage
fix/rsvp-horizon-test-tuesday
fix/media-volume-owner
build/lane8-p3-editor
fix/912-unidentified-rename
build/lane8-p5-party-quests
build/lane8-handout-takeback
build/lane10-pickers
build/lane8-p2-article
build/lane8-6-map
build/lane10-7b-email-pages
build/lane8-5-handouts
build/lane10-7a-test-the-bot-pages
build/lane8-p1-pages
build/lane8-4-quests
build/lane8-2b-feeds
build/lane8-3-parties
build/lane8-2a-links
build/lane10-5-commands
build/lane9-6-seed
build/lane10-4b-reactions
build/lane9-4d-pages
build/lane9-4c-pages
build/lane10-4a-posts
build/lane10-3-email
fix/891-web-fonts
build/lane9-4b-pages
build/lane10-6-test-the-bot
build/lane10-2-notify-out
build/lane8-1-wiki-text
build/lane9-4a-frame
design/lane10-drawings
fix/j6-budget
fix/j5-phone-flake
fix/869-test-leaks
fix/843-record-start-followups
build/lane7-all
build/lane6-all
build/lane9-b2-server
chore/changelog-fragments
docs/decisions-d218
build/lane9-a-owner-overview
fix/rule-card-level-label
fix/834-retention-semantics
fix/o3c-record-without-announcement
docs/decisions-d179
docs/decisions-d131-d170
fix/851-commit-before-response
build/lane6-j3-seed
build/lane9-b1-d67-identity
fix/841-blocking-loop
build/lane9-c-backups-audit
fix/vote-race-and-start-commit
fix/recording-announcement
fix/proposal-read-leak
fix/last-admin-guard
build/lane6-p4c-planning
build/lane6-p4b-margin
build/lane6-p4a-sheet
build/lane5-j4-seed
build/lane6-base
build/lane7-pages-talk
build/lane5-pages
build/lane7-pages-safety
build/lane7-p3-safety
build/lane7-p2-notify
build/lane6-p3-planning
build/lane6-p2-history
build/lane6-p1b-items
build/lane7-p1-threads
build/lane5-p6-faces
build/lane6-p1a-sheet
build/lane5-p5-find
build/lane5-p4a-board
build/lane5-p4b-scenes
build/lane5-p3-live
build/lane5-base
build/lane5-p2-cards
docs/lane5-decisions
build/review-r2-wide
fix/review-r1
build/lane5-p1-scenes
build/demo-seed
build/lane4-journeys-j5
build/lane4-page-review-b
build/lane4-page-review-a
build/lane4-page-read
build/lane4-journeys
build/lane4-page-sess2
build/lane4-page-sess1
build/lane4-notes
build/lane4-discord-on-approval
build/lane4-scheduling
build/lane4-versions
build/760-session-number
build/lane4-decisions
build/797-erase-no-regenerate
build/test-race-audit
build/lane3-completions
build/794-dark-only
build/796-titles-scroll
build/791-retention-anchor
build/a11y-sweep
build/shell-followups
build/retention-preview
build/753-backup-readback
docs/d91-d93
build/lane3-j1
build/ci-harness-paths-selftest
fix/useauth-test-race
build/ci-harness-paths
build/777-ai-settings-read
build/lane3-settings-c
build/lane3-settings-b
build/lane3-j6
build/lane3-sessionform
build/lane3-settings-a
build/lane3-members
build/lane3-thisweek
build/lane3-story
chore/87-align-python-3.12
v4.8.0-rc1
v4.7.1
v4.7.1-rc1
v4.7.0
v4.7.0-rc4
v4.7.0-rc3
v4.7.0-rc2
v4.7.0-rc1
v4.6.2
v4.6.2-rc4
v4.6.2-rc3
v4.6.2-rc2
v4.6.2-rc1
v4.6.1
v4.6.1-rc1
v4.6.0
v4.6.0-rc2
v4.6.0-rc1
v4.5.3
v4.5.3-rc1
v4.5.2
v4.5.2-rc1
v4.5.1
v4.5.1-rc2
v4.5.1-rc1
v4.5.0
v4.5.0-rc12
v4.5.0-rc11
v4.5.0-rc10
v4.5.0-rc9
v4.5.0-rc8
v4.5.0-rc7
v4.5.0-rc6
v4.5.0-rc5
v4.5.0-rc4
v4.5.0-rc3
v4.5.0-rc2
v4.5.0-rc1
v4.4.1
v4.4.0
v4.3.0
v4.2.3
v4.2.2
v4.2.1
v4.2.0
v4.1.2
v4.1.1
v4.1.0
v4.0.1
v4.0.0
v3.11.4
v3.11.3
v3.11.2
v3.11.1
v3.11.0
v3.10.0
v3.9.1
v3.9.0
v3.8.0
v3.7.0
v3.6.1
v3.6.0
v3.5.0
v3.4.1
v3.4.0
v3.3.0
v3.2.0
v3.1.0
v3.0.0
v2.1.0
v2.0.0
v1.1.0
v1.0.0
v0.12.0
v0.11.0
v0.10.0
v0.9.1
v0.3.3
v0.9.0
v0.8.0
v0.3.2
v0.3.1
v0.3.0
v0.7.0
v0.6.0
v0.5.0
v0.4.0
v0.2.1
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
backend
Issue related to the backend

  
bot
Issue related to the bot

  
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
frontend
Issue related to the frontend

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
recording
Issue related to the recording system

  
security
Security hardening / vulnerability work

  
wontfix
This won't be fixed

No labels
backend
bot
bug
duplicate
enhancement
frontend
help wanted
invalid
question
recording
security
wontfix
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/Quest-Board#1257
No description provided.