Skip to content

Add Scores and Bug origins pages to the Console - #1291

Merged
JacobStephens2 merged 2 commits into
issue-978from
issue-1031
Oct 25, 2026
Merged

JacobStephens2 merged 2 commits into
issue-978from
issue-1031

Conversation

@JacobStephens2

@JacobStephens2 JacobStephens2 commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

Summary

Console
├── Scores → weekly samples, calibration, five human Scores → reveal model Scores
└── Bug origins → proposed and settled origins → confirm / correct / reject

Closes #1031

Test seams

  • Console HTTP routes paired with the scoring and Bug-origin CLI commands, using retained private sample files and fake GitHub at its executable interface.
  • Browser navigation and submitted forms at 390 px, including withholding model Scores until all five human Scores are entered.

Evidence

  • Before: cargo test --test console scoring::scores_commit_five_human_scores_before_revealing_the_model_and_pair_with_cli failed because /scores returned 404; the Bug-origin route test likewise returned 404.
    After: cargo test --test console scoring:: passes all 3 regressions: atomic blind entry, all three Bug-origin actions paired with CLI results, and Console termination after form actions. The phone browser regression passes all four actions, keyboard jumps and escaping at 390 px.
  • cargo check --locked and cargo clippy --all-targets --locked -- -D warnings pass. Existing Scoring/Bug-origin tests and route/CLI registration checks pass.
  • scripts/affected-tests origin/issue-978: passed the full Rust suite (cargo test fallback) and all 50 public-site browser tests. /usr/bin/time -p around the selection reported 1386.12 s wall time, including compilation (Rust build: 37.75 s) and browser checks.
  • npm test --prefix console: 83 passed, including the new 390 px regression.

Merge Danger

Door: two-way

Blast Radius: Scoring

New views and authenticated forms write existing human-Score and Bug-origin formats through the CLI's operations. No migration; rolling back the binary preserves readable records.

Unaddressed findings

  • Standards: None. The review's P3 duplicate-fixture finding was addressed by sharing one fixture across route and browser tests.
  • Spec: None; no findings were declined or deferred.
  • Security: None.

Security review outcome

No unaddressed introduced findings.

Review coverage

Both independent axes read all 21 changed files against issue-978 at 093ac915da261a170083b344682640362bc94fc4, including the final fixture consolidation. Changed files left unread: none. Generated-output exclusions: none.

Built with codex · gpt-6.1-sol · xhigh

@JacobStephens2
JacobStephens2 merged commit d305b7e into issue-978 Oct 25, 2026
18 checks passed
@JacobStephens2
JacobStephens2 deleted the issue-1031 branch October 25, 2026 01:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant