dreampiler/kandev
1
0
Fork 0
Code Issues 43 Pull Requests Actions 6 Packages Projects Releases Wiki Activity

Kandev: dynamic route generation advances during a live session but the ACP model is not reapplied #86

New Issue
Closed
opened 2026-10-14 15:25:19 +09:00 by dreampiler · 1 comment
dreampiler commented 2026-10-14 15:25:19 +09:00
Owner
Copy Link
Copy Source

From model-mismatch investigation c258fc18 (P1): in sessions 39106092 and 10d5b0f4 the dynamic route state and task session execution_profile_id advanced to gen2 while acp_model_state.current_model_id kept the gen1 model and no gen2 relaunch was logged. Determine the trigger (failure fallback vs new-turn re-evaluation) and the missing model re-apply path; fix so the live model matches the route generation or the mismatch is explicitly recorded. Fork-only route generation (not an upstream candidate except any start_model overlap). Kandev task 49f4e5b3 under root 8e3eb6b7.

From model-mismatch investigation c258fc18 (P1): in sessions 39106092 and 10d5b0f4 the dynamic route state and task session execution_profile_id advanced to gen2 while acp_model_state.current_model_id kept the gen1 model and no gen2 relaunch was logged. Determine the trigger (failure fallback vs new-turn re-evaluation) and the missing model re-apply path; fix so the live model matches the route generation or the mismatch is explicitly recorded. Fork-only route generation (not an upstream candidate except any start_model overlap). Kandev task 49f4e5b3 under root 8e3eb6b7.
dreampiler commented 2026-10-14 17:04:00 +09:00
Author
Owner
Copy Link
Copy Source

ROUTE-GEN-MODEL done. PR #313 merged (squash) merge-commit 8f5aca3dd2ebac1426969528d8639839be737819, head fa260b4c88. Cause: manual route action changed the concrete candidate but did not clear the previous candidate's provider state (runtime_config/acp_model_state), so the fresh ACP session applied the old generation's model. Fix: clear the shared provider-state keys on a real candidate change + WARN after a committed change. Verified: go build/test/vet/lint (narrow). Remaining: none. Follow-up: minor test-coverage 6d02af45 not included (non-blocking).

ROUTE-GEN-MODEL done. PR #313 merged (squash) merge-commit 8f5aca3dd2ebac1426969528d8639839be737819, head fa260b4c88. Cause: manual route action changed the concrete candidate but did not clear the previous candidate's provider state (runtime_config/acp_model_state), so the fresh ACP session applied the old generation's model. Fix: clear the shared provider-state keys on a real candidate change + WARN after a committed change. Verified: go build/test/vet/lint (narrow). Remaining: none. Follow-up: minor test-coverage 6d02af45 not included (non-blocking).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dreampiler (dreampiler)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dreampiler/kandev#86
Delete Branch "%!s()"

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?