Document shared repo RAA deployment

MULTI_PROJECT.md

@@ -4,10 +4,14 @@ Goal: keep one codebase and run separate deployments for each editorial project.
 
 ## Target model
 
-- One canonical git repository for application code.
+- One canonical git repository for application code:
+  `http://192.168.1.135:3000/exostring/new_vk_parser.git`.
+- One canonical local workspace: `D:\DEVELOPMENT\new_vk_parser`.
 - One Coolify application per project.
 - One Postgres database per project.
 - Project differences live in Coolify env variables and database settings, not in code.
+- The old RAA local copy `D:\DEVELOPMENT\raa-parser_poster` and old RAA Gitea repo
+  are not the source of truth.
 
 ## Per-project env
 
@@ -43,14 +47,16 @@ RAA current social targets:
 - raw media Telegram channel: `tg_media_channel_id=-1004312015562`
 - final Telegram publication channel: `tg_poster_chat_id=-1001303630155`
 - VK owner: `vk_poster_owner_id=-36860851`, `vk_poster_from_group=true`
+- More RAA-specific runtime notes are in `RAA.md`.
 
 ## Poster modules
 
 The site poster is selected by `site_poster_provider`. A project can disable the worker or leave the provider empty when there is no website poster yet. New website integrations should be added as provider modules behind the same interface instead of branching the worker by project name.
 
-## Migration path
+## Current Status
 
-1. Finish removing project-specific constants from code.
-2. Choose one canonical repo for both deployments.
-3. Point both Coolify applications to that repo and branch.
-4. Keep only env and database settings different between projects.
+- FN-8 Coolify app `n6cnr60anmruiwkiey0pukye` points to `new_vk_parser.git`, branch `main`.
+- RAA Coolify app `korokrhpoyqxf0nw2y8vk7lp` points to `new_vk_parser.git`, branch `main`.
+- Both projects should deploy from the same commit SHA.
+- Keep only env and database settings different between projects.
+- Do not add project-specific defaults to migrations or `.env.example`.