Repository navigation
test(roster): RT-06 Seat staffing and per-profile concurrency admission #420
Description
RT-06: Seat staffing and per-profile concurrency admission
Campaign: eve-post-development-20261011
DEFERRED - do not execute. Development must be reviewed/integrated before the final candidate is frozen and Ray authorizes the round.
| Field | Declaration |
|---|---|
| Work item | Acceptance scenario RT-06; not a runnable implementation issue |
| Board | Roster Test; Backlog |
| Priority / mode | P1 / Mixed |
| Candidate SHA / manifest | Pending post-development freeze; old fingerprints do not identify this round |
| Attempts / result / evidence | 0 / Not run / Not run for this campaign |
| Owner / estimate | Operator approval required; not staffed; estimate pending corpus and environment |
Matrix: #414
Project: https://github.com/users/R4yHarris/projects/3
Spec: FEATURE_SPEC section 5.2: Roster and staffing; honor sections 3 and 7.
Baseline: pending final reviewed/integrated candidate SHA and frozen configuration; never reuse an old uncommitted fingerprint.
Mode: Mixed | Priority: P1 | Initial result: Not run | Evidence stage: Not run
Outcome
Demonstrate the named operational behavior with attributable evidence, or record a failure, blocker or unresolved spec decision without claiming success.
Prerequisites
Operator procedure
- Inspect configured principals, skills, tools, difficulty limits and profile context/concurrency/hardware before executing a bounded issue.
- With a controlled delayed compatible endpoint, submit concurrent child requests to profiles with capacities one and two; record active-request counters and FIFO order.
- Cancel one queued and one active request; observe drain, heartbeat and capacity release, then make another request.
Acceptance checks
- Each task's planner/coder/reviewer is sequential with one writer per worktree; seat tool restrictions remain effective.
- Observed active HTTP requests never exceed the selected profile's declared concurrency, and cancellation releases only owned capacity.
- Queued requests use the implemented FIFO order; queue depth is not treated as failure or measured model throughput.
- Missing hardware/context stays unknown; ineligible skill/difficulty staffing is documented as a gap if not enforceable rather than claimed from configuration alone.
Evidence and result
Use the matrix observation template. Append one redacted observation per actual attempt/case. Do not replace failed attempts with a later pass. Include run/seat IDs, exact interface, actual verification/review and human rating only when observed. Fixture results must be labeled fixture, not live operational evidence.
Fresh campaign starts at Not run. Previous comments, observations and evaluations are retained as historical evidence; they are not new-round results. Only observations tied to this candidate and campaign count. All required cases need new evidence and human review before Result becomes Pass. Unavailable prerequisites are recorded as fresh Blocked observations, not inherited old outcomes.
Safety and non-goals
This is TEST work, not a build task. No product/source/policy/workflow/vendor edits are requested; do not execute this issue as an implementation slice. Use disposable approved fixtures and separately approved bounded model tasks. No actual credentials, prompt/source bodies or transcripts may be posted.
No model calls, spend, publication, process termination or destructive cleanup are authorized by issue creation. Obtain explicit operator approval before those operations. Keep this issue only in Roster Test. Cross-link a separate Roster Build issue for any discovered defect; keep test failure evidence here and rerun after the fix.
Workflow and release gate
Backlog -> Ready only after dependencies, candidate freeze, disposable scope and budgets are approved. In progress means actual authorized execution; In review means evidence is awaiting independent/human review. Done/Pass requires all original required cases and genuine human acceptance, not a subset of green fixtures. A defect creates a separately scoped Roster Build issue; retain its failing observation here.
Plain-text Ask example
Plan two independent bounded documentation tasks and explain how profile capacity limits admission. Do not start concurrent workers. Output it in a new "staffing-guide" directory
Use: Illustrative entry point only. This scenario remains deferred; the original operator procedure and acceptance cases are still required.
A prompt alone does not verify this scenario. Operator-controlled fixtures, actual evidence and genuine human review remain mandatory. Never execute a TEST issue as a product implementation issue.
Activity
r4yharris-agent-coder commentedon Oct 10, 2026
Fresh RT-06 observation
Fresh campaign eve-matrix-9f80afa-20261010; candidate 9f80afa, contracts 61b97b3e93e670a675c0301cce5412c73404d179. Windows, Node v20.20.2. Original matrix protocol #414; previous 28044dd observations are not carried forward.
Full existing suite: ROSTER_TEST_JOBS=2; npm exec --yes --package=node@20 -- node scripts\run-tests.mjs. Exit 0; 171 files, 1593 tests, 1586 passed, 0 failed, 7 skipped; 784.0s wall. Nine 60-second file-budget warnings retained. This is fresh fixture/regression evidence, NOT whole-scenario operational acceptance, idle benchmark or human AI-Eval. Missing platforms, actual TTY, multi-model corpus and publication variants are not replaced with fixtures.
Evidence stage denotes the highest evidenced subcase only; it does not certify every required gate. Human evaluation/reviewer: absent. No TEST issue was sent wholesale to roster run; no policy/workflow/vendor edits, saved-default changes, deployments or disposable-product publication. Board: https://github.com/users/R4yHarris/projects/3
Spec: FEATURE_SPEC 5.2, honoring sections 3 and 7.
Whole-scenario disposition: Blocked.
Staffing/admission fixtures pass; actual controlled capacity/profile concurrency variants missing.
Fresh known lock failure is cross-linked to existing Build defect #441; Node20 code-planning failure is cross-linked to #454. Corrected live observations: one docs delivery/reviewer pass after automatic continuation, one code failure before coder; 1/2 reviewed yield, 0/2 first-pass yield, no human acceptance. Initial four experiment runtime/input mistakes and unavailable usage/exception evidence are retained, not relabeled as successful deliveries. See the new campaign summary on #414 for exact live outcomes and the complete 24-row disposition.
[-]TEST RT-06: Seat staffing and per-profile concurrency admission[/-][+]test(roster): RT-06 Seat staffing and per-profile concurrency admission[/+]r4yharris-agent-coder commentedon Oct 13, 2026
Authorized profile-admission fixture subset
Ray scopedofflinebatchauthorization2026-10-13 renewed17:19. OBSERVATIONcandidatef3bb779123dc73f1d52e278e2e0ca4b3510de7e5 contracts0050ada; Node20.20.2 Windows. Exactcommand:
node --test --test-reporter=tap tests\coder.scope.test.mjs tests\admission.test.mjs tests\llm.admission.test.mjs tests\route.admission.test.mjs
23/23PASS0fail0skip0cancel7233.8903ms. Validcommandexit0; precedingversionprobe failedonmistypedbinarypath, no runtimeinstall or defaultswitch. Fileauthorized-authority-admission-20261013.log retained. Scopecontrol in this selector is specificallyscratchcreate/delete accounting, NOT allprotectedpathauthority checks.
Admissionfixtureproof: concurrency2/FIFO, separateprofilequeues, queuedabortnoleak, one-shotownedrelease/detachedlisteners, failedrequestslotrelease, directseatchats sharingprofilelimit, busyroutewithoutquarantine/failover; evalhistory outranksqueuedepth. Saveddefaultwithoutfleetprofile intentionallynotlimited. Testsarecontrolledoffline endpoints, not measuredproductionthroughput/distributedadmission/hardwareproof.
RT-06 fullstaffing/skills/heartbeat/alloperatorcases and RT-04prerequisite remainoutstanding; noPassDone/humanrating. No model/spend/publish calls, productsourcechange or fullcampaignexecution. Spec§§5.2/5.4/5.8 honors3/7. Actualcodeproofslice#611 runsindependentlytest-only; no liveCopilotcontainmentclaim.
Read-onlyAppdiagnostic confirms configuredr4yharris-agent-coder installationadministration:null checks:read; tokenmintHTTP422 permissionsnotgranted. Ray's reportedgrant retained but effectiveAPIpermissionnotyetvisible; nofallback/consumerPRmutation.
r4yharris-agent-coder commentedon Oct 14, 2026
Board reconciliation 2026-10-14: Status In progress, Evidence stage Attempted; full Result remains Not run.
Existing authorized subset observation: 23/23 pass, zero skips, 7233.8903ms; candidate f3bb779. Original detailed selector, boundaries and failures remain in the retained evidence.
Full staffing/skills/heartbeat and RT-04 prerequisite acceptance remain outstanding. No new test execution, live inference, full scenario Pass/Done or human evaluation claimed. The stale Backlog/Evidence Not run fields are corrected, not used to erase acceptance requirements.