Commits
Marek Vsechovsky committed 957c492fa6a
Session 161, Step 1: Answer Chrome "Free up space" dialog, Aisman storage footprint, and localStorage quota questions
- AIM-3155 Answer Chrome "Free up space" dialog, Aisman storage footprint, and localStorage quota questions
- AIM-3162 Issues main list: aim-ready-icon rendered in front of .aim-list-item-inner instead of inside .aim-list-item-text
- AIM-3163 Wf S1: steps-ago indicator (-NS label) with click-to-highlight issues last processed in the same step
- AIM-3164 Fix syntax error in dashboard-settings.js (trailing comma) breaking conventions browser and min.js bundle
Outcome:
Answered the Chrome storage questions in issue -3752: what Aisman concretely stores (2 MB of `AimLS` localStorage keys + 5 server-set auth cookies), the per-origin `localStorage` quota (~10 MB in Chrome, `navigator.storage.estimate()` for monitoring), and that no API lets an app request more quota (`navigator.storage.persist()` only protects existing data from eviction).
Fixed issue -3753: the ready icon now lands inside `.aim-list-item-text` — after the `ACR-NUM ` prefix in `.aim-issue-list-label` — uniformly across all issue types and all issue list groups. Runtime propagation (`propagateReadyState`), the session-row status sync (`wfSyncSessionTab`) and inline title edits (`syncIssueListItemTitle`) all go through the new shared `Dash.Iss.insertReadyIconNearTitle()` helper, matching the build-time markup produced by `buildIssueListItem()`.
Implemented issue -3754: Wf S1 renders the `-NS` steps-ago pill for every issue not processed in the latest step (new `GET /api/sessions/{sessionId}/issue-last-steps` endpoint feeding `S.workflow.lastStepMap`), with primary-colored thin border and text on transparent background, the requested tooltips (`Last processed N step ago in step S.`), and a stop-propagation click that fills the pill plus every sibling last processed in the same step with primary/white and toggles all off when clicked again (state kept in `S.workflow.stepsAgoHighlight`, styled by `.aim-wf-steps-ago`/`.aim-wf-steps-ago-on` in `dashboard.scss`).
Fixed issue -3755: the stray trailing comma left in `_renderConventionsBrowser()` by commit `ebc69f4b` was a syntax error that killed the settings script at load and made `npx terser` fail; terminating the declaration with `;` restored the conventions browser and allowed the production `dashboard.min.js` bundle to be rebuilt with all of this step's changes.
### 000_161-02.json
Session 161, Step 2: No way to close the Crop & Annotate overlay on the Screenshots page
- AIM-2723 No way to close the Crop & Annotate overlay on the Screenshots page
Outcome:
Reworked issue -3754's data flow per the correction: the dedicated `GetIssueLastSteps` endpoint in `SessionsController.cs` and the extra `_wfEnsureLastStepMap()` fetch inside `loadWfIssues()` are gone. `GetUnfinishedIssues` now projects `lastProcessedStepNum` per issue inside its existing single EF Core query (correlated `MAX(SessionStepNumber)` over the session's `SessionStepIssues`, null when no session is selected) and returns `latestStepNum` from the last-step row it already loads for `previousStepIssueIds`. The client stores both values from that same payload (`S.workflow.latestStepNum`, `issue.lastProcessedStepNum`), so `_wfBuildStepsAgoHtml()` renders the unchanged `-NS` labels, tooltips and same-step highlight with zero additional server round trips — the labels are present on the very first paint of the list.
Session 161, Step 3: Validate and further optimize GetUnfinishedIssues for minimal server resource usage
- AIM-3155 Optimize GetUnfinishedIssues for minimal server resource usage (schema-validated rewrite)
Outcome:
Wf S1 unfinished-issues now answers in half the SQL round trips (16 → 8 per session load) with every per-issue flag resolved inside the main statement, backed by the seek indexes from script 133; the dashboard response contract is preserved (issueParentId added, which the client already reads), the session total derives from the loaded membership list, and the unassigned counters come from one grouped pass instead of a counter gate plus three counts.