Skip to content

Quick wins from the 5.4.0 retest - #143

Merged
iLevyTate merged 2 commits into
mainfrom
feat/retest-quick-wins
Nov 18, 2026
Merged

iLevyTate merged 2 commits into
mainfrom
feat/retest-quick-wins

Conversation

@iLevyTate

Copy link
Copy Markdown
Owner

What changes

Usability fixes from a tester's 5.4.0 review, checked against the local model.

  • Send held files to the folder they came closest to. When two or more files in Organize are held for review and all came closest to the same Smart Folder, the uncategorized bar names it and offers one button ("Send N to "). It only assigns the folder; nothing moves until the user moves the files. A file whose closest folder only ties the next one (within the engine's 0.03 tie margin) is left out of the offer. The 0.55 routing bar is unchanged.
  • Match scores read as words. Review cards and the sample run say "Strong match" (at or above the auto-organize default, 75%), "Good match" (at or above the routing bar, 55%) or "Check this". The percentage is the tooltip. A bare percentage read as an accuracy rate.
  • "Ask about your files" after a move opens Chat from the finished screen.
  • MCP setup for other apps: a "Copy address and token (other apps)" button for clients that take a server form rather than a config file. Documented in docs/MCP_SERVER.md.
  • "Watch smart folders" is now "Keep Smart Folders up to date", and its description says it watches destinations, not inputs.
  • Renaming is easier to find: the Discover button says how files will be named ("File names: Subject, then date"), and both naming pickers list conventions in words (one shared label map in validationConstants).

Local-model check

New manual spec test/e2e/manual/local-routing-review.spec.js (opt-in, never in CI) runs synthetic Search Console exports and unrelated files through the local model and reports folder, score, hold and closest folder for several folder descriptions. Findings that shaped this PR:

  • With the local model the bulk offer first proposed sending two exports to an unrelated folder that led their own by 1 to 5 points; the tie guard came from that.
  • A folder description present before analysis gave the best routing (10 of 11 correct in the last run).
  • Exports named after the site (Search Console's own naming) were held while a same-content file with a plain name routed. Matching against files already filed in a folder is the follow-up.

Testing

  • npm run ci equivalent run locally on Windows (format, lint, both typechecks, audits, compliance, coverage with thresholds, every verify step, knip, build): all passed.
  • New and updated unit tests for each change; the manual local-model spec run three times.

- Held files that all came closest to one Smart Folder can be sent there
  in one click from the uncategorized bar. The routing bar is unchanged.
- Match scores read as words (Strong match, Good match, Check this) on
  review cards and in the sample run; the percentage is the tooltip. The
  words follow the auto-organize default and the routing bar.
- The finished screen offers "Ask about your files", which opens Chat.
- MCP settings can copy the server address and token for apps that take
  a server form rather than a config file.
- "Watch smart folders" is now "Keep Smart Folders up to date", and says
  it watches where files go, not where they come from.
- The Discover naming button says how files will be named, and the
  naming pickers list conventions in words.
- Adds a manual local-model e2e review of small Search Console exports
  (test/e2e/manual/local-routing-review.spec.js).
With the local model, held Search Console exports came closest to an
unrelated folder by 1 to 5 points, and the bar offered to send them all
there. A file now counts toward the offer only when its closest folder
leads the next by the engine's tie margin (0.03). Engine entries carry
the closest and runner-up scores for this.

The manual local routing review gains a same-content control with a
plain name, a 1,000-row export, and the scoring method per file.
@iLevyTate
iLevyTate merged commit a41c2dc into main Nov 18, 2026
8 checks passed
@iLevyTate
iLevyTate deleted the feat/retest-quick-wins branch November 18, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant