rbrooks/Quest-Board

Watch

Fork

You've already forked Quest-Board

Code Issues 58 Pull requests 7 Projects Releases 76 Packages Wiki Activity Actions

[Backend] Validate beats in code before any prose is written #333

New issue

Closed

opened 2026-08-25 20:38:52 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-08-25 20:38:52 +00:00

Collaborator

Copy link

Severity: CRITICAL. Found in the August 2026 session lifecycle review (#319). This is the issue that makes accuracy independent of model size.

Why

The two reported failure modes — scrambled chronology and misattributed actions — are both currently trusted to the model. This makes them checked.

Crucially, the check is pure code and free. It runs the same way on a 9B local model and on a frontier hosted one. Given that self-hosted is a first-class target, this is the only design whose correctness floor does not ride on model size.

Proposed fix

After the map phase, before any prose is generated:

Evidence exists — every evidence timestamp must correspond to a real transcript line.
Actor is grounded — every named actor must be the resolved speaker (per the code-side legend) of at least one cited line. For an action described by the GM rather than performed on-mic, the beat is tagged narrated and the actor must appear in the text of a cited GM line.
Time range is sane — t_start <= t_end, both inside the session, and consistent with the cited evidence.
Sort by time in code. Chronology becomes a sorted() guarantee rather than a model behaviour. This is the entire point.

Beats that fail validation are flagged, not silently dropped — surface them to the GM as "unverified" so a real event with a bad citation is recoverable rather than invisible. Silent dropping would trade one invisible failure for another.

Acceptance criteria

Validator is pure code with no model call
All four checks implemented, each independently unit-tested
Failing beats are flagged and surfaced, never silently discarded
Validated beats are ordered by sorted(), not by the model
Validation results are recorded per session so accuracy can be tracked over time
A deliberately misattributed beat and a hallucinated-citation beat are both caught in tests

**Severity: CRITICAL.** Found in the August 2026 session lifecycle review (#319). This is the issue that makes accuracy independent of model size. ## Why The two reported failure modes — scrambled chronology and misattributed actions — are both currently *trusted* to the model. This makes them *checked*. Crucially, the check is **pure code and free**. It runs the same way on a 9B local model and on a frontier hosted one. Given that self-hosted is a first-class target, this is the only design whose correctness floor does not ride on model size. ## Proposed fix After the map phase, before any prose is generated: 1. **Evidence exists** — every `evidence` timestamp must correspond to a real transcript line. 2. **Actor is grounded** — every named actor must be the resolved speaker (per the code-side legend) of at least one cited line. For an action described by the GM rather than performed on-mic, the beat is tagged `narrated` and the actor must appear *in the text* of a cited GM line. 3. **Time range is sane** — `t_start <= t_end`, both inside the session, and consistent with the cited evidence. 4. **Sort by time in code.** Chronology becomes a `sorted()` guarantee rather than a model behaviour. This is the entire point. Beats that fail validation are **flagged, not silently dropped** — surface them to the GM as "unverified" so a real event with a bad citation is recoverable rather than invisible. Silent dropping would trade one invisible failure for another. ## Acceptance criteria - [ ] Validator is pure code with no model call - [ ] All four checks implemented, each independently unit-tested - [ ] Failing beats are flagged and surfaced, never silently discarded - [ ] Validated beats are ordered by `sorted()`, not by the model - [ ] Validation results are recorded per session so accuracy can be tracked over time - [ ] A deliberately misattributed beat and a hallucinated-citation beat are both caught in tests

claude-bot added this to the v4.0.0 - Session Pipeline Accuracy milestone

2026-08-25 20:38:52 +00:00

claude-bot added the

bug

backend

labels

2026-08-25 20:38:52 +00:00

rbrooks referenced this issue from a commit

2026-08-26 01:02:23 +00:00

feat(backend): resolve speaker attribution deterministically in code (#329, #342, #344)

rbrooks referenced this issue from a commit

2026-08-26 01:30:27 +00:00

feat(backend): verify session summaries against the transcript (#332, #333, #334)

claude-bot referenced this issue

2026-08-27 21:45:04 +00:00

[Frontend] Show a GM the verified events behind a summary #424

rbrooks referenced this issue from a commit

2026-08-28 00:45:01 +00:00

feat(backend): persist the events a summary was built from (#332, #333, #329)

rbrooks referenced this issue from a commit

2026-08-28 01:38:24 +00:00

feat(backend): expose the events behind a summary over the API (#333, #424)

claude-bot referenced this issue

2026-08-28 16:37:56 +00:00

[Backend] Extend truncation rejection and token budgeting to the prose paths #338

rbrooks referenced this issue from a commit

2026-08-28 18:39:30 +00:00

fix(backend): make the beat validator actually check what it claims (#332, #333)

rbrooks referenced this issue from a commit

2026-08-28 18:57:44 +00:00

feat(backend): anchors, a rollback lever, and a name the bot could not find

claude-bot commented

2026-08-28 19:13:40 +00:00

Author

Collaborator

Copy link

Verified against acceptance criteria, and five defects fixed in 152048e. This is the issue whose stated purpose is that the accuracy floor "does not ride on model size" because the check is pure code — so a check that does not run matters more here than anywhere else in the pipeline.

Criteria

Validator is pure code with no model call — validate_beats is synchronous and makes no request.
All four checks implemented, each independently unit-tested — checks 1, 2 and 4 were genuinely done. Check 3 was not, three ways over:
- t_start <= t_end was repaired in _coerce_beat, never recorded.
- "inside the session" was unreachable dead code: _coerce_beat clamped t_start to transcript_seconds, then validate_beats tested beat.t_start > transcript_seconds. "starts after the session ends" could not be appended under any input.
- "consistent with the cited evidence" was never implemented at all.
Failing beats are flagged and surfaced, never silently discarded — plus two silent discards found and fixed, below.
Validated beats are ordered by sorted() — and the sort key is now derived from verified data rather than a field nothing checked.
Validation results recorded per session — used_beats was computed every run and never persisted, so the runs that skipped validation were the ones leaving no trace. Now every run gets a row.
A misattributed beat and a hallucinated-citation beat are both caught — already true.

The test that could not fail

test_a_beat_starting_after_the_session_ends_is_flagged asserted only result.beat.t_start <= max(index), which the clamp guarantees unconditionally. It never touched result.ok or result.problems. Its own comment hedged — "the range problem may resolve" — which reads like the author noticing and writing a weaker assertion rather than chasing it down.

Why the evidence check re-anchors instead of rejecting

My first implementation flagged a beat whose range contained none of its citations. The scrambled_chronology eval fixture immediately showed that was wrong: all five of its beats failed, so five real, correctly-attributed events dropped out of the summary. That fixture exists precisely to demonstrate this gap — its notes say so, and its expected chronology_tau: -1.0 encoded the defect.

The evidence has already been checked against the transcript; the declared range has been checked by nothing. When they disagree, the verified value wins. So the range is re-anchored onto the citations, which makes the chronology guarantee stronger than it was — the sort key now comes from transcript-verified timestamps rather than a model-supplied field.

That fixture now scores tau = +1.0 with coverage, attribution and validation all 1.0. Its expectations and notes are rewritten to record the fix rather than the gap; the five reversed timestamps still make it hand-checkable in both directions.

A hallucinated citation is never used as an anchor — that would trade a wrong time the validator reported for a wrong time it invented.

BeatValidation.repairs carries corrections, separate from problems and not affecting ok: a beat the code could fix did not fail. Persisted to session_beats.repairs and exposed through #424's API, because a silent correction is indistinguishable from a correct answer.

dedupe_beats preferred hallucinations

It kept whichever duplicate had more citations, with no reference to the verdict — and gather_validated_beats validates before merging, so both sides already carried one. A second-pass beat citing the same real line plus one invented stamp beat a clean single-citation beat. render_beats_for_compose skips failing beats, so the event then vanished from the summary having been both correctly extracted and correctly checked. Verified beats now win outright.

The loop's docstring described a filter that did not exist

"'Did this pass find anything new' has to mean anything new that survives checking" sat three lines above gained = len(merged) - len(validations), which counted flagged beats. A pass of fresh hallucinations looked like progress and ran to the cap — a full re-extraction over every window, paid for nothing.

test_a_pass_of_pure_hallucination_does_not_keep_the_loop_running passed for the wrong reason: its invented beat was identical every pass, so dedupe_beats collapsed it. It would have gone on passing if the .ok filter it is named for were deleted — which it was, because it never existed. It now varies actor and stamp per pass, and fails against the old code.

Verified by mutation, not by reading

Reverting gained and the dedupe rule fails exactly the three tests named above and nothing else. _coerce_beat's silent discards are now counted and logged.

1,306 → 1,324 passing. Migration f7a8b0c1d2e3, applied and rolled back against a real database. Closing.

**Verified against acceptance criteria, and five defects fixed in `152048e`.** This is the issue whose stated purpose is that the accuracy floor "does not ride on model size" because the check is pure code — so a check that does not run matters more here than anywhere else in the pipeline. ## Criteria - [x] **Validator is pure code with no model call** — [`validate_beats`](webapp/backend/app/services/beat_service.py#L216) is synchronous and makes no request. - [x] **All four checks implemented, each independently unit-tested** — checks 1, 2 and 4 were genuinely done. **Check 3 was not**, three ways over: - `t_start <= t_end` was *repaired* in `_coerce_beat`, never recorded. - "inside the session" was **unreachable dead code**: `_coerce_beat` clamped `t_start` to `transcript_seconds`, then `validate_beats` tested `beat.t_start > transcript_seconds`. `"starts after the session ends"` could not be appended under any input. - "consistent with the cited evidence" **was never implemented at all**. - [x] **Failing beats are flagged and surfaced, never silently discarded** — plus two silent discards found and fixed, below. - [x] **Validated beats are ordered by `sorted()`** — and the sort key is now derived from verified data rather than a field nothing checked. - [x] **Validation results recorded per session** — `used_beats` was computed every run and never persisted, so the runs that *skipped* validation were the ones leaving no trace. Now every run gets a row. - [x] **A misattributed beat and a hallucinated-citation beat are both caught** — already true. ## The test that could not fail `test_a_beat_starting_after_the_session_ends_is_flagged` asserted only `result.beat.t_start <= max(index)`, which the clamp guarantees unconditionally. It never touched `result.ok` or `result.problems`. Its own comment hedged — *"the range problem may resolve"* — which reads like the author noticing and writing a weaker assertion rather than chasing it down. ## Why the evidence check re-anchors instead of rejecting My first implementation flagged a beat whose range contained none of its citations. The **`scrambled_chronology` eval fixture immediately showed that was wrong**: all five of its beats failed, so five real, correctly-attributed events dropped out of the summary. That fixture exists precisely to demonstrate this gap — its notes say so, and its expected `chronology_tau: -1.0` encoded the defect. The evidence has already been checked against the transcript; the declared range has been checked by nothing. When they disagree, the verified value wins. So the range is **re-anchored onto the citations**, which makes the chronology guarantee *stronger* than it was — the sort key now comes from transcript-verified timestamps rather than a model-supplied field. That fixture now scores **`tau = +1.0`** with coverage, attribution and validation all 1.0. Its expectations and notes are rewritten to record the fix rather than the gap; the five reversed timestamps still make it hand-checkable in both directions. A hallucinated citation is never used as an anchor — that would trade a wrong time the validator *reported* for a wrong time it *invented*. `BeatValidation.repairs` carries corrections, separate from `problems` and not affecting `ok`: a beat the code could fix did not fail. Persisted to `session_beats.repairs` and exposed through #424's API, because a silent correction is indistinguishable from a correct answer. ## dedupe_beats preferred hallucinations It kept whichever duplicate had more citations, with **no reference to the verdict** — and `gather_validated_beats` validates *before* merging, so both sides already carried one. A second-pass beat citing the same real line plus one invented stamp beat a clean single-citation beat. `render_beats_for_compose` skips failing beats, so the event then vanished from the summary having been both correctly extracted **and** correctly checked. Verified beats now win outright. ## The loop's docstring described a filter that did not exist *"'Did this pass find anything new' has to mean anything new that survives checking"* sat three lines above `gained = len(merged) - len(validations)`, which counted flagged beats. A pass of fresh hallucinations looked like progress and ran to the cap — a full re-extraction over every window, paid for nothing. `test_a_pass_of_pure_hallucination_does_not_keep_the_loop_running` passed for the wrong reason: its invented beat was identical every pass, so `dedupe_beats` collapsed it. It would have gone on passing if the `.ok` filter it is named for were deleted — which it was, because it never existed. It now varies actor and stamp per pass, and fails against the old code. ## Verified by mutation, not by reading Reverting `gained` and the dedupe rule fails exactly the three tests named above and nothing else. `_coerce_beat`'s silent discards are now counted and logged. 1,306 → 1,324 passing. Migration `f7a8b0c1d2e3`, applied and rolled back against a real database. Closing.

claude-bot referenced this issue

2026-08-28 19:14:40 +00:00

[Backend] Compose the summary from validated beats only, with a critic pass #334

claude-bot referenced this issue

2026-08-28 19:15:21 +00:00

[Backend] Resolve every speaker label to a character in code, and delete the prompt-time rename #329

claude-bot closed this issue

2026-08-28 19:15:59 +00:00

claude-bot referenced this issue

2026-09-06 19:53:16 +00:00

[Frontend] Show a GM the verified events behind a summary #424

rbrooks referenced this issue from a commit

2026-09-10 05:26:15 +00:00

fix(backend): stop the summariser reading a GM's answer as an event (#584)

claude-bot referenced this issue

2026-09-11 05:12:03 +00:00

fix(backend): no empty "What's next?", and collapse exact-duplicate beats (#595, #588) #598

rbrooks referenced this issue from a commit

2026-09-11 06:09:57 +00:00

fix(backend): dedupe keeps the story copy over a table_admin one (#596, #588)

claude-bot referenced this issue

2026-09-11 06:10:33 +00:00

feat(backend): label the GM's table admin instead of narrating it (#596) #599

No Branch/Tag specified

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

More information is needed

recording

Issue related to the recording system

security

Security hardening / vulnerability work

No labels

Milestone

Clear milestone

No items

No milestone

v4.0.0 - Session Pipeline Accuracy

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#333

Reference in a new issue

Repository

rbrooks/Quest-Board

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns