Bring Your Own Keys, Bring Your Own Settings

Added

• Bring your own keys per project — On any team project you can now set personal API keys, storage credentials, and .env.local-style secrets that only apply to your runs. Teammates use their own; nobody sees yours. The new Yours tab on the Secrets page is where these live.
• Personal storage default — Your /settings/Storage Default card now stores your S3/R2 credentials as personal defaults. They follow you across every team you're in and every project you work on, without leaking to teammates.
• Per-target overrides for your personal keys — The same per-target precision the project-shared editor has (one row per environment) now works on your personal Yours tab. Web app and API can use different values for the same key — yours, not the team's.
• Generic team-default secrets editor — /team-settings/secrets is a new catch-all editor for keys that don't have a dedicated card. Visible to everyone on the team, mutated by team owners and managers.
• Your settings follow you across teams — Theme, timezone, graph direction, dead-end visibility, and auto-update preferences now stick to you, not to whichever team you happen to be in. Switch scopes and your appearance stays put.
• Per-team personal overrides — New /team-settings/me page. Set your own automation defaults, model picks, and git preferences for a specific team without touching the team-wide defaults the rest of the team sees.
• Per-project personal overrides — New /projects/:id/settings/me page. Same idea, narrower scope: tune model picks or automation toggles for one project, just for your runs. Like a personal .env.local for that project.
• Promote and demote team managers — Team owners can turn members into managers, or demote managers back, directly from the Teams page on the website and the Members panel in the desktop app. Managers can invite members, change other members' roles, and manage team secrets — same access as owners except they can't transfer ownership or delete the team.
• Skills picker with live search — The skills selector searches the registry as you type, surfacing matches in real time so you don't scroll the whole list.

Changed

• Team defaults are starting points, not enforcement — For preferences (model picks, automation toggles, git settings), your personal override now wins over the team default for your runs. Previously the team value forced everyone, including you. Storage type, permissions, and a small set of policy fields stay team-binding — those still apply to everyone.
• Help Assistant is always available — The toggle to hide it is gone. If you don't want it, ignore it; the bottom-right speed dial doesn't get in the way.

Improved

• Secret resolution understands precedence — When a job runs, Trinity picks the right value automatically: your per-target override beats your project-wide override, which beats the project default, which beats your team-wide personal default, which beats the team default. You set things at whatever level makes sense; the cascade does the rest.
• Onboarding stores keys as yours by default — New project onboarding and existing-project import now save provider keys and .env values as personal-per-project. If you actually want to share with the team, switch to the Shared tab and re-save. Stops accidental "I just shared my Anthropic key with everyone."
• Cleaner storage credential handling on project create — When you create a new project under a team, your existing storage credentials apply via the cascade automatically. No more silent copying of the team's credentials into the new project's secret store.

Fixed

• Personal settings actually take effect when stories run — Model picks, automation toggles, git config, and other preferences you save on /team-settings/me and /projects/:id/settings/me now apply to your story runs. The team default was quietly winning even after you'd overridden it personally.
• Personal keys and storage credentials work in team scope — When you're working in a team, saving your provider keys (DeepSeek, Moonshot, Z.ai, Qwen, Anthropic) or personal S3/R2 storage credentials on the Settings page now lands them where stories you run in that team can pick them up. The AI Models setup chat also reflects your real provider config in the active scope.
• Identity preferences load on first boot — Theme, timezone, graph direction, and auto-update settings load on the first workspace fetch instead of showing defaults until you next save. Sign in on a new device and your theme is right immediately.
• Queue list shows the real phase during PR creation and merge — Stories that finished the agent pipeline used to keep saying "Documenter" through PR creation, merging, and conflict resolution. The queue now shows "Creating PR", "Merging", or "Resolving conflict" once agents are done.
• Your repos stay clean of Trinity files — Trinity's agent skills and quality-check files used to land inside your project repo and end up committed and pushed. They now live alongside your repo at the workspace level instead, so your git history stops filling with Trinity-internal scaffolding.
• Agents pick up their skills and hooks reliably — On every story run, agents now consistently find their full skill set, hooks, and quality-check rules at the workspace they're working in. No more silent gaps where a hook didn't fire or a skill wasn't available.
• Permission settings on secrets enforce everywhere — When Manage Secrets is set to Owner only, members can no longer change or reveal those values from any client. The team-default and team-wide secret editors are similarly locked to owners and managers.
• Managers cannot remove the team owner — A manager pressing Remove on the owner gets a clear "transfer ownership first" message instead of silently kicking them out. Owners exit the team only through ownership transfer.
• Onboarding dashboard refreshes when the first PRD lands — After onboarding finishes generating your initial PRD, the dashboard updates immediately instead of looking empty until you click refresh. The Architect and Align tabs also stay hidden while generation is in progress so you can't click into them mid-build.

Notes

• Auto-update from 0.2.1-beta installs this build in place; no reinstall needed.
• Existing project secrets keep their current behavior — they're shared with the team by default, just like before. The new tier sits underneath them as your personal fallback.
• If a team owner was relying on a team-set automation default applying to everyone (not just as a starting point), they'll want to communicate that to teammates — the cascade now lets each member override.