Testfinally/#39
Conversation
…ling-connections Fix dangling connection deletes
…e-1129 Revert staging backport of issue 1129
This reverts commit e85da38.
…play-avatar-height Fix roleplay panel avatars clipping on short messages
…rom-staging Revert issue 1272 from staging
…alpha-workflow Register pre-alpha build workflow on default branch
✅ Bunny Review CompletedTip Review posted. The specimen has left the observation table.
|
🐰 Bunny ReviewCaution Specimen unstable. 1 finding(s): 🚫 1 blocking Note Mode: 🧭 Specimen Summary
🔎 Isolated Defects
🤖 Repair prompt for isolated Bunny findings✅ Control Checks
❓ Open Questions
🧪 Observations
🧰 CI Status
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| || echo "::warning::Unable to write Bunny command status before dispatch." | ||
|
|
||
| set +e | ||
| DISPATCH_OUTPUT="$(gh workflow run bunny-review.yml \ |
There was a problem hiding this comment.
🚫 BLOCKING: Command dispatch targets a missing reviewer workflow
Location: .github/workflows/bunny-review-command.yml:78
The gateway invokes
gh workflow run bunny-review.yml, yet the bounded review context reports no matching.github/workflows/bunny-review.ymlcontract or workflow-dispatch inputs. Every accepted slash command can therefore mature into a GitHub CLI rejection rather than a review. The wrapper has been assembled, but the organ it stimulates is absent from the observed repository.
Tip
Suggested fix: Add the trusted bunny-review.yml workflow with matching workflow_dispatch inputs, or dispatch an existing workflow file that actually exists on the selected ref.
🤖 Repair prompt for agents
Use this as an implementation handoff, not as reviewer prose. Keep the response concise, technical, and direct.
Task: verify and repair `.github/workflows/bunny-review-command.yml` around line 78.
Finding: Command dispatch targets a missing reviewer workflow
Severity: blocking
Suggested repair: Add the trusted `bunny-review.yml` workflow with matching `workflow_dispatch` inputs, or dispatch an existing workflow file that actually exists on the selected ref.
Validate the fix with the narrowest relevant check.
If the finding is stale, leave the code unchanged and record why.
| PR_NUM: ${{ github.event.issue.number }} | ||
| COMMENT_BODY: ${{ github.event.comment.body }} | ||
| COMMENT_AUTHOR: ${{ github.event.comment.user.login }} | ||
| TARGET_REF: refactor |
There was a problem hiding this comment.
⚠️ MEDIUM: Dispatch ref is frozen to an unexplained branch
Location: .github/workflows/bunny-review-command.yml:28
The command hard-codes
TARGET_REF: refactor, while the packet names a different review target and repository guidance points normal development atstaging. Ifrefactordisappears, lags, or lacks the expected workflow inputs, the accepted command fails or runs stale reviewer logic. A trusted bootstrap should not hide branch selection inside a literal fossil.
Tip
Suggested fix: Derive the dispatch ref from the PR base ref or a documented protected repository variable, and expose that resolved value in the status comment.
🤖 Repair prompt for agents
Use this as an implementation handoff, not as reviewer prose. Keep the response concise, technical, and direct.
Task: verify and repair `.github/workflows/bunny-review-command.yml` around line 28.
Finding: Dispatch ref is frozen to an unexplained branch
Severity: medium
Suggested repair: Derive the dispatch ref from the PR base ref or a documented protected repository variable, and expose that resolved value in the status comment.
Validate the fix with the narrowest relevant check.
If the finding is stale, leave the code unchanged and record why.
| dispatch: | ||
| if: > | ||
| github.event.issue.pull_request && | ||
| startsWith(github.event.comment.body, '/bunny-review') && |
There was a problem hiding this comment.
ℹ️ LOW: Slash-command matcher admits prefix impostors
Location: .github/workflows/bunny-review-command.yml:17
The job guard uses
startsWith(..., '/bunny-review'), so/bunny-reviewerand/bunny-review-anythingstill dispatch the trusted workflow. The later mode parser is stricter, but the expensive action has already been summoned. The command grammar is therefore looser than the status ritual claims.
Tip
Suggested fix: Use a boundary-aware predicate, such as ^/bunny-review([[:space:]]|$), before dispatching.
🤖 Repair prompt for agents
Use this as an implementation handoff, not as reviewer prose. Keep the response concise, technical, and direct.
Task: verify and repair `.github/workflows/bunny-review-command.yml` around line 17.
Finding: Slash-command matcher admits prefix impostors
Severity: low
Suggested repair: Use a boundary-aware predicate, such as `^/bunny-review([[:space:]]|$)`, before dispatching.
Validate the fix with the narrowest relevant check.
If the finding is stale, leave the code unchanged and record why.
| # This pull_request_target workflow is intentionally a dispatcher only. | ||
| # It must not checkout, install, or execute code from the pull request. | ||
| gh workflow run bunny-review.yml \ | ||
| --repo "${{ github.repository }}" \ |
There was a problem hiding this comment.
🚫 BLOCKING: Auto dispatch targets a missing reviewer workflow
Location: .github/workflows/bunny-review-auto.yml:33
The dispatcher invokes
gh workflow run bunny-review.yml, yet the provided workflow context does not contain that workflow, and the adjacent Bunny command workflow uses the same apparently absent target. GitHub rejects dispatches to nonexistent workflow files, so eligible PR events would produce failed automation rather than reviews. A machine built to observe the experiment cannot begin if its heart is imaginary.
Tip
Suggested fix: Add the trusted bunny-review.yml workflow with the expected workflow_dispatch inputs on the target ref, or point this dispatch command at the actual reviewer workflow file that exists.
🤖 Repair prompt for agents
Use this as an implementation handoff, not as reviewer prose. Keep the response concise, technical, and direct.
Task: verify and repair `.github/workflows/bunny-review-auto.yml` around line 33.
Finding: Auto dispatch targets a missing reviewer workflow
Severity: blocking
Suggested repair: Add the trusted `bunny-review.yml` workflow with the expected `workflow_dispatch` inputs on the target ref, or point this dispatch command at the actual reviewer workflow file that exists.
Validate the fix with the narrowest relevant check.
If the finding is stale, leave the code unchanged and record why.
* Fix mobile composer text input collapse (Pasta-Devs#1136) * Fix tracker aliases, avatars, HUD temps, and changelog (Pasta-Devs#1137) Resolve tracker characters through active-chat names, aliases, title/comment aliases, and bracketed aliases so group chats can match card names that differ from tracker names. Preserve uploaded NPC tracker avatars and portrait focus across agent refreshes, including first snapshot writes, without copying manual avatars onto real character-card IDs. Reuse the shared temperature display helpers in the roleplay HUD so the tracker temperature unit setting applies there too. Backfill changelog entries for recent Xel PRs and record the tracker hotfix under 1.6.1. * Reduce chat startup and focus refetch lag * Revert "Reduce chat startup and focus refetch lag" This reverts commit e85da38. * Register pre-alpha workflow on default branch * Add Bunny review command bootstrap (Pasta-Devs#1821) * Register Bunny auto review dispatcher on main (Pasta-Devs#1872) * Enable Bunny dispatch for draft PRs (Pasta-Devs#2026) * Update Bunny auto dispatch bootstrap (Pasta-Devs#2261) * Enable Bunny review bootstrap on main (Pasta-Devs#2406) * Fix Bunny main CI check names --------- Co-authored-by: Xel <Xelvanas@gmail.com> Co-authored-by: Spicy_Marinara <mgrabower97@gmail.com> Co-authored-by: munimunigamer <munimunigamer@protonmail.com> Co-authored-by: Promansis <damon.kyle.walling@gmail.com>
5 participants
Linked issue
Closes #
Why this change
What changed
Validation
pnpm checkpasses locallyCONTRIBUTING.mdManual verification notes
Docs and release impact
UI evidence (if applicable)