✨ feat: auto-reload tibi-server on api/ changes + skill docs for project registration

.agents/BUILD_CHECKLIST.md

@@ -31,7 +31,6 @@ Do not mark a phase done only because code exists. A phase is done only when its
 - `api/hooks/config-client.js`
 - `frontend/.htaccess` when the deployment path uses the shipped Apache rewrite/proxy file
 - `package.json`
-- optional operator-owned root `config.yml` for the tibi-server instance when the current stack expects server-level config outside the project config
 
 **Implementation checks:**
 
@@ -55,8 +54,8 @@ Do not mark a phase done only because code exists. A phase is done only when its
 - [ ] Decide explicitly which bootstrap path applies:
   - local starter Docker stack from `docker-compose-local.yml` and `Makefile`
   - shared or operator-managed tibi-server with explicit server-level config/project registration
-- [ ] For the local starter Docker path, confirm the repo is mounted into `/data` and the project serves through the repo-local `api/config.yml`; do not invent a separate root `config.yml` or `/api/v1/project` step.
-- [ ] For the shared/external tibi-server path, create the root `config.yml`, register the project, and reload it.
+- [ ] For the local starter Docker path, confirm the repo is mounted into `/data` and the project serves through the repo-local `api/config.yml`; treat a new project as initially unregistered and, if the running stack returns `project not found` for the namespace, complete a one-time `/api/v1/project` registration.
+- [ ] For the shared/external tibi-server path, confirm the raw project API access and register/reload the project there.
 - [ ] Confirm local/dev assumptions for Docker, reverse proxy, and any required basic-auth files only when the current environment actually uses them.
 - [ ] If audit logging or transaction-sensitive features are planned, confirm the MongoDB/replica-set prerequisite for the target environment instead of assuming the local Docker setup is enough.