2026-10-09 ยท Personal Social Desk
An explicitly selected local visual tagging option and bounded metadata retries preserve existing media filenames and delivery receipts.
What changed
- Adds an optional local visual tagging backend for an explicitly selected, already installed model. Provider failures do not switch providers, download models or enable a paid fallback.
- Retains the existing free-only OpenRouter option and its saved rate-limit hold independently of the local provider.
- Uses bounded image previews or representative video frames, request deadlines and validated descriptive output for visual tags and folder suggestions.
- Adds an explicit metadata-only retry for one idle processed file in a batch that opted in to visual tagging, with three total attempts and durable request receipts.
- Preserves original and processed media, effective filenames, selected destination, conversion and cloud attempt counts, and existing Drive receipts during tagging retries.
- Keeps uncertain Drive uploads on their existing file identity so a later retry can reconcile saved copies without renaming or reconverting them.
- Shows the selected tagging provider and whether previews remain local or are sent to the configured remote provider. Saved tags remain searchable in the existing media library.
- Uses current Drive pacing status for the connection banner so historical file failures do not falsely report an active rate limit after recovery. Individual file errors remain visible.
Verification
- The complete local application suite passed 1,112 tests with one platform-specific skip and no failures (1,113 total).
- Syntax checks passed for 237 JavaScript and 14 Python files. Feature preservation passed for nine views, 98 controls, 17 selectors, 184 routes and 266 required files.
- Independent review verified fixed loopback transport, installed local-model checks, separate provider cooldowns, strict output validation, durable retry receipts and unchanged effective filenames.
- A bounded synthetic local-model probe returned validated labels in approximately eight seconds. The installed application subsequently saved a title and five searchable tags through its media API, preserving both binaries, filenames, cloud state, receipts and prior tagging history.
- Independent review and 14 focused media-library tests verified that a recovered Drive connection clears the current rate-limit banner without discarding saved file errors or future cooldowns.
- The target Linux deployment passed all 1,113 application tests, 20 scanner tests and seven Python checks. The reviewed source archive was installed with a rollback backup.
- All nine main application views rendered without browser console errors. Saved local tags were found through the media-library search and remained present after reload; the current Drive connection banner no longer reports historical rate limits as active.
- A controlled upload completed with independently verified original and processed Drive receipts. The unfinished import was resumed with its original job identity and options; broader backfill remains in progress.
Rollout
Installed and verified on the owner-controlled production instance. Local visual tagging and the current Drive-status banner are live. A saved tagging retry, browser search, reload persistence and both copies of a controlled Drive transfer were verified. The existing import has resumed; its broader media backfill is not yet complete. Revision 2026.10.09.001 was superseded before installation and remains available in the release history.
Updating
- Install only the reviewed Personal Social Desk release and preserve existing private configuration, media, import history and delivery receipts.
- Select the local provider explicitly only after confirming the approved model is already installed and available. Existing OpenRouter settings and cooldown history remain intact.
- Retry an existing eligible file with its saved identity and a stable request ID. Resume an unfinished import rather than creating a replacement job.
- Refresh the application after installation and verify the provider disclosure, saved tags and retained filenames before continuing broader processing.
Scope and limitations
- Visual descriptions and folder labels are suggestions and can be inaccurate. They do not establish identity, ownership, authenticity or unseen events, and they do not move files or publish content.
- Local tagging requires an available compatible model and sufficient resources. Unavailable, timed-out or invalid results remain untagged; there is no automatic provider switch or paid fallback.
- Tagging retries do not reset exhausted Drive attempts, clear provider cooldowns or guarantee cloud delivery. Both original and processed Drive copies still require verified receipts.
- An import marked complete confirms staging, not completed conversion or cloud delivery. The resumed backfill is still in progress. Historical files with exhausted cloud attempts retain their individual errors for explicit review.
- Developer and copyright credit: MatthewxMurphy.com. Release owner: CreatorPublishingHub.com. This update retains private source and owner-controlled distribution.