CodeSnuffler Forgejo End-to-End historical review range codesnuffler-forgejo-live-20260630T041807949Z-bd8cb7ec-69e #49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "change_forgejo_end_to_end"
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?
Exercise the live Forgejo webhook review pipeline against a stable historical CodeSnuffler diff.
Run marker: codesnuffler-forgejo-live-20260630T041807949Z-bd8cb7ec-69e.
Run started at: 2026-06-30T04:18:07.949Z.
Fixture range: f9d210eccd0075b6b39b606cea9b1376719aa062..d8a3fc420b055e04df1d203706b89b1f1261a9c1.
This two-commit AI Harness range stops before
404b386cremoved stale persona and old-shape compatibility, so the review is expected to produce actionable findings.CodeSnuffler Review Findings
Findings
1. Dev shell still sends removed persona_id query parameter
frontend/src/dev-shell/components/DevShellTerminal.vue:155dev_shell_websocketnow readsinstance_id, but the frontend terminal still sendspersona_id. For runner auth commands launched from this component, any non-primary selected identity is dropped and the backend falls back toprimary, so auth/login can target the wrong plugin instance.Open finding in CodeSnuffler
Fix via CodeSnuffler
Suggested fix: Rename the prop to
instanceId(or map the existing prop at the boundary) and sendurl.searchParams.set("instance_id", ...); update callers and tests to use the current field name.2. AI review policy choices still expose persona_id
app/settings/ai_review_policy/schemas.py:76The PR standardizes the AI tool identity shape around
instance_id, but this response schema still exposespersona_id, and the generated frontend type/components continue consuming it. That leaves a public old-shape API in place, contrary to the repository's no-compatibility-shim policy for removed fields.Open finding in CodeSnuffler
Fix via CodeSnuffler
Suggested fix: Replace this field with
instance_idin the schema/service projection, regenerate frontend API types, and update the Vue label helpers to consumeinstance_idwith user-facing text changed from persona terminology.3. Persona alias remains as runtime compatibility shim
app/ai_tools/instances.py:226-227AiToolInstanceConfig.persona_idremains as an alias forinstance_id, and current code still calls it in storage paths. Because this PR removes/standardizes persona-shaped auth identity, keeping the alias and runtime reads preserves the old shape instead of completing the cleanup required by AGENTS.md.Open finding in CodeSnuffler
Fix via CodeSnuffler
Suggested fix: Remove the
persona_idproperty and replace remaining runtime uses such asconfig.persona_idin storage/materialization code withconfig.instance_id; keep only negative tests/docs that assertpersona_idis rejected.Pull request closed