chore(repo): initialize Cowork Local Gitea repository

docs/gitea/actions-runner.md

@@ -0,0 +1,13 @@
+# Gitea Actions Runner
+
+The repository includes `.gitea/workflows/ci.yaml`. Source import does not depend on a runner being online, but Pull Request checks do.
+
+An administrator should:
+
+1. Register an `act_runner` compatible with Gitea 1.27.1 at the instance, organization, or repository level.
+2. Give it a label that can satisfy `runs-on: ubuntu-latest` (the common default label mapping is acceptable).
+3. Ensure the runner can fetch the pinned major versions of `actions/checkout` and `actions/setup-python`, or mirror those actions internally.
+4. Trigger the CI workflow and confirm both the syntax and routing test jobs complete.
+5. Only then make the CI status check mandatory in stable-branch protection.
+
+Do not weaken or ignore failing checks to obtain a green workflow. If no runner is available, keep the workflow committed and enforce the same commands during review.

docs/governance/definition-of-done.md

@@ -0,0 +1,25 @@
+# Definition of Done
+
+## Cowork-native feature
+
+A Cowork-native change is done when:
+
+- implementation is complete;
+- applicable tests pass;
+- documentation is updated when needed;
+- the Pull Request is reviewed;
+- the change is merged into the stable/default branch.
+
+## Core AI contribution
+
+A Core AI contribution is done only when its Pull Request is merged into Cowork Local. “Core AI finished coding” or “Core AI pre-review passed” is not Done.
+
+Required evidence:
+
+- Core issue reference;
+- Cowork Local Pull Request;
+- test/validation evidence;
+- Cowork reviewer;
+- merge commit or merge reference.
+
+Use one logical change per Pull Request. For example, TL-065, TL-146, and TL-148 Phase 1 require separate Pull Requests. Split large work into vertical, reviewable slices.

docs/governance/ownership.md

@@ -0,0 +1,28 @@
+# Repository Ownership
+
+## Cowork Team
+
+The Cowork Team owns:
+
+- product architecture;
+- Cowork runtime and platform behavior;
+- UI/UX;
+- releases;
+- the stable/default branch;
+- final Pull Request review and merge.
+
+## FSG AI Core Team
+
+The AI Core Team contributes selected generic capabilities, including:
+
+- MCP integrations;
+- agent capabilities;
+- orchestration tests;
+- model-routing and fallback tests;
+- security/evaluation integration;
+- Superpowers enhancements;
+- reusable platform improvements.
+
+AI Core is a contributor, not the owner of Cowork Local. It does not self-merge a contribution into the Cowork production branch before Cowork Team review.
+
+`OWNERS.yaml` records team-level ownership only. It intentionally contains no invented usernames and does not assume GitHub CODEOWNERS semantics in Gitea.

docs/governance/review-policy.md

@@ -0,0 +1,12 @@
+# Review Policy
+
+Normal Cowork changes follow the Cowork Team's reviewer policy.
+
+Core AI contributions require two review stages:
+
+1. Core AI internal/pre-review.
+2. Cowork Team final review and merge decision.
+
+Additional scrutiny is required for permissions, credentials, MCP write/exec, sandboxing, network access, TLS, customer/project isolation, security rules, model routing/fallback, and data deletion. These changes must not be auto-merged merely because automated checks pass.
+
+Branch protection should prevent force-push and deletion of the stable branch, prefer Pull Requests, and require CI after an Actions runner is available. Core AI contributors must not be configured as Cowork final approvers by process convention.

docs/integration/core-ai-contribution.md

@@ -0,0 +1,43 @@
+# FSG AI Core Contribution Integration
+
+Core AI task execution source of truth:
+
+[fsg-ai-core-assets Issues / Project](http://34.143.229.138/gitea-admin/fsg-ai-core-assets)
+
+Cowork source changes:
+
+`cowork-local` Pull Requests
+
+Typical relationship:
+
+```text
+Core Issue #42 -> cowork-local PR #18 -> Cowork Review -> Merged
+-> Core Issue #42 Done
+```
+
+The Core board lifecycle is:
+
+```text
+Backlog -> Ready -> In Progress -> Review -> Upstream Review -> Done
+```
+
+- `Review` means Core AI internal/pre-review.
+- `Upstream Review` means the Cowork Pull Request is waiting for Cowork Team review.
+- `Done` means the Cowork Team merged the Pull Request.
+
+Every Core AI Pull Request should reference:
+
+```text
+Core Repo: http://34.143.229.138/gitea-admin/fsg-ai-core-assets
+Core Issue: #<number> (prefer the full issue URL)
+Core Task: T?-??
+```
+
+## Promotion model
+
+```text
+Core Asset -> Evaluated -> Candidate for Upstream -> Cowork PR
+-> Cowork Review -> Upstream Merged
+```
+
+Not every Core asset needs promotion. Do not create a `core-ai-assets/` copy here. Golden datasets, CASAN, internal agent catalogs, knowledge/RAG collections, and Core evaluation assets remain Core-owned unless the Cowork runtime needs a specific artifact under an agreed integration contract.