Skip to content

feat(app): restore the archive app and retire the orchestrator - #18

Merged
hsusul merged 4 commits into
mainfrom
p1-1-restore-archive
Oct 26, 2026
Merged

hsusul merged 4 commits into
mainfrom
p1-1-restore-archive

Conversation

@hsusul

@hsusul hsusul commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Why

Lore is going back to being a local archive of Claude Code and Codex sessions. Commit 502827d swapped the archive app for an agent orchestrator. This PR puts the archive app back and deletes the orchestrator.

What changed

  • scripts/p1-restore.sh deletes the orchestrator crate, the workbench UI, the task commands, and the IPC mock. It then checks out the archive shell and UI from 502827d^.
  • The workspace, the shell manifest, the capability file, and lore-ipc go back to their 502827d^ state. That drops the orchestrator DTOs, their bindings, and the notification plugin.
  • npm dependencies that only the workbench used are gone.

Scope

  • Covers the shell, the UI, lore-ipc, and the manifests. The whole tree now matches 502827d^ except the script, README.md, tauri.conf.json, the favicon in index.html, src/vite-env.d.ts, and one lockfile license field.
  • Leaves README.md and tauri.conf.json to their own PR.
  • Leaves the scan worker and watcher as they were. P1-3 owns the CPU cost of the background scan.

Tradeoffs

  • The restored sources needed no hand edits, so the script output and the manifest commit stay separate. Reviewers can rerun scripts/p1-restore.sh on main and diff against the first commit. A rerun on this branch leaves the working tree clean.
  • The orchestrator stays reachable on branch archive/orchestrator-providers and at commit 0fab97f, which is worth a tag.

Blast Radius

The desktop app becomes the archive again, and every orchestrator command is gone. npm run dev shows no sample data until P1-2 adds an archive mock.

Verification

  • cargo fmt --all -- --check, cargo clippy --workspace --all-targets --all-features -- -D warnings, and cargo test --workspace pass, with 834 tests including no_egress.
  • cargo test -p lore-ipc leaves crates/lore-ipc/bindings unchanged, and cargo build --locked -p lore-app succeeds.
  • npm ci, npm run lint, npm run typecheck, npm test (151 tests), and npm run build pass.

The script deletes the orchestrator crate, the workbench UI, the task
commands, and the in-memory IPC mock. It then checks out the archive shell
and UI from 502827d^, the parent of the orchestrator pivot. It keeps
src/format.ts because the restored UI imports it, and drops src/diff.ts
because nothing does.

This commit is the script's output and nothing else. Rerun the script on
the parent commit and diff to check it. The tree does not build yet; the
next commit holds the hand edits.
Drop lore-orchestrator from the workspace. Point the shell back at lore-core
and rusqlite, and remove tauri-plugin-notification with its capability
entries, since no restored code sends notifications. Remove the task,
workspace, activity, merge queue, repo settings, and decision DTOs from
lore-ipc with their generated bindings.

Each manifest, the capability file, lore-ipc, and Cargo.lock now match
502827d^ byte for byte. The restored sources needed no edits for the pinned
toolchain, clippy, eslint, or tsc.
Remove the four @fontsource-variable fonts, @tauri-apps/plugin-notification,
react-markdown, remark-gfm, and sonner. No file under src, index.html, or the
build config imports them after the restore. package.json now matches
502827d^, and the lockfile differs from it only by the license field newer
npm writes.
@hsusul
hsusul merged commit 7f13a54 into main Oct 26, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant