chore: add migration/ bundle for cross-machine setup
Bundles state that lives OUTSIDE the xenia-rs repo so a fresh clone on
another machine can be brought up to identical configuration via
migration/setup.sh:
- claude-memory/ ~/.claude/projects/-home-fabi-RE-Project-Sylpheed/memory/
(103 files, 1.1 MB - MEMORY.md + every
project_xenia_rs_*.md from audits
addis_signext through audit-058)
- project-root/dot-claude/ <project-root>/.claude/settings.json
(Stop hook + permissions)
- project-root/ppc-manual/ <project-root>/ppc-manual/
(PowerPC reference docs, 397 files, 3.7 MB)
- project-root/run-canary.sh <project-root>/run-canary.sh
- README.md Human-readable setup checklist
- setup.sh Idempotent installer (also reclones
xenia-canary at pinned HEAD 6de80dffe)
- MANIFEST.md Per-file mapping + per-file-not-bundled
restoration recipe
Excluded from bundle (not shippable via git):
- Sylpheed ISO (7.8 GB; copyright; manual copy required)
- sylpheed.db (395 MB; regenerable from XEX via analysis tooling)
- target/ build artifacts (rebuild on target)
- audit-runs probe firehoses (.log/.stdout/.stderr ~11 GB; rerun if needed)
- audit-runs memory dumps (.bin ~4.5 GB; rerun audit-026/027/029 if needed)
- xenia-canary checkout (setup.sh reclones from
git.mc02.dev/fabi/Xenia-Canary.git at HEAD 6de80dffe)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
10
migration/claude-memory/project_xenia_rs_desktop_app.md
Normal file
10
migration/claude-memory/project_xenia_rs_desktop_app.md
Normal file
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: xenia-rs desktop app design
|
||||
description: UI/UX design decisions for the xenia-rs desktop app — feature groupings and view layout
|
||||
type: project
|
||||
originSessionId: c12e8acc-6326-4933-9263-32745c4b1219
|
||||
---
|
||||
The disassembler, debugger, analyzer, and executor share a single unified view in the desktop app. Their purposes and underlying data are related/overlapping, so they are not treated as separate panels or tabs.
|
||||
|
||||
**Why:** The user explicitly stated this during the overview drafting phase.
|
||||
**How to apply:** When writing UI copy, feature descriptions, or design docs, describe these four as one combined "Analysis Workspace" rather than four separate features.
|
||||
Reference in New Issue
Block a user