docs: design activity project reclassification

- docs: plan activity project reclassification
- fix(parser): recognize generic GitHub worktrees
- feat(settings): manage worktree mappings by machine
- fix(db): preserve mapping origin during resync
- fix(db): retain mapping context during pre-copy
- feat(activity): add atomic project reclassification
- fix(db): unify scoped worktree mapping evaluation
- feat(api): expose project reclassification workflow
- fix(sync): preserve mapped project moves across mirrors
- fix(sync): retain source labels in identity snapshots
- fix(sync): qualify snapshot tombstones by project
- fix(sync): bound incremental identity reconciliation
- feat(settings): manage remote worktree mappings
- fix(settings): isolate mapping mutations by machine
- feat(activity): reclassify projects from breakdowns
- fix(activity): harden reclassification state transitions
- test(e2e): cover activity project reclassification
- fix(sidebar): align root totals across backends
- test(e2e): gate DuckDB reclassification
- test(e2e): allow isolated server ports
- fix(sync): preserve source project in identity snapshots
- fix(sync): complete mapped identity ingestion
- fix(sync): retain snapshots across empty reparses
- fix(sync): make identity ingestion atomic
- fix(sync): preserve source identity on reprocessing
- test(e2e): validate isolated server ports
- chore(frontend): pin merged kit-ui contracts
- fix(activity): polish reclassification UI review findings
- docs: document activity project reclassification
- docs: close out completed superpowers plans
- fix(sync): harden project snapshot upgrades
- fix(sync): preserve reparsed snapshots on upgrade

Author: wesm

.github/workflows/ci.yml

@@ -118,6 +118,7 @@ jobs:
         run: |
           bash scripts/install_test.sh
           bash scripts/retry_test.sh
+          bash scripts/e2e-server_test.sh
           bash scripts/check_desktop_release_health_test.sh
           bash scripts/check_desktop_release_health_from_event_test.sh
           bash desktop/scripts/test-repair-appimage-diricon.sh
@@ -362,3 +363,9 @@ jobs:
         env:
           E2E_PREBUILT_FIXTURE: /tmp/testfixture
           E2E_PREBUILT_SERVER: /tmp/agentsview
+
+      - name: Run DuckDB E2E tests
+        run: make e2e-duckdb
+        env:
+          E2E_PREBUILT_FIXTURE: /tmp/testfixture
+          E2E_PREBUILT_SERVER: /tmp/agentsview

Makefile

@@ -378,6 +378,7 @@ e2e:
 # Run focused Playwright smoke tests against duckdb serve.
 e2e-duckdb:
 	cd frontend && AGENTSVIEW_E2E_BACKEND=duckdb npx playwright test \
+		e2e/activity-project-reclassification.spec.ts \
 		e2e/duckdb-backend.spec.ts e2e/session-list.spec.ts --project=chromium
 
 # Vet

cmd/testfixture/main.go

