feat(dashboard): show admin bot profiles#1213
Conversation
|
Codex validation pass for #1213 on 2026-05-26. Scope checked:
Validation on PR head:
Acceptance notes:
Merge rehearsal:
I did not find a blocker for the #425 acceptance in #1213. GitHub still reports this PR as |
|
Current-main closure-path evidence for #425. Commits checked:
Environment/artifacts:
Acceptance checked:
Commands/results:
Result:
|
|
Current-main validation for #425 on 2026-05-29. Validated PR head Acceptance evidence:
Commands run:
Environment: Remaining gap: GitHub reports this PR as |
|
Current-main validation refresh for #425, without force-pushing the PR branch. Evidence:
Passed:
Acceptance status: PR #1213 still satisfies #425 on current main. Remaining blocker: PR #1213 is still |
9fe86a3 to
798c937
Compare
|
Current-main refresh evidence for #425 / PR #1213:
Commands passed: Result:
Issue acceptance: AdminBotPage now loads and shows admin profiles with running/stopped status, has an empty state, links to Remaining gap: GitHub CI is running on the refreshed head. The PR is still expected to be branch-protection blocked by required review before merge/auto-close. |
|
Final CI refresh for #425 / PR #1213:
Result: #1213 is current-main green and satisfies #425 acceptance evidence. Remaining gap: branch protection still reports |
c0912cc to
b905099
Compare
b905099 to
ba8008d
Compare
Summary
/profiles/new?adminMode=trueand makeNewProfilesubmitadmin_mode: truewhen that shortcut is used.AdminBotPageandNewProfiletests.main/origin/main1df02bd3975a66b232ae1a5c62ddf48297f88317; refreshed headba8008dc04590bc255121953787d21c9c4bb3375.Closes #425
Validation
Environment: isolated clone
/Users/yuechen/home/octos/target/octos-1213-refresh.rIYT6Z/octos; root checkout left untouched; npm cache/private/tmp/octos-npm-cache-425-current; explicit dashboard build output/private/tmp/octos-425-dashboard-build-current-1df02.Passed locally:
git diff --check origin/main...HEADcargo fmt --all -- --checkgit ls-files --others --exclude-standard-> emptyNPM_CONFIG_CACHE=/private/tmp/octos-npm-cache-425-current npm --prefix dashboard ci-> completed with existing npm audit findings only: 3 vulnerabilities, 1 moderate and 2 highNPM_CONFIG_CACHE=/private/tmp/octos-npm-cache-425-current npm --prefix dashboard test -- AdminBotPage NewProfile-> 2 files / 3 tests passedNPM_CONFIG_CACHE=/private/tmp/octos-npm-cache-425-current npm --prefix dashboard test-> 8 files / 35 tests passedNPM_CONFIG_CACHE=/private/tmp/octos-npm-cache-425-current npm --prefix dashboard run typecheckNPM_CONFIG_CACHE=/private/tmp/octos-npm-cache-425-current VITE_OUT_DIR=/private/tmp/octos-425-dashboard-build-current-1df02 npm --prefix dashboard run buildNPM_CONFIG_CACHE=/private/tmp/octos-npm-cache-425-current ./scripts/milestone-ci.sh dashboard-> passed and left the checkout cleantypos dashboard/src/pages/AdminBotPage.test.tsx dashboard/src/pages/AdminBotPage.tsx dashboard/src/pages/NewProfile.test.tsx dashboard/src/pages/NewProfile.tsxGitHub CI passed on refreshed head
ba8008dc04590bc255121953787d21c9c4bb3375:checkcheck-matrixdashboardswarm-apptest-octos-agent (lib)test-octos-agent (integration)test-octos-clityposreject blocked author/committer emailsNo generated artifacts are included. Explicit dashboard build output stayed under
/private/tmp/octos-425-dashboard-build-current-1df02; milestone output left no tracked or untracked diff.Current State
mergeStateStatus=BLOCKED,mergeable=MERGEABLE, andreviewDecision=REVIEW_REQUIRED; remaining blocker is required review.