FailedProxy
  • Joined on 2026-03-21
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 02:13:13 +00:00
d5944c2443 Sweep every onclick built from data: an unescaped quote silently killed nine handlers
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 02:08:11 +00:00
d135dff5cd An unescaped quote ended the onclick attribute early, so clicking an error line did nothing
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 02:00:46 +00:00
62a838ebdd Clicking a recent error opens the log on that line and acks it, so acknowledged means seen
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 01:51:57 +00:00
f2d0e18f2c Ask about a run from the row it is on, and stop spending context on health checks when the run was clean
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 01:38:43 +00:00
4347fc5f07 Capture the dock phrasing that worked, so it keeps working
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 01:34:06 +00:00
ce0cbd868c Write down the routing every bug so far produced, and check it without asking the model
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 01:27:27 +00:00
2658082607 Explain mode: show what a question would be given and why, without asking the model
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 01:17:58 +00:00
55aa7f968f A phrase list missed one word order, and the assistant answered a log question with a command that re-runs the job
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 00:56:48 +00:00
0882942164 General Chat now hands a Varaverk question up to the Assistant instead of telling the operator to do it
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-07 00:51:21 +00:00
917ff43795 Profile permissions belong in one table, because scattered they hid a capability chat was never meant to have
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 22:49:19 +00:00
d562644581 State the no-citation rule for run evidence in the contract itself, since as an amendment it lost
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 22:48:02 +00:00
02aa73bb8d Chat invented a log inspection when asked how a run went, and the rundown cited passages it had not read
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 22:45:57 +00:00
0fa871ef61 The run-outcome gate ignored the profile, so chat could be handed a log it is promised it never sees
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 22:43:14 +00:00
815ceef276 A question about how a run went should arrive with the run attached, not with directions to the log panel
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 22:36:50 +00:00
10c1705790 An answer sized the assistant dock past the bottom of the page because nothing refit the panel after it landed
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 22:28:21 +00:00
e467cdaf23 The scheduler AI dock read the poll envelope as the job, so every answer hung on thinking
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 01:25:01 +00:00
269ef9b2de Verify a bug report's component and evidence before filing it
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 01:12:42 +00:00
657ee435d1 Add a copy-out button that formats a report as a pasteable issue
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 00:55:59 +00:00
2f8af3a1b7 Say the bug was recorded locally, because that is what happened
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-06 00:48:55 +00:00
2c5e412d91 File AI-detected Varaverk defects as deduped reports, surfaced on the AI tab and counted in the coffee report