Bugfix/workspace file upload and csv encoding

[Xeelee33]

Summary

• Added shared CSV decoding with UTF-8, UTF-8 BOM, Windows-1252, and Latin-1 fallbacks so ANSI-encoded uploads preserve their content during metadata extraction, indexing, citations, and tabular queries.
• Improved tabular analysis recovery by detecting repeated equivalent tool failures and routing subsequent model attempts toward a different query path instead of repeating the same failing call.
• Added visible retry lifecycle reporting and server-side diagnostics for repeated tabular tool failures.
• Fixed group workspace chat uploads so workspace owners are recognized correctly.

Linked issue

No associated GitHub issue.

Release Notes & Latest Features

• New Feature
• Bug Fix
• UI Enhancement
• Breaking Change
• Internal only

Is this visible to end users?

• Yes
• No

Is this admin-facing (Admin Settings, governance, deployment, config)?

• Yes
• No

Should this become a Latest Feature card?

• Yes
• No
• Already added

Screenshot needed for the card?

• Yes
• No
• Attached

Version bump

config.py remains at 0.261.030 because the version was already updated in a prior commit included in this PR.

• config.py version is already updated for this PR; no additional bump is needed
• version.txt not needed because deployers was not changed

Testing / validation

• python -m py_compile passed for all changed Python files.
• python scripts/check_swagger_routes.py passed for all changed route files.
• Route policy tests passed: 12 passed.
• Focused functional tests passed:
  • test_tabular_csv_ansi_encoding.py
  • test_chat_upload_group_workspace_handoff.py
• python check_xss_sinks.py --full-file passed for all changed application Python files.
• git diff --check passed.
• The broken-access-control scan reported one pre-existing finding in route_backend_chats.py:3806; the line is unchanged relative to origin/Development.
• Tested re-uploading a previously failing .csv file with ANSI encoding/characters and was able to successfully prompt against it.
• Tested dropping a file into a chat window with the conversation set to a group workspace context as an Admin, Document Manager, and User. Admin and Document Manager could add the file properly, User was unable to add the file.

Documentation

• Release notes updated under v0.261.030
• Feature documentation updated, not needed
• Fix documentation updated

Security checklist

• New Flask routes include @swagger_route(security=get_auth_security()); no new Flask routes were added
• Settings sent to non-admin frontends use sanitize_settings_for_user(); no new settings payloads were added
• Browser JavaScript is served from local SimpleChat static assets only; no browser JavaScript changes were included
• No secrets, keys, connection strings, or local-only artifacts are included

[Paul Lizer (paullizer)]

nice! thank you for the update!