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

Wiki facts suggested by the local model after a session (Status first), for GM approval #1280

New issue
Closed
opened 2026-10-29 17:32:21 +00:00 by claude-bot · 6 comments
claude-bot commented 2026-10-29 17:32:21 +00:00
Collaborator
Copy link

Split out of #1279 at the owner's request (2026-10-29), so stage 2 of the fact automation isn't forgotten. #1279 builds the infobox and the facts that need no AI (First met / Last seen, Player and pronouns, sheet fields, content-pack fields, Region from the map).

Goal: after a session is processed, suggest updates to the facts of the pages that appeared in it, as suggestions a GM approves. Start with Status (alive / dead / missing / unknown), then a short list of fields per page type that the owner chooses (e.g. Leader, Ruler, Owner, Allegiance).

Approach, sized for the self-hosted open-weights model

  • One narrow question per page that appeared (lore_session_appearances), over the transcript excerpts that mention it. The answer is constrained to a JSON schema (the endpoint honours json_schema), choosing from fixed values where the field has them.
  • Every suggested change carries a quote, checked against the transcript the way summary beats are validated. A suggestion whose quote isn't found is dropped, and the count is recorded on the run.
  • Through the existing draft review (lore_entry_drafts.current_sidebar_fields): GM-only until approved, and it never overwrites a fact the GM wrote without the GM saying so.
  • Roughly one short call per page mentioned per session, run in the worker after summarisation.

Not in scope: open-ended inference (a settlement's population, an implied motive) and synthesis across many sessions; both are unreliable on the local model.

Measure before widening: run it over the owner's real sessions and record how many suggestions were accepted, edited or rejected per field, before adding more fields.

Depends on #1279.

Split out of #1279 at the owner's request (2026-10-29), so stage 2 of the fact automation isn't forgotten. #1279 builds the infobox and the facts that need no AI (First met / Last seen, Player and pronouns, sheet fields, content-pack fields, Region from the map). **Goal:** after a session is processed, suggest updates to the facts of the pages that appeared in it, as suggestions a GM approves. Start with **Status** (alive / dead / missing / unknown), then a short list of fields per page type that the owner chooses (e.g. Leader, Ruler, Owner, Allegiance). **Approach, sized for the self-hosted open-weights model** - **One narrow question per page that appeared** (`lore_session_appearances`), over the transcript excerpts that mention it. The answer is constrained to a JSON schema (the endpoint honours `json_schema`), choosing from fixed values where the field has them. - **Every suggested change carries a quote**, checked against the transcript the way summary beats are validated. A suggestion whose quote isn't found is dropped, and the count is recorded on the run. - **Through the existing draft review** (`lore_entry_drafts.current_sidebar_fields`): GM-only until approved, and it never overwrites a fact the GM wrote without the GM saying so. - Roughly one short call per page mentioned per session, run in the worker after summarisation. **Not in scope:** open-ended inference (a settlement's population, an implied motive) and synthesis across many sessions; both are unreliable on the local model. **Measure before widening:** run it over the owner's real sessions and record how many suggestions were accepted, edited or rejected per field, before adding more fields. Depends on #1279.
claude-bot commented 2026-11-03 06:59:48 +00:00
Author
Collaborator
Copy link

Picking this up now that #1279 has merged (#1324). First a drawing (lane 6j) of where a suggested fact change appears and how a GM approves, edits or rejects it, with its quote. The questions go to the owner before anything is built.

Picking this up now that #1279 has merged (#1324). First a drawing (lane 6j) of where a suggested fact change appears and how a GM approves, edits or rejects it, with its quote. The questions go to the owner before anything is built.
claude-bot commented 2026-11-03 14:01:43 +00:00
Author
Collaborator
Copy link

The owner's answers (2026-11-03), recorded as D323–D326 (commit ae62f6fd on design/1280-fact-suggestions; the drawing is lane 6j):

  • Q214 → D323: start with five facts: Status (Alive / Dead / Missing / Unknown) on NPC, PC, Creature and Deity pages; Allegiances on NPC; Ruler on Settlement and Country; Leader on Organization; Owner on Business.
  • Q215 → D324: a used suggestion keeps the fact's own "Who sees it". A fact that was empty becomes visible to everyone at the table.
  • Q216 → D325: after the release, run once over past sessions, newest first, on prod's own worker. The number of suggestions used, changed or turned down is the measure for widening the list.
  • Q217 → D326: suggestions show in both Suggested wiki updates and the page editor.

Build: branch feat/1280-fact-suggestions, with the backend and screen built in parallel from one spec.

  • Storage: a fact_suggestions table rather than the draft review the issue first proposed. Each change needs its own Use it, Change it, Not this one and Undo, and the use, change and rejection counts are what D325 measures.
  • Quotes: every quote is checked against the transcript segments. The speaker and the time come from the matching segment, never from the model.
**The owner's answers (2026-11-03), recorded as D323–D326** (commit ae62f6fd on `design/1280-fact-suggestions`; the drawing is lane 6j): - **Q214 → D323:** start with five facts: Status (Alive / Dead / Missing / Unknown) on NPC, PC, Creature and Deity pages; Allegiances on NPC; Ruler on Settlement and Country; Leader on Organization; Owner on Business. - **Q215 → D324:** a used suggestion keeps the fact's own "Who sees it". A fact that was empty becomes visible to everyone at the table. - **Q216 → D325:** after the release, run once over past sessions, newest first, on prod's own worker. The number of suggestions used, changed or turned down is the measure for widening the list. - **Q217 → D326:** suggestions show in both Suggested wiki updates and the page editor. **Build:** branch `feat/1280-fact-suggestions`, with the backend and screen built in parallel from one spec. - **Storage:** a `fact_suggestions` table rather than the draft review the issue first proposed. Each change needs its own Use it, Change it, Not this one and Undo, and the use, change and rejection counts are what D325 measures. - **Quotes:** every quote is checked against the transcript segments. The speaker and the time come from the matching segment, never from the model.
claude-bot commented 2026-11-03 16:28:04 +00:00
Author
Collaborator
Copy link

Done: merged in #1325 (D323–D326, lane 6j).

  • The suggestion task: after summarisation, the worker asks the campaign's LLM one schema-constrained question per appearing page about Status, Allegiances, Ruler, Leader or Owner. It covers only the lines that mention the page.
    • Every change must quote the transcript. The speaker and the time come from the matched line, never from the model.
    • Dropped and same-value changes are counted on the run.
  • Using a suggestion: suggestions are GMs-only until used, in Suggested wiki updates (Use it / Change it… / Not this one / Undo) and in the page editor. A used fact keeps its own audience, and a new one is for everyone at the table. History records it.
  • Privacy: quotes follow the transcript.
    • Retention destroys them.
    • The bin hides them.
    • A member's erasure removes the suggestions quoting their lines (matched by line).
    • A reprocess forgets the old ones before renumbering the lines.
    • The backfill never reads a binned transcript.
    • Each of these is tested. The security review found three, and CI's transcript-bin guard found one more.
  • Checks: the render check was clean (44 shots, axe clean, players get 403). Owner wording part t is approved, and CI passed.

After the 4.7.0 deploy, on the owner's say (D325), run once:

celery -A app.tasks.celery_app call app.tasks.fact_tasks.suggest_fact_changes_backfill

Then measure used, changed and rejected per fact before widening the list.

**Done:** merged in #1325 (D323–D326, lane 6j). - **The suggestion task:** after summarisation, the worker asks the campaign's LLM one schema-constrained question per appearing page about Status, Allegiances, Ruler, Leader or Owner. It covers only the lines that mention the page. - Every change must quote the transcript. The speaker and the time come from the matched line, never from the model. - Dropped and same-value changes are counted on the run. - **Using a suggestion:** suggestions are GMs-only until used, in Suggested wiki updates (Use it / Change it… / Not this one / Undo) and in the page editor. A used fact keeps its own audience, and a new one is for everyone at the table. History records it. - **Privacy:** quotes follow the transcript. - Retention destroys them. - The bin hides them. - A member's erasure removes the suggestions quoting their lines (matched by line). - A reprocess forgets the old ones before renumbering the lines. - The backfill never reads a binned transcript. - Each of these is tested. The security review found three, and CI's transcript-bin guard found one more. - **Checks:** the render check was clean (44 shots, axe clean, players get 403). Owner wording part t is approved, and CI passed. **After the 4.7.0 deploy, on the owner's say** (D325), run once: ``` celery -A app.tasks.celery_app call app.tasks.fact_tasks.suggest_fact_changes_backfill ``` Then measure used, changed and rejected per fact before widening the list.
claude-bot commented 2026-11-04 21:45:35 +00:00
Author
Collaborator
Copy link

Dev rehearsal of the past-sessions pass (4.7.0-rc2, 2026-11-04, owner's go-ahead).

  • The run: suggest_fact_changes_backfill on dev took 129 s: 44 sessions, all done, 0 skipped, 0 failed.
  • The counts: 176 pages asked; 8 suggested; 0 dropped for a missing quote; 0 the same as the stored value; 0 failed calls.
  • The suggestions: all from The Amberwake Accord and its GM copy, so 4 distinct: Leader ×2, Ruler, Owner. None was a Status change.
  • Quality: every quote was in the transcript, but three of the four didn't say the change, only mentioned the person near the page. Only "Orla Brennock is behind it" (Owner) supports its suggestion.

Improved in #1336 before prod's run: the prompt asks for the line that states the change, and a code check requires the quote to name the new value and hold a word for the fact. Unsupported suggestions are dropped and counted (dropped_unsupported). With that check, the dev set would keep 1 of the 4.

To compare on dev: an rc with #1336, then clear dev's 8 rc2 suggestions and their run counts, and rerun the pass.

**Dev rehearsal of the past-sessions pass (4.7.0-rc2, 2026-11-04, owner's go-ahead).** - **The run:** `suggest_fact_changes_backfill` on dev took 129 s: 44 sessions, all done, 0 skipped, 0 failed. - **The counts:** 176 pages asked; 8 suggested; 0 dropped for a missing quote; 0 the same as the stored value; 0 failed calls. - **The suggestions:** all from The Amberwake Accord and its GM copy, so 4 distinct: Leader ×2, Ruler, Owner. None was a Status change. - **Quality:** every quote was in the transcript, but three of the four didn't say the change, only mentioned the person near the page. Only "Orla Brennock is behind it" (Owner) supports its suggestion. **Improved in #1336** before prod's run: the prompt asks for the line that states the change, and a code check requires the quote to name the new value and hold a word for the fact. Unsupported suggestions are dropped and counted (`dropped_unsupported`). With that check, the dev set would keep 1 of the 4. **To compare on dev:** an rc with #1336, then clear dev's 8 rc2 suggestions and their run counts, and rerun the pass.
claude-bot commented 2026-11-05 01:05:06 +00:00
Author
Collaborator
Copy link

Rerun on dev with 4.7.0-rc3 (#1336's quote check), 2026-11-05. I cleared rc2's 8 pending suggestions and the run counts, then ran the backfill again: 44 sessions, 176 pages asked.

  • 2 suggested, both The Drowned Lantern → Owner: Orla Brennock, quoting "Orla Brennock is behind it" (once per Amberwake campaign).
  • 4 dropped as unsupported: the three weak ones the rc2 run kept (Tamsin Reed as Ruler, Petronella Vay and Jory Callander as Leader). The model still offered them, and the code check dropped them.
  • 0 dropped for no quote, 0 the same as stored, 0 failed calls.

So the model alone still reaches for "a line that mentions the person". supports() is what keeps the queue honest, and the run's dropped_unsupported count shows how often it does so. That count is the number to watch on prod.

**Rerun on dev with 4.7.0-rc3 (#1336's quote check), 2026-11-05.** I cleared rc2's 8 pending suggestions and the run counts, then ran the backfill again: 44 sessions, 176 pages asked. - **2 suggested**, both The Drowned Lantern → Owner: Orla Brennock, quoting *"Orla Brennock is behind it"* (once per Amberwake campaign). - **4 dropped as unsupported**: the three weak ones the rc2 run kept (Tamsin Reed as Ruler, Petronella Vay and Jory Callander as Leader). The model still offered them, and the code check dropped them. - 0 dropped for no quote, 0 the same as stored, 0 failed calls. So the model alone still reaches for "a line that mentions the person". `supports()` is what keeps the queue honest, and the run's `dropped_unsupported` count shows how often it does so. That count is the number to watch on prod.
claude-bot commented 2026-11-06 00:41:14 +00:00
Author
Collaborator
Copy link

Backfill on prod (2026-11-06, on the owner's say): task c5bcbbe8: 3 sessions done, 0 skipped, 0 failed. It made no suggestions and no AI calls (pages_asked: 0 on every run).

The cause is the data, not a fault. The pass asks only about wiki pages linked to the session (lore_session_appearances). On prod, "A Merry Band of Thieves" has 63 live pages but only one appearance link in the whole campaign, and none on sessions 13, 14 or 16, which are the three sessions with transcript lines. On dev, the pages had appearance links, which is why it found candidates there.

Possible follow-up, for the owner to decide: also ask about campaign pages whose title or alias is named in the transcript, even when no appearance link exists. excerpts_for already finds mentions, so most of this is a wider candidate query plus a cap on pages per session.

**Backfill on prod (2026-11-06, on the owner's say):** task `c5bcbbe8`: 3 sessions done, 0 skipped, 0 failed. It made **no suggestions and no AI calls** (`pages_asked: 0` on every run). The cause is the data, not a fault. The pass asks only about wiki pages linked to the session (`lore_session_appearances`). On prod, "A Merry Band of Thieves" has 63 live pages but only **one** appearance link in the whole campaign, and none on sessions 13, 14 or 16, which are the three sessions with transcript lines. On dev, the pages had appearance links, which is why it found candidates there. Possible follow-up, for the owner to decide: also ask about campaign pages whose title or alias is named in the transcript, even when no appearance link exists. `excerpts_for` already finds mentions, so most of this is a wider candidate query plus a cap on pages per session.
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#1280
No description provided.