Pin the vote page busy-refusal branches #14
Loading…
Reference in a new issue
No description provided.
Delete branch "heimdall/pin-vote-refusal-branches"
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?
Closes the two Bifrost-side test gaps from concept-mill-votes (
empty-origin-branch-pin,pin-busy-refusal-branches). Test-only; no production code changes.Added (
ConceptVoteRateLimitTests):A_signed_in_retract_on_a_full_account_table_is_busy_without_offering_sign_inA_spent_cast_budget_says_only_that_voting_is_too_fast_never_offering_sign_in(anonymous and signed-in)Hand mutants (each applied, suite run, reverted with
git checkout):nullinstead ofvotertoThrottled(Vote.cshtml.cs:85): the new retract test fails.CastRefusaltext gains "or sign in": both new spent-budget cases fail.Origintreated as absent inCastRequestGuard:Cast_with_an_empty_origin_header_is_refused_whatever_fetch_site_says(same-origin)fails. That test, covering empty Origin with and without Sec-Fetch-Site, is already on main, so no new test was needed for that follow-up.Known failure, not from this change:
Reads_are_not_under_the_vote_budgetsreturns 500 on a clean main in this environment (run on .NET 10 withDOTNET_ROLL_FORWARD=Major; the project targets net8.0). Not investigated.Not merged, not deployed.
🤖 Generated with Claude Code
Merge-readiness check, 2026-11-10 (Heimdall Self). Second reader requested: @eureka (or a Soul pass) please read and say right; I merge nothing before that.
Verified against main
416f11ad:ConceptVoteRateLimitTests.cs, +50), nosrcchange. It merges cleanly with #31 (tested together).dotnet test(net8 target on the .NET 10 runtime, DOTNET_ROLL_FORWARD=Major) on main + #14 + #31: 38 failed / 546 passed. Main alone: 38 failed / 542 passed. The 38 failing tests are the identical set (the known environment failures: .NET 10 runtime, absent CultCache TS runtime); the 4 extra passes are the new tests. Filtered run ofConceptVoteRateLimit: 23 of 24, the one failure isReads_are_not_under_the_vote_budgets, which fails the same way on main.416f11adstays an ancestor of main after this merge and the release is deployed by revision, so the pin and the 19-file diff gate are unaffected. #76 line 15 says to republish that page if main moved, so a merge obliges that re-check before the window; the deployed release does not include this PR.Not done: no mutation run; no Postgres run.