* chore: remove legacy orchestrator, trading and one-off script leftovers The repository still carried the pre-evOo prototype: a Python orchestrator, the old HTML "evoo-platform" cockpit (whose test ran in the root unit suite), an apex-trading package, the hot-reload deploy.sh for it, a permissions manifest, an architecture note with local file links, agent handoff notes, a Steve Jobs persona template and about ninety one-off scripts that probe a developer database with hard-coded local URLs. None of it is used by the product, CI or the real deploy in ops/evo-deploy. Delete those files, drop the evoo-platform test glob from the root vitest config, the Cockpit section from .env.example and the dead biome and gitignore entries, and update the docs that listed the removed tools. scripts/start-tmux.sh no longer starts the removed sentinel and resolves the checkout from its own location instead of a machine-specific path; scripts/seed-ollama.ts requires DATABASE_URL instead of falling back to a local URL with a username. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * fix(web): drop trading and persona prompts from the conversation shell The web shell still showed leftovers from the trading prototype: composer chips with German trading and "Steve Jobs" prompts, trading suggestion chips under the empty conversation line, a German trading hero for the empty transcript, and a German "data protection" status panel in the sidebar. They suggested actions the product does not have and added persistent chrome. Remove the composer chips and their helper, the empty-state chips and the hero (the empty conversation keeps its existing one-line start hint), the sidebar trading indicator and the data trust panel. The new-bot E2E now asserts the plain empty state; the sidebar spec no longer expects the trading status, and the placeholder Steve Jobs spec with no assertions is gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * refactor: remove the trading bot status integration With the sidebar trading indicator gone, the only remaining consumer of the trading bot status was a banner in General settings that reused the same component. evOo is a personal assistant; a status proxy and poller for one external trading service, configured through service-specific TRADING_BOT_URL and VITE_TRADING_BOT_URL variables, does not belong in the core product. Remove the settings banner and its prop plumbing, the web poller, the indicator component, the /api/trading-bot/status proxy, the shared core contract, the env loading and both variables from .env.example, together with their tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * chore: remove one-off database scripts and a stale review note packages/db carried four hand-run scripts outside the package build that query or seed a developer database with a hard-coded connection string, one of them for a specific account. docs/VOICE-FIRST-REVIEW.md was a one-time verification note for a workflow that no longer exists and named private machines and local paths. Nothing references them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(memory): remember appends dated notes instead of replacing memory The remember tool rewrote the bot's whole MEMORY.md with each call, so every new fact erased the earlier ones unless the model re-sent the full document. - MemoryCommitRequest gains mode "append" (the store joins the note onto the current content inside the same serializable transaction and still writes a revision row) and every commit is capped at 16 KB per document. - remember appends a dated bullet ("- YYYY-MM-DD: ...", the user's local date) by default and rewrites only with mode "replace"; a full document returns an error that tells the bot to condense it. Retries of the same tool call stay single appends through the existing effect record. - Scripted runtime memory entries can append too; the scripted "remember" script now appends instead of overwriting the bot's memory. - When memory does not fit the run's 32 KB budget, the prompt keeps a document's newest lines instead of its oldest. - memory.update maps an oversized save to BAD_REQUEST. - docs/PRODUCT.md records that UserFact is the cross-space user model and the space MEMORY.md stays space notes (no migration). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(coach): goals, habits, check-ins, daily briefs and check-in rhythm The main agent should coach the user, but nothing stored what the user wants to achieve or keep doing, and no routine ever checked in. This adds the data model and the interfaces the onboarding intake and the coach tools build on. - Schema: UserGoal, Habit, CheckIn (one per habit, goal or day and date) and DailyBrief, all keyed to the user's local calendar date, plus a coachKey on Routine that marks the main bot's coach check-ins. - Contracts (coach.ts): CoachRhythm, Goal, Habit, CheckIn, DailyBrief and CoachToday DTOs and the RPC inputs. - Repository (@rakazo/db coach.ts): goal, habit and check-in CRUD with per-user limits, upsertDailyBrief and loadCoachToday with streaks in the user's time zone. - coach-rhythm.ts: setCoachRhythm/getCoachRhythm keep up to three main bot routines (morning brief, evening check-in, weekly review) in the main conversation in step with the user's chosen times. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(notifications): add push subscriptions, notification settings and web push interfaces Push could only reach one mobile device per user (a token file), quiet hours did not exist, and the web app had no service worker, so a closed tab never heard about finished work. This lands the shared interfaces first so onboarding can build on them: - push_subscriptions (web push endpoints and Expo tokens, one row per device) and user_notification_settings (quiet hours as minutes in the profile time zone, nudges, a per-day nudge counter), with CHECK constraints. - NotificationSettingsSchema and web push contracts, notifications.settings.get/update and notifications.webPush.config/subscribe/unsubscribe (owner-scoped, https endpoints only). - getNotificationSettings/updateNotificationSettings plus the policy and nudge-cap helpers. - VAPID keys from VAPID_PUBLIC_KEY/VAPID_PRIVATE_KEY or generated once and stored encrypted, and an SSRF-guarded web push sender built on the web-push package. - The web app links its manifest, registers a push-only service worker where supported (secure context, not the desktop app) and exposes webPushSupported/webPushEnabled/enableWebPush/ disableWebPush. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * chore: replace machine-specific paths and addresses with placeholders ORIGIN.md pinned the intended checkout to an absolute path under a personal home directory, docs/LOCAL-SETUP.md listed folders on one developer's machine, and two tests used what looks like a real tailnet address. Use a home-relative path, drop the machine-specific folder list, and use 100.100.100.100 in the tests; it is still inside 100.64.0.0/10, so both tests check the same thing as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(coach): repository, streak and rhythm suites Covers what the coach interfaces promise before anything builds on them: goal and habit ownership and limits, one check-in per habit, goal and day dated in the user's time zone, streaks across weekends and weeks, and a rhythm that keeps exactly one main-bot routine per check-in and is idempotent when set again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * refactor(contracts): share one clock-time schema The coach rhythm and the quiet hours both parse "HH:MM" wall-clock times and each defined its own ClockTimeSchema, which the contracts index cannot export twice. Both now import it from one module. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(onboarding): ask the onboarding questions in the main conversation The wizard asked for the account name again and a "Tell us about yourself" form, and the focus answer in the main conversation was never saved. The main bot now gets to know the user in the main conversation instead, one card after each answer. - UserOnboarding keeps the pending step, the focus and when onboarding finished. - onboarding-intake.ts declares the steps (focus, goal, rhythm, quiet hours, notifications) as cards plus what their answers change; onboarding.ts commits an answer, the focus app suggestions and the next card or the closing line in one transaction. - The choice block gains a step, an optional text input and the typed answer; choose takes the step, the text and whether the device can still turn push on. - The focus answer becomes a goals fact; the goal, rhythm and quiet-hours effects and the push seam are placeholders until the coach and notification modules are merged. - The wizard drops the preferences step and fills time zone, locale and language from the browser; the main bot's prompt notes open onboarding cards; agent history shows a card's question and answer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(notifications): fan push out to every device, honour quiet hours, add notify_user Run notifications reached at most one phone and nothing could hold them back at night. - PushNotificationProvider sends each notification to all of the user's registered devices (web push and Expo), skips everything during quiet hours in the profile time zone, drops devices the push service reports gone (404/410, DeviceNotRegistered), records lastUsedAt and links each push to its conversation. - Expo tokens move from DATA_DIR/push-tokens files into push_subscriptions: the API imports and deletes the legacy files at start; notifications.registerPush/unregisterPush keep their contract for the mobile app (tokens must look like Expo tokens). - NotificationMessage gains the nudge kind, and the main bot gets notify_user: a short push to the main conversation that respects the nudge switch, quiet hours and a cap of three per day. It is withheld from shared messaging channels and from runs answering another owner's agent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(coach): main-bot coach tools and goals in its prompt The main agent had no way to record what the user wants to achieve or how their day went, and its prompt never showed their goals or habits. - update_goal, update_habit, log_check_in and write_daily_brief, main-bot only and, like update_user_profile, withheld from shared channels and from runs that answer another owner's agent. Goals and habits can be named by id or exact title. - The main bot's own runs list active goals and habits (with ids, done state and streak) in the <user> block; the basics-only block and every other bot never see them. The main agent role adds a short coaching stance and names each coach tool only when the run has it, so the check-in routine prompts stay tool-agnostic. - The scripted runtime understands a few coach commands and the morning check-in, so tests can drive the tools end to end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * fix(web): use English Lingui sources for German UI text Several web surfaces hard-coded German (the project card, roster and activity status labels, the sidebar "Heute" label) or used German text as the Lingui source message (sidebar sections, project timeline, bot picker, voice entry, group stage, copy and read-aloud buttons). English users saw German, and because production builds keep only message ids, none of these strings could be translated per locale. Convert them to English source messages, keeping the meaning: - ProjectCreatedCard: Lingui Trans/Plural instead of literals. - agent-activity: labels go through i18n._ with literal ids so the module stays importable from plain unit tests; the extractor still collects them. - Shell, ProjectSessionTimeline, bot-picker, StageVoiceEntry, OoStage: English sources, reusing existing messages where one already fit ("just now", "{n}m ago", "Search", "No bots match", "Set up voice", "Group conversation", "Transcript"). - The conversation picker matches its create entry against the translated label instead of a fixed German string. The German wording returns through the de catalog in the next commit. Unit and E2E tests now assert the English labels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(web): keep Lingui catalogs complete and in sync The committed catalogs were last extracted weeks ago: about 330 source messages were missing from every locale, and production builds keep only message ids, so those strings rendered as hash ids (sidebar sections, privacy settings, profile, timeline, ...). German also had 226 empty entries, and every extraction rewrote the files because references carried line numbers. - lingui.config.ts: po references without line numbers, and a stable sort that breaks Lingui's ordering ties (explicit ids, equal text) by id, so the output no longer depends on file-system order. - Re-extract all catalogs with --clean (drops 25-44 obsolete entries per locale; no existing translation changed). - Translate every German entry (du form, consistent with the existing catalog). Other locales keep empty entries and fall back to English. - i18n-catalog-sync.test.ts extracts into a copy of the catalogs and fails when the committed files differ or a German entry is empty, so stale catalogs fail the unit test job (offline, about 5 s). Adds @lingui/format-po (already installed through @lingui/cli) as a direct dev dependency to configure the formatter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * refactor(memory): derive the run's memory budget from the document limit The prompt budget was a separate 32 KB constant; it is now twice the per-document limit, so a full bot document and a full space document keep fitting if either number changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(profile): edit facts in place in About you About you could only confirm or delete what the bots know about the user, so a fact that was slightly wrong or filed under the wrong category had to be deleted and taught again, and a fact could not be limited to some spaces from the app even though the profile supports it. - Each fact gets an Edit button that turns its row into an inline editor: wording, category, and (when the user has more than one space, or the fact is already limited) which spaces it shows in. Escape or Cancel leaves it unchanged; only changed fields are sent through profile.update editFacts. - A limited fact names its spaces next to its source. - The repository validates edits like new facts: a wording whose normalized form is empty or equals another fact of the user is refused, all edits of one update apply atomically, and the stored embedding is only dropped when the wording really changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(inbox): list and answer items from all of the user's spaces The inbox in the main conversation only showed asks, approvals, takeovers and unread threads of the current space. The main conversation lives in the home space, so anything a bot needed in a project space never reached it. - inbox.list now covers every space the user belongs to (except spaces being deleted), still only the user's own bots, runs and threads. Items from another space carry that space's id and name. - The web inbox shows the space name next to the bot for those items, answers them with that space's header so the existing thread procedures check membership and ownership for that space, and opens their thread in it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(coach): coach RPCs for goals, habits, check-ins, today and rhythm The web app needs to show and change the user's coach data, and the check-in times need a way to change after onboarding. - coach.today, coach.goals.*, coach.habits.*, coach.checkIns.* and coach.rhythm.get/set, owner-only and not space-scoped; another user's ids read as not found, invalid input as a bad request. - coach-rhythm reuses the shared clock-time helpers. - Tests: an API suite covering ownership and validation for every procedure, the coach tools driven through the main bot (and refused for a specialist), and a morning check-in routine that fires in the main conversation and writes today's brief; the unauthenticated authorization sweep lists the new procedures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(onboarding): save goal, check-in rhythm, quiet hours and push from the cards With the coach and notification modules merged, the onboarding answers now take effect: - the goal card creates a goal (source onboarding) through createGoal; - the rhythm card sets the main bot's check-in routines through setCoachRhythm, and the closing line names the first check-in from the routines that were saved; - the quiet-hours card updates the notification settings; - the choice card tells the server whether this browser can still turn push on, so the notifications card is offered only there, and "Turn on" subscribes before answering. The thread lock becomes NO KEY UPDATE so a rhythm routine, which references the thread, can be written while the answer holds the lock. The goal answer is capped at the coach title length. A Postgres suite walks the questions end to end: answers, skips, a dismissed card, a stale and a doubled answer, another bot's focus card, and another user's access. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(notifications): cover quiet hours, delivery, nudges and the notification RPCs The quiet-hours CHECK accepted a row with only one bound set, because a NULL comparison made the whole condition NULL; it now requires both bounds explicitly. The migration has not shipped yet, so it is corrected in place. - Unit: quiet-hours math across midnight, time zones and daylight saving; VAPID key handling (configured, generated once and shared, invalid); the web push sender (encrypted VAPID-signed request, gone on 404/410, no private or non-https endpoints); the fan-out with fake senders. - PostgreSQL: settings and subscription repositories (constraints, per-user removal, endpoint hand-over, device cap, concurrent nudge cap, cascade on account deletion), delivery and notify_user against a real main conversation, and every notification RPC through the API including cross-user isolation and endpoint validation. - .env.example documents the optional VAPID keys and VAPID_SUBJECT. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(web): notification settings, and sign-out stops this browser's push Users had no way to turn on push for a browser, set quiet hours or opt out of nudges. Settings gains a compact Notifications section: a switch for push on this device (only where web push works: a secure context outside the desktop app), quiet hours with from/to times (22:00-07:00 when first turned on) and a switch for nudges. Changes save in order as they are made. A browser that blocked notifications says so instead of offering a dead switch. Logging out unregisters the browser first, so a shared computer stops receiving the account's pushes. The E2E stubs the Push API (headless Chromium has no push service), walks all three controls, checks they survive a reload and captures the notification-settings screenshot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * fix(profile): keep the fact editor's Save label visible Small buttons in ui-web merge their text-ui-label size over the default variant's text color, so the small Save button rendered ink on ink. The editor now uses default-size controls, with the category select at the same height. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * refactor(notifications): keep the push sender contract next to the fan-out The payload, target and outcome types are shared by the Expo and web push senders, so they now live with PushSender in push-notifications.ts instead of in the web push adapter. The settings E2E also stubs the Notification permission (headless Chromium reports it as denied even when granted), and the quiet-hours inputs are wide enough for 12-hour times. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * fix(core): load child_process normally in the git checkout reader readGitCheckout loaded node:child_process through require(), which does not exist in the ESM API runtime. Linking a project space to a folder that is a git checkout therefore failed after the space was created. The lazy load is no longer needed: the reader is only reachable through the server-only "@rakazo/core/git-checkout" subpath, never through the package entry the web app bundles. Import spawn at the top instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(onboarding): ask before discovering projects and let the user choose The onboarding scan started on its own, discarded what it found, claimed to read email and calendars, simulated progress for everyone who could not scan, and its project creation always failed (wrong Space fields and a space lookup by title across tenants). Discovery now asks first and creates nothing without a choice: - The scan step appears only for the deployment owner when ONBOARDING_SCAN_HOME is set; everyone else skips it. The simulated scan is gone. - It shows the folder and asks. Only directory listings are read: git projects up to four levels deep, their languages and a few tools (Docker, GitHub Actions, Terraform). Symlinks are never followed and each chosen folder is resolved again before use, so nothing outside the folder is reached. Results stay with the account that scanned. - Found projects are a checklist (none preselected); found languages and tools are facts (preselected). "Add" creates one project space per chosen project with createSpaceForMember and wireProjectWorkspace in the user's own organization, reusing the user's own space already linked to that folder, and saves the chosen facts as onboarding facts under the profile lock and fact limit. - When a connection becomes connected (direct connect, authorization round trip, or catalog reconciliation), "Uses <App>" is remembered as a tools fact from the connector. Revoking keeps it. The E2E harness now points ONBOARDING_SCAN_HOME at a fixture folder and starts without a deployment owner, so owner-only onboarding steps appear only in specs that take the seat through /__e2e/deployment-owner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(web): coach on the Heute page Heute only listed runs and linked to a hard-coded local Mission Control address, so the coach's work had nowhere to show. - Today's brief at the top, habits with a check-off and their streak, and active goals, each only when there is something to show; then the existing needs-you, doing and done lists. - One icon button opens the check-in times (morning, evening, weekly), loaded when opened and saved on every change. - The page reads coach.today, refreshes it when a run finishes or the tab becomes visible, and checks habits off optimistically; the date header uses the user's time zone from the profile. - Removes the Mission Control link and its constant. - Tests: helper unit tests and a web E2E that writes the brief through the main bot, checks a habit off across a reload and sets check-in times (screenshots heute-coach and heute-rhythm). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(onboarding): walk the onboarding questions end to end; mobile reads cards as text - onboarding-intake.spec walks focus, goal (after typing into the composer, which still works), check-ins, quiet hours and the notifications card when the browser offers it, with the onboarding-intake-goal, -rhythm and -done screenshots. - completeOnboarding and the wizard specs drop the preferences step; the scan step is optional (skipped when it asks, otherwise it advances by itself). - The user-profile spec now checks the browser-filled profile and the focus fact; the conversation spec checks the shorter app suggestion and the following goal question. - The hover spec measures a reply that fills its row (a bot row's rail sits at the row's end, so the old long onboarding line was what made it pass) and scopes Send to the composer, since an open goal card has its own. - Mobile shows a choice card as its question and answer instead of an empty bubble. - The focus options drop their unused summary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(web): stub the Notification permission without a static-only class Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(web): find the sidebar Today button by its English label The shell contrast test added on main looks up the sidebar button by the old German source text, which this branch replaces with "Today". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * feat(onboarding): show the onboarding cards and check-in names in the user's language The onboarding cards, the closing line and the coach routine names were English server text for every user. The server keeps the state and an English fallback; the web now words them through Lingui, so there is one translation source. - Choice cards: the web says the question, the option labels and the placeholder from the step and option ids, and keeps the server text for anything it does not know (quiet-hour ranges are already written in the user's locale). Another bot's focus card is recognized by its option ids. Mobile and agent history keep the server text. - The "Got it. … are a good place to start." line is gone: the app cards speak for themselves, and with no cards nothing is said. - The closing line becomes an intake_note block (note "done", nextCheckInAt, English text). The web words it with the first check-in in the user's clock; mobile blockText and blocksToAgentHistoryText read its text through their generic fallback. - Routines carry coachKey. The routine list and editor show a check-in under its label in the UI language until the user renames it; saving an untouched label keeps the stored name. The English names move to contracts (COACH_ROUTINE_NAMES); prompts stay English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * style: use top-level type imports in the coach changes AGENTS.md asks for top-level `import type` instead of inline `type` specifiers; this applies it to the import statements the coach work added or changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * chore(web): extract catalogs and translate the coach strings to German Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(web): look for the bot reply in the transcript only The main conversation's sidebar row now previews the latest reply, so the unscoped text lookup matched the sidebar too and failed in strict mode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(web): drop the trading status from the shell contrast test main's contrast test now waits for the sidebar trading status before measuring; this branch removes that status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(onboarding): link the foreign folder while its tenant owns the deployment Since #112 only the deployment owner can link a host folder, so the discovery test creates the other tenant's linked space while that tenant holds the deployment, then hands the deployment to the scanning owner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * chore(web): extract catalogs and translate the in-app browser strings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test: look up the home main conversation in the scheduling journey Since every project has its own main conversation, the journey that schedules for a specialist found the user's main conversation with findFirst over all of them. With the Lab project's conversation also matching, it picked either one, so the check failed about one run in three. The lookup now names the home space, where the specialist joined and the routine is created. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test: expect the home main conversation's ask in another space's inbox Every project now has a main conversation of its own, so an ask waiting in the home main conversation is not visible from a project and its inbox lists it, answered in the home space. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * fix(coach): move check-ins when the user's time zone changes The coach check-ins are main-bot routines scheduled in the profile time zone, but a later zone change (About you, onboarding, the main bot's update_user_profile tool, or forgetting the whole profile) left them in the old zone until the rhythm was saved again, so they fired at the wrong local time. syncCoachTimeZone, next to the rhythm code, moves the main bot's coach routines that are not in the current profile zone into it, recomputes the next run of armed ones and re-arms their wakeup. Paused check-ins move but stay paused, routines the user made are never touched, users without check-ins get none, and a save that leaves the zone as it is changes nothing. The profile update and forget RPCs and the profile tool call it whenever they write the zone. Quiet hours, the daily nudge cap and coach dates are evaluated in the profile zone when they are used, so they need no migration. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * fix(web): word the main conversation preview in the user's language during onboarding While onboarding wrote the main conversation, its sidebar row, project rows and Heute showed the server preview: nothing for a pending card (a card has no text of its own, so the row fell back to "Ready") and the English fallback of the closing note, even for a German user. Groups now carry `previewBlock` next to `preview`: the latest message when it is an onboarding card or note, validated with the same block schemas the messages use (now named exports). The web words it with the helpers that render the card and the note, so no copy is duplicated: the question while a card waits, the answer once given, and the closing note in the user's language and clock. A dismissed card keeps the plain preview, as the conversation no longer shows it. The field is left out for every other message, and mobile keeps using the plain `preview`. The chosen-answer lookup moves from the card into onboarding-copy so the card and the preview share it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u * test(web): look for the focus question in the conversation, not the sidebar The main conversation's sidebar row now shows the pending intake question, so a page-wide text match finds it twice (strict mode) or never reaches zero. The specs mean the card in the open conversation, so they look there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u --------- Co-authored-by: Claude <noreply@anthropic.com>
435 lines
14 KiB
TypeScript
435 lines
14 KiB
TypeScript
// Onboarding discovery. With the deployment owner's consent, it lists the code projects (git
|
|
// checkouts) in the configured scan folder and the languages and tools they use. It reads
|
|
// directory listings only, never file contents, and never follows a symlink, so nothing outside
|
|
// the folder is reached. Results stay with the account that started the scan, and nothing is
|
|
// created until the owner picks projects and facts from them.
|
|
import { randomUUID } from "node:crypto";
|
|
import type { Dirent } from "node:fs";
|
|
import { readdir, realpath, stat } from "node:fs/promises";
|
|
import path from "node:path";
|
|
import { ORPCError } from "@orpc/server";
|
|
import type {
|
|
Actor,
|
|
OnboardingScanApplyInput,
|
|
OnboardingScanApplyResult,
|
|
OnboardingScanStatus,
|
|
UserFactCategory,
|
|
} from "@rakazo/contracts";
|
|
import { ONBOARDING_SCAN_MAX_FACTS, ONBOARDING_SCAN_MAX_PROJECTS } from "@rakazo/contracts";
|
|
import type { PrismaClient } from "@rakazo/db";
|
|
import {
|
|
createSpaceForMember,
|
|
ensureMainConversation,
|
|
InvalidProjectWorkspacePathError,
|
|
InvalidSpaceNameError,
|
|
InvalidUserFactError,
|
|
resolveProjectWorkspaceDirectory,
|
|
SpaceLimitError,
|
|
updateUserProfile,
|
|
wireProjectWorkspace,
|
|
} from "@rakazo/db";
|
|
|
|
/** Project roots are looked for at most this deep below the scan folder. */
|
|
const PROJECT_DEPTH = 4;
|
|
/** Bounds the walk of a large home folder. */
|
|
const MAX_DIRECTORIES = 5_000;
|
|
/** Bounds the language count inside one project. */
|
|
const MAX_FILES_PER_PROJECT = 5_000;
|
|
const MAX_FILE_DEPTH = 8;
|
|
const MAX_LANGUAGES_PER_PROJECT = 3;
|
|
const SCAN_TTL_MS = 60 * 60_000;
|
|
|
|
const SKIPPED_DIRECTORIES = new Set([
|
|
"node_modules",
|
|
"dist",
|
|
"build",
|
|
"out",
|
|
"target",
|
|
"vendor",
|
|
"venv",
|
|
"__pycache__",
|
|
"Library",
|
|
]);
|
|
|
|
const LANGUAGES = new Map<string, string>(
|
|
Object.entries({
|
|
ts: "TypeScript",
|
|
tsx: "TypeScript",
|
|
mts: "TypeScript",
|
|
cts: "TypeScript",
|
|
js: "JavaScript",
|
|
jsx: "JavaScript",
|
|
mjs: "JavaScript",
|
|
cjs: "JavaScript",
|
|
py: "Python",
|
|
go: "Go",
|
|
rs: "Rust",
|
|
java: "Java",
|
|
kt: "Kotlin",
|
|
kts: "Kotlin",
|
|
swift: "Swift",
|
|
rb: "Ruby",
|
|
php: "PHP",
|
|
c: "C",
|
|
h: "C",
|
|
cc: "C++",
|
|
cpp: "C++",
|
|
cxx: "C++",
|
|
hpp: "C++",
|
|
cs: "C#",
|
|
dart: "Dart",
|
|
ex: "Elixir",
|
|
exs: "Elixir",
|
|
scala: "Scala",
|
|
lua: "Lua",
|
|
}),
|
|
);
|
|
|
|
const COMPOSE_FILES = new Set([
|
|
"docker-compose.yml",
|
|
"docker-compose.yaml",
|
|
"compose.yml",
|
|
"compose.yaml",
|
|
]);
|
|
|
|
interface FoundProject {
|
|
id: string;
|
|
name: string;
|
|
/** Relative to the scan folder. */
|
|
path: string;
|
|
languages: string[];
|
|
tools: string[];
|
|
}
|
|
|
|
interface FoundFact {
|
|
id: string;
|
|
label: string;
|
|
category: UserFactCategory;
|
|
/** Stored as data for the user's bots, so it stays a plain English statement. */
|
|
value: string;
|
|
}
|
|
|
|
export interface OnboardingScanFindings {
|
|
projects: FoundProject[];
|
|
facts: FoundFact[];
|
|
}
|
|
|
|
interface ScanRecord extends OnboardingScanFindings {
|
|
id: string;
|
|
ownerUserId: string;
|
|
/** Real path of the scanned folder. */
|
|
home: string;
|
|
status: "scanning" | "complete" | "failed";
|
|
finishedAt: number | null;
|
|
applying: boolean;
|
|
}
|
|
|
|
/** Per API process; a scan only lives as long as the onboarding that started it. */
|
|
const scans = new Map<string, ScanRecord>();
|
|
|
|
/** Code-point order, so results do not depend on the server's locale. */
|
|
function compareText(left: string, right: string): number {
|
|
return left < right ? -1 : left > right ? 1 : 0;
|
|
}
|
|
|
|
/** Most frequent first, then by name. */
|
|
function byCount([leftName, left]: [string, number], [rightName, right]: [string, number]): number {
|
|
return right - left || compareText(leftName, rightName);
|
|
}
|
|
|
|
async function listDirectory(directory: string): Promise<Dirent[]> {
|
|
try {
|
|
return (await readdir(directory, { withFileTypes: true })).sort((left, right) =>
|
|
compareText(left.name, right.name),
|
|
);
|
|
} catch {
|
|
return [];
|
|
}
|
|
}
|
|
|
|
/** isDirectory() is false for a symlink, so links (and anything they point to) are never walked. */
|
|
function walkable(entry: Dirent): boolean {
|
|
return entry.isDirectory() && !entry.name.startsWith(".") && !SKIPPED_DIRECTORIES.has(entry.name);
|
|
}
|
|
|
|
async function findProjectRoots(home: string): Promise<string[]> {
|
|
const roots: string[] = [];
|
|
let visited = 0;
|
|
let level = [home];
|
|
// Breadth first, so shallow projects win when a limit is reached. The scan folder itself is
|
|
// never a project: a home folder tracked by git still holds the projects below it.
|
|
for (let depth = 0; depth <= PROJECT_DEPTH && level.length > 0; depth += 1) {
|
|
const next: string[] = [];
|
|
for (const directory of level) {
|
|
if (roots.length >= ONBOARDING_SCAN_MAX_PROJECTS || visited >= MAX_DIRECTORIES) return roots;
|
|
visited += 1;
|
|
const entries = await listDirectory(directory);
|
|
if (depth > 0 && entries.some((entry) => entry.name === ".git")) {
|
|
roots.push(directory);
|
|
continue;
|
|
}
|
|
for (const entry of entries) {
|
|
if (walkable(entry)) next.push(path.join(directory, entry.name));
|
|
}
|
|
}
|
|
level = next;
|
|
}
|
|
return roots;
|
|
}
|
|
|
|
async function analyzeProject(root: string): Promise<{ languages: string[]; tools: string[] }> {
|
|
const counts = new Map<string, number>();
|
|
const tools = new Set<string>();
|
|
let files = 0;
|
|
const rootEntries = await listDirectory(root);
|
|
if (rootEntries.some((entry) => entry.name === ".github" && entry.isDirectory())) {
|
|
const github = await listDirectory(path.join(root, ".github"));
|
|
if (github.some((entry) => entry.name === "workflows" && entry.isDirectory())) {
|
|
tools.add("GitHub Actions");
|
|
}
|
|
}
|
|
const visit = async (directory: string, depth: number, entries: Dirent[]): Promise<void> => {
|
|
for (const entry of entries) {
|
|
if (files >= MAX_FILES_PER_PROJECT) return;
|
|
if (entry.isFile()) {
|
|
files += 1;
|
|
const name = entry.name.toLowerCase();
|
|
const extension = name.includes(".") ? name.slice(name.lastIndexOf(".") + 1) : "";
|
|
const language = LANGUAGES.get(extension);
|
|
if (language) counts.set(language, (counts.get(language) ?? 0) + 1);
|
|
if (name === "dockerfile" || name.startsWith("dockerfile.") || COMPOSE_FILES.has(name)) {
|
|
tools.add("Docker");
|
|
}
|
|
if (extension === "tf") tools.add("Terraform");
|
|
} else if (depth < MAX_FILE_DEPTH && walkable(entry)) {
|
|
const child = path.join(directory, entry.name);
|
|
await visit(child, depth + 1, await listDirectory(child));
|
|
}
|
|
}
|
|
};
|
|
await visit(root, 0, rootEntries);
|
|
const total = [...counts.values()].reduce((sum, count) => sum + count, 0);
|
|
const languages = [...counts.entries()]
|
|
.filter(([, count]) => count >= total * 0.1)
|
|
.sort(byCount)
|
|
.slice(0, MAX_LANGUAGES_PER_PROJECT)
|
|
.map(([language]) => language);
|
|
return { languages, tools: [...tools].sort() };
|
|
}
|
|
|
|
/** Labels used by the most projects first, then by name. */
|
|
function rankLabels(lists: string[][]): string[] {
|
|
const counts = new Map<string, number>();
|
|
for (const list of lists)
|
|
for (const label of list) counts.set(label, (counts.get(label) ?? 0) + 1);
|
|
return [...counts.entries()].sort(byCount).map(([label]) => label);
|
|
}
|
|
|
|
/** Lists the projects below a real (symlink-free) folder path, and what they use. */
|
|
export async function discoverOnboardingScan(home: string): Promise<OnboardingScanFindings> {
|
|
const roots = await findProjectRoots(home);
|
|
const analyzed = await Promise.all(
|
|
roots.map(async (root) => ({ root, ...(await analyzeProject(root)) })),
|
|
);
|
|
const projects = analyzed
|
|
.map(({ root, languages, tools }) => ({
|
|
name: path.basename(root),
|
|
path: path.relative(home, root),
|
|
languages,
|
|
tools,
|
|
}))
|
|
.sort((left, right) => compareText(left.path, right.path))
|
|
.map((project, index) => ({ id: `project-${index}`, ...project }));
|
|
const facts: FoundFact[] = [
|
|
...rankLabels(projects.map((project) => project.languages)).map((label) => ({
|
|
id: `language:${label}`,
|
|
label,
|
|
category: "work" as const,
|
|
value: `Codes in ${label}`,
|
|
})),
|
|
...rankLabels(projects.map((project) => project.tools)).map((label) => ({
|
|
id: `tool:${label}`,
|
|
label,
|
|
category: "tools" as const,
|
|
value: `Uses ${label}`,
|
|
})),
|
|
].slice(0, ONBOARDING_SCAN_MAX_FACTS);
|
|
return { projects, facts };
|
|
}
|
|
|
|
/**
|
|
* The scan reads the server's filesystem, so only the deployment owner may scan, and only the
|
|
* folder the deployment configured. Null hides the step.
|
|
*/
|
|
export async function onboardingScanFolder(
|
|
actor: Pick<Actor, "isDeploymentOwner">,
|
|
scanHome: string | undefined,
|
|
): Promise<string | null> {
|
|
if (!actor.isDeploymentOwner || !scanHome) return null;
|
|
try {
|
|
const home = await realpath(scanHome);
|
|
return (await stat(home)).isDirectory() ? home : null;
|
|
} catch {
|
|
return null;
|
|
}
|
|
}
|
|
|
|
function forgetExpiredScans(now: number): void {
|
|
for (const [id, scan] of scans) {
|
|
if (scan.finishedAt !== null && now - scan.finishedAt > SCAN_TTL_MS) scans.delete(id);
|
|
}
|
|
}
|
|
|
|
export async function startOnboardingScan(
|
|
actor: Pick<Actor, "userId" | "isDeploymentOwner">,
|
|
scanHome: string | undefined,
|
|
): Promise<{ scanId: string }> {
|
|
const home = await onboardingScanFolder(actor, scanHome);
|
|
if (!home) throw new ORPCError("FORBIDDEN");
|
|
forgetExpiredScans(Date.now());
|
|
const running = [...scans.values()].find(
|
|
(scan) => scan.ownerUserId === actor.userId && scan.status === "scanning",
|
|
);
|
|
if (running) return { scanId: running.id };
|
|
const scan: ScanRecord = {
|
|
id: randomUUID(),
|
|
ownerUserId: actor.userId,
|
|
home,
|
|
status: "scanning",
|
|
projects: [],
|
|
facts: [],
|
|
finishedAt: null,
|
|
applying: false,
|
|
};
|
|
scans.set(scan.id, scan);
|
|
void discoverOnboardingScan(home)
|
|
.then((findings) => {
|
|
scan.projects = findings.projects;
|
|
scan.facts = findings.facts;
|
|
scan.status = "complete";
|
|
})
|
|
.catch(() => {
|
|
scan.status = "failed";
|
|
})
|
|
.finally(() => {
|
|
scan.finishedAt = Date.now();
|
|
});
|
|
return { scanId: scan.id };
|
|
}
|
|
|
|
/** Another account's scan reads as missing. */
|
|
function ownedScan(scanId: string, userId: string): ScanRecord {
|
|
const scan = scans.get(scanId);
|
|
if (!scan || scan.ownerUserId !== userId) throw new ORPCError("NOT_FOUND");
|
|
return scan;
|
|
}
|
|
|
|
export function onboardingScanStatus(scanId: string, userId: string): OnboardingScanStatus {
|
|
const scan = ownedScan(scanId, userId);
|
|
if (scan.status !== "complete") return { status: scan.status };
|
|
return {
|
|
status: "complete",
|
|
projects: scan.projects.map(({ id, name, path }) => ({ id, name, path })),
|
|
facts: scan.facts.map(({ id, label }) => ({ id, label })),
|
|
};
|
|
}
|
|
|
|
const MISSING_FOLDER = "That folder does not exist or is not readable.";
|
|
|
|
/** Resolves a found project again, so a folder swapped for a symlink cannot leave the scan folder. */
|
|
async function confinedProjectFolder(home: string, relative: string): Promise<string> {
|
|
const folder = await resolveProjectWorkspaceDirectory(path.join(home, relative));
|
|
const inside = path.relative(home, folder);
|
|
if (!inside || inside === ".." || inside.startsWith(`..${path.sep}`) || path.isAbsolute(inside)) {
|
|
throw new InvalidProjectWorkspacePathError(MISSING_FOLDER);
|
|
}
|
|
return folder;
|
|
}
|
|
|
|
async function projectSpace(
|
|
prisma: PrismaClient,
|
|
actor: Pick<Actor, "userId" | "spaceId">,
|
|
name: string,
|
|
folder: string,
|
|
): Promise<{ id: string; name: string }> {
|
|
// Applying twice, or onboarding again, reuses the user's own space linked to this folder.
|
|
const existing = await prisma.space.findFirst({
|
|
where: {
|
|
workspacePath: folder,
|
|
deletingAt: null,
|
|
memberships: { some: { userId: actor.userId } },
|
|
},
|
|
select: { id: true, name: true },
|
|
orderBy: { createdAt: "asc" },
|
|
});
|
|
if (existing) return existing;
|
|
const space = await createSpaceForMember(prisma, {
|
|
currentSpaceId: actor.spaceId,
|
|
userId: actor.userId,
|
|
name: name.slice(0, 60),
|
|
});
|
|
await wireProjectWorkspace(prisma, { spaceId: space.id, workspacePath: folder });
|
|
// Like any new project, it starts with its own main agent.
|
|
await ensureMainConversation(prisma, actor.userId, space.id);
|
|
return space;
|
|
}
|
|
|
|
function toRpcError(error: unknown): unknown {
|
|
if (
|
|
error instanceof SpaceLimitError ||
|
|
error instanceof InvalidSpaceNameError ||
|
|
error instanceof InvalidProjectWorkspacePathError ||
|
|
error instanceof InvalidUserFactError
|
|
) {
|
|
return new ORPCError("BAD_REQUEST", { message: error.message });
|
|
}
|
|
return error;
|
|
}
|
|
|
|
/** Creates a project space per chosen project and saves the chosen facts to the profile. */
|
|
export async function applyOnboardingScan(
|
|
prisma: PrismaClient,
|
|
actor: Pick<Actor, "userId" | "spaceId" | "isDeploymentOwner">,
|
|
scanHome: string | undefined,
|
|
input: OnboardingScanApplyInput,
|
|
): Promise<OnboardingScanApplyResult> {
|
|
const scan = ownedScan(input.scanId, actor.userId);
|
|
if (scan.status !== "complete" || scan.applying) throw new ORPCError("CONFLICT");
|
|
scan.applying = true;
|
|
try {
|
|
// Ownership or the configured folder can change after the scan; check again before writing.
|
|
if ((await onboardingScanFolder(actor, scanHome)) !== scan.home) {
|
|
throw new ORPCError("FORBIDDEN");
|
|
}
|
|
const projectIds = new Set(input.projectIds);
|
|
const factIds = new Set(input.factIds);
|
|
const projects = scan.projects.filter((project) => projectIds.has(project.id));
|
|
const facts = scan.facts.filter((fact) => factIds.has(fact.id));
|
|
// Every chosen folder is checked before anything is written.
|
|
const chosen = await Promise.all(
|
|
projects.map(async (project) => ({
|
|
name: project.name,
|
|
folder: await confinedProjectFolder(scan.home, project.path),
|
|
})),
|
|
);
|
|
const added =
|
|
facts.length > 0
|
|
? await updateUserProfile(prisma, actor.userId, {
|
|
addFacts: facts.map(({ category, value }) => ({
|
|
category,
|
|
value,
|
|
source: "onboarding" as const,
|
|
})),
|
|
})
|
|
: [];
|
|
const spaces: Array<{ id: string; name: string }> = [];
|
|
for (const { name, folder } of chosen)
|
|
spaces.push(await projectSpace(prisma, actor, name, folder));
|
|
return { spaces, factsAdded: added.filter((fact) => fact.created).length };
|
|
} catch (error) {
|
|
throw toRpcError(error);
|
|
} finally {
|
|
scan.applying = false;
|
|
}
|
|
}
|