Polish Settings navigation and personal AI connection management

[Maneek21]

Settings mixed personal clients, workspace tools and service credentials, and the Claude Code setup could overflow on narrow screens. This consolidated change groups Settings by ownership, guides personal AI connection setup through four steps, and applies a consistent visual baseline across the Settings pages.

Includes the work from #324 and #325, preserving their commits. Existing URLs and backend authorization contracts remain intact. Apps has a searchable inventory and detail routes; Profile, Calendar and AI use sections that retain drafts. Connection management supports search, scoped activity, one-time token acknowledgement, retry states and explicit revoke confirmation. Mobile review fixes cover task templates, task rules, service keys and tags.

Security closeout updates Next.js to 16.3.3 and patched Tiptap, Hono, Sharp and js-yaml dependencies. Full pnpm audit now reports no known vulnerabilities. The earlier production-image job reached successful browser smoke and then failed its image scan; this candidate retains both gates.

Validation: fresh web typecheck, full web lint, three navigation tests, browser-smoke syntax and diff checks pass. Prior rendered review covered all 18 top-level Settings routes on desktop and mobile, including forms and narrower 320px tag layout. Updated CI exercises real personal-token creation, acknowledgement and revocation against a disposable database, plus the existing broader product smoke. Full final-candidate CI must pass before merge.

Limits: local visual review used fixtures. External OAuth, screen-reader acceptance, full role/persistence coverage and four employee detail routes remain follow-up work. Tracks B/C/D and Gate G remain open. No production fixture data or generated screenshots are included.

The author has reviewed the UI and authorized merge and deployment to demo.deft.ing after validation. Deploy with a stopped recovery backup, rehearsal of the supported database upgrade, preserved site configuration/feature flags, and post-deployment doctor, smoke and rendered checks. No new release tag is part of this closeout.

[Maneek21]

Merged and deployed to demo.deft.ing at 7c2e409. #324 is incorporated and #325 is closed as incorporated.

Final candidate and master CI/security are green, including production image scanning and real database-backed browser smoke. The separate deployment image was built from the exact merged SHA: https://github.com/Maneek21/Deft/actions/runs/34339934166. Public health/readiness, doctor and connector smoke pass after deployment. Authenticated live checks covered Settings, existing personal connections, Claude Code setup at 390px, Profile sections, App search/detail and existing Modules.

A stopped database/uploads/configuration backup and the previous image are retained on the host. No live schema migration was needed: the deployed and merged database contracts match after line-ending normalization. A restored copy passed doctor/smoke and its 146 table counts matched immediately after restore.

Operational findings: an initial on-host build caused a temporary memory-related outage; the final image was built off-host. A missing public readiness proxy route caused the first cutover to roll back; the site-specific Caddy route was fixed and the second cutover passed. The preview database has an existing uninitialized migration ledger that requires a separately reviewed repair before any future schema upgrade. Do not replay historic migrations on it. The checked-in demo proxy example also needs the readiness route in a follow-up ops change.

Previously documented external OAuth, screen-reader, role/persistence and employee detail-route gaps remain open, along with Tracks B/C/D and Gate G. No release tag or Settings schedule was created.