Commits
Marek Vsechovsky committed 4d4a95527e1
Session 174, Step 1: Exclude already-executed stories from Wf S2 Next-step input-prompt inclusion - AIM-3258 Exclude already-executed stories from Wf S2 Next-step input-prompt inclusion - AIM-3259 Wf S4 Process button stays disabled after cancelling processing via X → Cancel processing? - AIM-3260 Add a direct Cancel button to the Credit tracking dialog - AIM-3261 Auto-fix output-file numbering mismatch instead of reporting it first - AIM-3262 "What LLM model was used?" dialog with typeable filterable model dropdown for missing/incorrect step.model - AIM-3263 Increment AiAgent.AiAgentUsedCount by 1 per output-file submission using that model (skip when -1) - AIM-3264 Recent-models list (15 in localStorage) with 5 radio quick picks + 10 dropdown entries and server fallback loading - AIM-3265 Apply AiAgentSameAs exclusion/inclusion rules to the loaded model list - AIM-3266 Apply the selected model to the output file and continue validation with the updated file Outcome: Implemented 9 free-text requests: - issue -3901: executed stories (linked to processed steps) are no longer offered for inclusion into the new input prompt by the Wf S2 "Next step" dialogs. - issue -3902: the Wf S4 **Process** button is correctly re-enabled after cancelling processing. - issue -3903: the "Credit tracking" dialog gained a direct **Cancel** button. - issue -3904: numbering mismatches are auto-fixed by Aisman and only reported when the auto-fix fails. - issue -3905: new "What LLM model was used?" dialog with a typeable, filterable, auto-completing model dropdown. - issue -3906: `AiAgent.AiAgentUsedCount` is incremented by 1 per submitted output file (not counted when the counter is -1). - issue -3907: 15-entry recent-models `localStorage` list with 5 radio quick picks, 10 dropdown entries and a server fallback list. - issue -3908: `AiAgentSameAs` exclusion/inclusion rules applied to the loaded model list. - issue -3909: the selected model is applied to the output file and validation continues with the updated file. Session 174, Step 2: Use the single set-based available-models query instead of the in-memory version - AIM-3315 Use the single set-based available-models query instead of the in-memory version - AIM-3316 Record the efficient-query convention in project memory - AIM-3317 Evaluate the proposed AiAgentAliases composite indexes (inspect before creating) Outcome: Used the user's single set-based query for GetAvailableModels (-3897) and recorded the efficient-query convention in project memory (-3898). Evaluated both proposed composite indexes after live inspection (-3899): (ProjectId, AiAgentId) is fully redundant with the PK_AiAgentSameAs clustered key and by design not created, while (ProjectId, AiAgentSameAsId) has no coverage and was created as IX_AiAgentSameAs_ProjectId_AiAgentSameAsId via idempotent script 144 on the local dev DB. Session 174, Step 3: Clear the stale server-rejection record from 000_174-01.json - AIM-3318 Clear the stale server-rejection record from 000_174-01.json - AIM-3319 Copy generatedAt from the input into 000_174-02.json - AIM-3320 Renumber 000_174-02.json temp issue nums to the catalog-expected sequence - AIM-3321 Do not require generatedAt on output files created from direct steering Outcome: Implemented all four reported fixes: - issue -3897: `000_174-01.json` reference consistency re-verified against the server's temp-reference rules and its stale stored `-3903` rejection record cleared — the file no longer presents as server-rejected. - issue -3898: root `generatedAt` copied from `000_174-02.md` into `000_174-02.json`. - issue -3899: `000_174-02.json` temp nums renumbered to `-3897..-3899` (declarations, relations and outcome text remapped together) and the catalog registered for step 3 (`nextIssueNum` 3901). - issue -3900: `generatedAt` is no longer required on direct-steering outputs (`step.steeringPrompt`/`step.userStory` guard) and `dashboard.min.js` was rebuilt from all 15 bundle inputs so the app serves the fix. Session 174, Step 4: Preserve temporary parent and link references during server conflict renumbering - AIM-3322 Preserve temporary parent and link references during server conflict renumbering Outcome: Issue -3910: repaired server conflict renumbering so temporary parents and legacy links move with their declarations. Corrected 000_174-01.json outcome references to its current -3901..-3909 declarations and cleared the failed-run record. Application compilation and an executable C# remapping regression fixture passed. The processing server must run the updated controller before retrying import. Session 174, Step 5: Make conflict renumbering atomic and return the correct original-to-actual issue mapping - AIM-3323 Make conflict renumbering atomic and return the correct original-to-actual issue mapping Outcome: Issue -3911: prevent ambiguous conflict repair, apply one complete temporary-number map to declarations and references, and reconcile original numbers to the newly imported issue instead of unrelated occupied-number rows. Application compilation and two executable regression checks passed. Server deployment or restart is required to activate the prevention fix.