Projects
A project is a folder on the Core's machine that hosts harness workspaces. The path is a path on that machine; only the Core can validate it. The Core owns the project and stores it in its SQLite. The Panel never keeps the folder path as its own state.
Add a project
From the Panel, Add project asks the selected Core to register a folder it can see. On the reference Compose stack that is the bind-mounted ./repos directory on the host — that is where Add project finds checkouts. On a metal Core, pick any directory that already has your code. The Core is the only process that checks the path exists and is allowed.
From the CLI, the same fact is an absolute path on the Core, sent as typed:
actana project add api /srv/work/api
Nothing on your laptop is resolved or stat'd. actana project browse lists the Core's disk when you need to find the path.
A project's path is fixed once it exists. A folder at a different path is a different project.
Remove never deletes files
Removing a project from the Panel only unlinks it. The Core drops the row (and the sessions under it); the files on disk are not touched. The confirmation in the Panel says so. Your checkouts stay where they were, including ./repos on Compose.
Pins are Core facts
Pinning a project (or a session) is stored on the owning Core. Every Panel connected to that Core sees the same pin. It is not a per-browser preference.
The Harness a project starts sessions with, whether to skip the new-session dialog, and the project's default grid view are also Core facts. Filing that is yours alone — groups, card images, a launch URL — lives on the Panel and two Panels on one Core may disagree about it.
