Document Gitea AGit PR workflow

.codex/project.md

@@ -10,6 +10,12 @@ Repository:
 MrSphay/WatchLink
 ```
 
+Current organization remote:
+
+```text
+Code-Inc/WatchLink
+```
+
 ## Commands
 
 ```text
@@ -49,6 +55,25 @@ Package manager:
 npm
 ```
 
+## Pull Requests
+
+This project uses the Gitea organization repository directly rather than a
+personal fork workflow. If API-based PR creation is unavailable or
+`GITEA_TOKEN` is not a valid API token, create PRs over SSH with Gitea AGit:
+
+```text
+git push -o topic=<branch-name> origin HEAD:refs/for/<base-branch>
+```
+
+Example:
+
+```text
+git push -o topic=codex/project-hygiene-followups origin HEAD:refs/for/feature/room-invites-chat-moderation
+```
+
+After creation, validate the PR with the public API or web UI and poll any
+started Gitea checks until success or a concrete blocker is known.
+
 ## Build Artifacts
 
 Next.js standalone build output:

docs/agent-handoff.md

@@ -15,6 +15,8 @@ Initial implementation created from `codex-agent-repository-kit` guidance.
 
 - Repository visibility is public.
 - Gitea Actions can run `npm install`, tests, build, and Docker image publishing.
+- PRs can be created in the organization repo over SSH with Gitea AGit when API
+  credentials are unavailable: `git push -o topic=<branch> origin HEAD:refs/for/<base>`.
 - Local Docker is still unavailable in this Codex environment, but Gitea Actions can build the image.
 - Docker publish was fixed by updating `REGISTRY_TOKEN`; Gitea issue #1 is closed.
 - Room-scoped persisted invite codes were added to the room Invite rail. Room owners, admins, and room managers can create expiring invite codes and revoke active room invites.