@@ -12,6 +12,7 @@ import (
 
 	"go.kenn.io/agentsview/internal/db"
 	duckdbsync "go.kenn.io/agentsview/internal/duckdb"
+	"go.kenn.io/agentsview/internal/export"
 )
 
 type sessionSpec struct {
@@ -118,6 +119,12 @@ func main() {
 		log.Fatalf("creating recent-edits fixture: %v", err)
 	}
 
+	if err := createProjectReclassificationFixture(
+		database, base.Add(120*time.Hour),
+	); err != nil {
+		log.Fatalf("creating project-reclassification fixture: %v", err)
+	}
+
 	fmt.Printf("Fixture DB written to %s\n", *out)
 	if *duckDBOut != "" {
 		if err := writeDuckDBMirror(database, *duckDBOut); err != nil {
@@ -127,6 +134,80 @@ func main() {
 	}
 }
 
+func createProjectReclassificationFixture(
+	database *db.DB, start time.Time,
+) error {
+	const (
+		machine      = "remote-example-host"
+		project      = "wrong_branch_label"
+		worktreeRoot = "/srv/worktrees/github.com/example-org/sample-service/example-worktree"
+		model        = "claude-sonnet-4-20250514"
+	)
+	cwds := []struct {
+		suffix string
+		cwd    string
+	}{
+		{suffix: "root", cwd: worktreeRoot},
+		{suffix: "nested", cwd: worktreeRoot + "/cmd/server"},
+	}
+	ctx := context.Background()
+	for index, item := range cwds {
+		sessionID := "test-session-project-reclassification-" + item.suffix
+		startedAt := start.Add(time.Duration(index) * time.Hour)
+		endedAt := startedAt.Add(12 * time.Minute)
+		firstMessage := "Inspect the sample service worktree."
+		session := db.Session{
+			ID:               sessionID,
+			Project:          project,
+			Machine:          machine,
+			Agent:            "claude",
+			StartedAt:        new(startedAt.Format(time.RFC3339Nano)),
+			EndedAt:          new(endedAt.Format(time.RFC3339Nano)),
+			MessageCount:     2,
+			UserMessageCount: 1,
+			FirstMessage:     new(firstMessage),
+			Cwd:              item.cwd,
+		}
+		if err := database.UpsertSession(session); err != nil {
+			return fmt.Errorf(
+				"upserting project-reclassification session: %w", err,
+			)
+		}
+		if err := database.InsertMessages(generateMessages(
+			sessionID, session.MessageCount, startedAt, model,
+		)); err != nil {
+			return fmt.Errorf(
+				"inserting project-reclassification messages: %w", err,
+			)
+		}
+		if err := database.UpsertProjectIdentityObservation(
+			ctx,
+			export.ProjectIdentityObservation{
+				SessionID:            sessionID,
+				Project:              project,
+				Machine:              machine,
+				RootPath:             worktreeRoot,
+				RepositoryPath:       "/srv/worktrees/github.com/example-org/sample-service",
+				WorktreeName:         "example-worktree",
+				WorktreeRootPath:     worktreeRoot,
+				WorktreeRelationship: export.WorktreeLinked,
+				CheckoutState:        export.CheckoutBranch,
+				GitBranch:            "example-worktree",
+				ObservedAt:           startedAt,
+			},
+		); err != nil {
+			return fmt.Errorf(
+				"upserting project-reclassification identity: %w", err,
+			)
+		}
+		fmt.Printf(
+			"  %s: %d messages (project reclassification)\n",
+			sessionID, session.MessageCount,
+		)
+	}
+	return nil
+}
+
 func writeDuckDBMirror(database *db.DB, path string) error {
 	if err := os.Remove(path); err != nil &&
 		!errors.Is(err, os.ErrNotExist) {

cmd/testfixture/main_test.go

@@ -0,0 +1,53 @@
+package main
+
+import (
+	"context"
+	"path/filepath"
+	"testing"
+	"time"
+
+	"github.com/stretchr/testify/assert"
+	"github.com/stretchr/testify/require"
+
+	"go.kenn.io/agentsview/internal/db"
+)
+
+func TestCreateProjectReclassificationFixture(t *testing.T) {
+	database, err := db.Open(filepath.Join(t.TempDir(), "sessions.db"))
+	require.NoError(t, err)
+	t.Cleanup(func() { require.NoError(t, database.Close()) })
+
+	base := time.Date(2026, 7, 1, 10, 0, 0, 0, time.UTC)
+	require.NoError(t, createProjectReclassificationFixture(database, base))
+
+	const (
+		machine      = "remote-example-host"
+		wrongProject = "wrong_branch_label"
+		worktreeRoot = "/srv/worktrees/github.com/example-org/sample-service/example-worktree"
+	)
+	wantCwds := map[string]string{
+		"test-session-project-reclassification-root":   worktreeRoot,
+		"test-session-project-reclassification-nested": worktreeRoot + "/cmd/server",
+	}
+	for sessionID, wantCwd := range wantCwds {
+		session, getErr := database.GetSession(context.Background(), sessionID)
+		require.NoError(t, getErr)
+		require.NotNil(t, session)
+		assert.Equal(t, machine, session.Machine)
+		assert.Equal(t, wrongProject, session.Project)
+		assert.Equal(t, wantCwd, session.Cwd)
+	}
+
+	snapshots, err := database.ListSessionProjectIdentitySnapshots(
+		context.Background(),
+	)
+	require.NoError(t, err)
+	require.Len(t, snapshots, 2)
+	for _, snapshot := range snapshots {
+		assert.Equal(t, machine, snapshot.Machine)
+		assert.Equal(t, wrongProject, snapshot.Project)
+		assert.Equal(t, worktreeRoot, snapshot.RootPath)
+		assert.Equal(t, worktreeRoot, snapshot.WorktreeRootPath)
+		assert.NotEmpty(t, snapshot.Key)
+	}
+}

docs/activity.md

@@ -99,6 +99,40 @@ stacked bars to compare interactive and automated contributions.
 Rows with no value for the selected metric are omitted from that view, so
 cost-only untimed sessions appear in **Cost** but not **Agent-min**.
 
+## Reclassify A Project
+
+Worktree layouts the parser does not recognize can surface a branch or
+worktree directory name as a project. When that happens, hover or
+keyboard-focus a row in the **Project** breakdown and use the pencil action to
+open **Reclassify project**. On touch devices the action is always visible.
+
+The dialog works through the existing
+[worktree project mapping](/configuration/#worktree-project-mappings) system:
+
+- It lists the worktrees that produced the clicked row in the current Activity
+  view, grouped by machine and worktree evidence. A single group is
+  preselected; several groups require an explicit choice, because different
+  worktrees usually need different target projects.
+- The suggested **path prefix** covers the selected group's working
+  directories. You can edit it — for example, shorten it to cover sibling
+  worktrees of the same repository.
+- The **target project** typeahead suggests known projects and accepts a new
+  name. When the server normalizes the name (for example `sample-service`
+  becomes `sample_service`), the dialog shows the stored form before you
+  apply.
+- The **full archive impact** preview is live and authoritative: it counts
+  matching sessions across all dates for that machine, not just the current
+  Activity range. A prefix that touches more than one existing project shows a
+  warning with per-project counts — usually a sign the prefix is too broad. A
+  prefix matching zero sessions cannot be applied.
+
+**Apply** saves the rule and rewrites the matching sessions in one atomic
+step, then reloads the report. The rule stays active for future syncs and is
+managed under **Settings → Worktree mappings**, which records the label the
+row originally showed. On a read-only server (`pg serve` or `duckdb serve`)
+the action explains that reclassification happens on the writable archive that
+syncs the machine's sessions.
+
 ## Activity Insight
 
 At the bottom of the page, **Activity Insight** shows an existing global

docs/configuration.md

@@ -616,27 +616,42 @@ manual sync, and the periodic directory scan.
 
 ### Worktree Project Mappings
 
-The parser infers a session's project from its `cwd`, which works for standard
-layouts but not custom worktree conventions like
-`~/code/{project}.worktrees/feat/<branch>/` — those sessions otherwise group
-under `<branch>` rather than `{project}`. As of 0.29.0, you can register manual
-**path-prefix → project** rules from the **Worktree Project Mappings** section
-in Settings:
+The parser infers a session's project from its `cwd`. It recognizes common
+worktree manager layouts, including the generic
+`worktrees/github.com/<owner>/<repository>/<worktree>` convention, where the
+repository segment becomes the project. Layouts it does not recognize — such
+as `~/code/{project}.worktrees/feat/<branch>/` — otherwise group sessions
+under `<branch>` rather than `{project}`. For those, register manual
+**path-prefix → project** rules from the **Worktree mappings** section in
+Settings, or directly from the Activity project breakdown (see
+[Reclassify a project](/activity/#reclassify-a-project)):
 
 ![Worktree Project Mappings settings section](/assets/generated/screenshots/worktree-mappings.png)
 
 - Mappings are explicit; there is no auto-discovery.
+- Each rule is scoped to one machine. The machine selector manages rules for
+  the local machine and for any remotely synced machine. Rules live in the
+  writable archive that ingests that machine's sessions, which may be the
+  source machine's local SQLite archive or a separate collector archive.
 - Each rule applies whenever a session's `cwd` falls under the configured
   prefix, on both new sessions as they sync and (via the **Apply** button)
-  already-imported sessions.
+  already-imported sessions. Prefixes match on directory boundaries, so
+  `/worktrees/service` does not match `/worktrees/service-old`.
+- Enabled mappings run after parser inference, so an explicit rule always wins
+  when the two disagree.
 - The default `explicit` layout maps every matching path to the project name
   stored on the rule. The `repo_dot_worktrees` layout derives the project from
   the first path segment under the prefix when it is named `<repo>.worktrees`,
   so a path like `/code/agentsview.worktrees/feature/frontend` resolves to
   project `agentsview`.
-- Rules are stored in a `worktree_project_mappings` SQLite table scoped to the
-  host machine, so a mapping created on one machine does not leak into another
-  machine's view of synced sessions.
+- Rules created from the Activity dialog record the mislabeled project they
+  corrected, shown as **Originally shown as …**. The value is informational
+  and set once; to manually revert a reclassification, edit the rule's target
+  back to that original label and apply again.
+- Disabling or deleting a rule does not rewrite sessions by itself. Sessions
+  whose source files still exist revert to parser-derived names on a later
+  reparse or full resync, while orphaned sessions keep their stored
+  classification.
 - Excluded, trashed, and skipped session files are left alone.
 
 Mappings only mutate the session's `project` field; the rest of the session

docs/superpowers/plans/2026-07-12-ci-docker-build-retry.md

@@ -1,5 +1,8 @@
 # CI Docker Build Retry Implementation Plan
 
+> **Status:** Complete. Shipped via scripts/retry.sh and PR #1111 (fix(ci):
+> retry transient SSH image builds); verified against origin/main 2026-07-17.
+
 > **For agentic workers:** REQUIRED: Use superpowers:subagent-driven-development
 > (if subagents available) or superpowers:executing-plans to implement this
 > plan. Steps use checkbox (`- [ ]`) syntax for tracking.
@@ -22,7 +25,7 @@ ______________________________________________________________________
 
 - Create: `scripts/retry_test.sh`
 
-- [ ] **Step 1: Write the failing behavioral test**
+- [x] **Step 1: Write the failing behavioral test**
 
     Create a temporary fake command that records its arguments and attempt count,
     fails twice, and succeeds on its third invocation. Assert that
@@ -36,7 +39,7 @@ ______________________________________________________________________
     Add a second fake command that always exits 17. Assert that the helper invokes
     it exactly three times and returns exit status 17.
 
-- [ ] **Step 2: Run the test to verify it fails for the missing helper**
+- [x] **Step 2: Run the test to verify it fails for the missing helper**
 
     Run: `bash scripts/retry_test.sh`
 
@@ -50,15 +53,15 @@ ______________________________________________________________________
 
 - Test: `scripts/retry_test.sh`
 
-- [ ] **Step 1: Add the minimal retry loop**
+- [x] **Step 1: Add the minimal retry loop**
 
     Accept a maximum-attempt count and delay in seconds followed by the command
     and its arguments. Run the command until it succeeds or reaches the limit,
     sleep for `base delay * failed-attempt number` between failures, emit a
     concise retry message to standard error, and return the final command's exit
     status when exhausted.
 
-- [ ] **Step 2: Run the behavioral test to verify it passes**
+- [x] **Step 2: Run the behavioral test to verify it passes**
 
     Run: `bash scripts/retry_test.sh`
 
@@ -72,16 +75,16 @@ ______________________________________________________________________
 
 - Modify: `.github/workflows/ci.yml:282-283`
 
-- [ ] **Step 1: Add the retry test to the scripts job**
+- [x] **Step 1: Add the retry test to the scripts job**
 
     Run `bash scripts/retry_test.sh` alongside the existing shell-script tests.
 
-- [ ] **Step 2: Wrap the SSH image build**
+- [x] **Step 2: Wrap the SSH image build**
 
     Replace the direct build invocation with
     `bash scripts/retry.sh 3 10 docker build -t agentsview-sshd -f testdata/ssh/Dockerfile .`.
 
-- [ ] **Step 3: Run focused validation**
+- [x] **Step 3: Run focused validation**
 
     Run: `bash scripts/retry_test.sh`
 
@@ -97,17 +100,17 @@ ______________________________________________________________________
 
 - Commit the design, plan, helper, test, and workflow changes.
 
-- [ ] **Step 1: Review and scrub the outgoing diff and messages**
+- [x] **Step 1: Review and scrub the outgoing diff and messages**
 
     Verify that no private paths, identities, hostnames, or unrelated changes are
     present.
 
-- [ ] **Step 2: Commit the implementation**
+- [x] **Step 2: Commit the implementation**
 
     Use a focused conventional commit explaining why transient registry
     availability should not invalidate successful integration work.
 
-- [ ] **Step 3: Push and open a pull request**
+- [x] **Step 3: Push and open a pull request**
 
     As explicitly requested by the user, push the current feature branch and open
     a rationale-first PR whose description is a summary only, without a