Squashed history of PR #4892 (pr-4784-fix). Makes spaces the primary
navigation and working surface, on the "associations bind at creation
time only" model.
Model
- Issue <-> space is the only enforced ownership (per-space numbering).
Parent/child and project<->space associations only seed defaults at
creation; cross-space/child and project-association validations are
removed.
- Moving an issue renumbers it and records the old identifier in
issue_identifier_alias; API/CLI lookups and GitHub branch/PR
auto-linking fall back to the alias, so old identifiers resolve forever.
- Membership drives only the sidebar and personal defaults — never
access. Anyone can configure any space's member set wholesale
(PUT /api/spaces/{id}/members); saving an empty set archives the
space behind a confirm.
- Per-user space order (workspace_space_member.sort_order, fractional):
drag-sorted sidebar, "my first space" is the personal issue-creation
default; the workspace default space backs headless creation
(agents/CLI/Slack) and system placement.
Surfaces
- Sidebar: joined-spaces section (drag reorder, row -> space page,
per-group persisted collapse), Workspace group with a More menu,
Settings demoted to a footer icon.
- /space/:key/{issues,projects,autopilots,settings} — space surfaces
reuse shared page components; a routed /space/new create page
(replacing the earlier create-space modal), reserved key "NEW" so it
can never collide with a real space's /space/:key detail page.
- Issue detail moves to /issue/:id (identifier-first, Linear-style; old
/issues/:id redirects); create dialogs lead with a required space pill.
- Agent runtime brief now carries Space context (id/key/name) through
the daemon claim -> TaskContextForEnv -> prompt pipeline, with a
"## Space Context" section and --space on issue create/update in both
brief renderers, matching Project's existing treatment.
- zh-Hans: Space translated to 空间 across locales and conventions.zh.mdx.
Fixes along the way
- Cache membership judgment gains the space dimension + space_changed
WS flag.
- Silent skip on default-space lookup during invite acceptance is now a
hard failure (no space-less members).
- Backfilled space_id into ~28 raw-SQL Go test fixtures across
internal/handler and cmd/server that predated migration 132's NOT
NULL cutover.
- Fixed a resolve-loop bug in the IssueDetail identifier wrapper (mount/
unmount cycle on resolution failure) and gave it its own loading
skeleton instead of a blank screen while resolving.
- reserved-slugs generator's stale hardcoded doc-comment example synced
back to /create-space.
Verification
- go build ./..., go vet ./..., go test ./... all clean.
- pnpm typecheck (core/views/web/desktop) clean.
- packages/views: 162 files / 1656 tests passing.
- pnpm generate:reserved-slugs produces no diff.
Follow-ups tracked in docs/follow-ups/space-rollout.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Add comment trigger preview suppression
Co-authored-by: multica-agent <github@multica.ai>
* Use TanStack Query for trigger preview
Co-authored-by: multica-agent <github@multica.ai>
* Test note comments skip create triggers
Co-authored-by: multica-agent <github@multica.ai>
* feat(issues): redesign comment trigger chips as avatar chips
Single agent renders as avatar + presence dot + full sentence; several
agents collapse to an overlapping stack + active count, mirroring the
header working chip. Per-agent skip moves into a click-opened popover
(hover layers stay read-only tooltips); suppression reads as brightness,
not a ban glyph. Loading and preview errors render nothing.
Also: share one tooltip body across chip and popover rows, invalidate
cached previews after a comment lands (the enqueued task changes the
dedup answer), move the preview query key into issueKeys, and drop the
now-unconsumed status field from useCommentTriggerPreview.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* refactor(server): drop comment trigger wrappers kept only for tests
enqueueMentionedAgentTasks and shouldEnqueueSquadLeaderOnComment had no
production callers after the compute/enqueue split — the comment path
goes through computeCommentAgentTriggers. Tests now exercise the compute
functions directly via package-local helpers, so the legacy adapters
cannot drift from the real path.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(skills): sync mentioning/squads source maps with shared trigger computation
The squads source map still pointed the comment-trigger contract at the
pre-refactor call chain (comment.go:940 -> shouldEnqueueSquadLeaderOnComment),
and the mentioning skill referenced the deleted wrapper. Re-anchor both
to computeCommentAgentTriggers / computeAssignedSquadLeaderCommentTrigger
/ computeMentionedAgentCommentTriggers with current line numbers.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: multica-agent <github@multica.ai>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
