@moretea-labs/forge 1.5.0-rc.1

package/docs/tutorials/01-install-and-start.zh-CN.md

@@ -0,0 +1,93 @@
+# 教程 1：安装并启动
+
+本教程完成 CLI 安装、用户级运行时初始化、环境检查和第一个仓库注册。
+
+## 1. 平台与基础环境
+
+- macOS / Linux：完整支持。
+- Windows：完整工作流推荐 WSL2。
+- Windows 原生 PowerShell：预览支持安装、doctor、仓库注册/读取和可移植 Controller 操作。
+
+需要 Git、Node.js 20.10 或更高版本、npm 和可写的用户目录。Bun 1.0+ 是可选项，推荐用于源码开发和完整测试。
+
+```bash
+git --version
+node --version
+npm --version
+```
+
+详细范围见[平台支持说明](../operations/platform-support.zh-CN.md)。
+
+## 2. 安装 CLI
+
+发布候选版本使用 npm 的 `next` channel：
+
+```bash
+npm install -g @moretea-labs/forge@next
+# 或
+bun add -g @moretea-labs/forge@next
+forge --version
+```
+
+需要参与 Forge 源码开发时，再从仓库安装：
+
+```bash
+git clone https://github.com/moretea-labs/forge.git
+cd forge
+npm ci --ignore-scripts --no-audit --no-fund
+npm install -g . --omit=optional --no-audit --no-fund
+```
+
+该 package 只提供 `forge`、`forge-hook` 与 `forge-runtime`。候选版本使用 `next`，稳定版本使用 `latest`。
+
+## 3. 打开引导式配置会话
+
+```bash
+forge --version
+forge setup open --target both
+```
+
+`forge setup open` 会在 `~/.forge/setup/` 下创建或恢复同一个用户级配置会话，执行就绪检查，并且每次只给出一个下一步配置动作。完成该动作后继续执行：
+
+```bash
+forge setup next
+```
+
+反复执行 `forge setup next`，直到状态变成 `ready`，然后关闭会话：
+
+```bash
+forge setup close
+```
+
+可使用 `forge setup status` 查看持久化进度，使用 `forge setup check` 获取一次性只读报告。只使用一个 host 时可改为 `--target codex` 或 `--target claude`。配置会话不会静默执行远程写入、读取秘密、破坏性操作或服务安装。
+
+## 4. 接入或注册仓库
+
+macOS、Linux、WSL2 先预览再执行完整接入：
+
+```bash
+forge adopt --repo /path/to/your-project --dry-run
+forge adopt --repo /path/to/your-project
+```
+
+所有平台均可显式注册：
+
+```bash
+forge repo register /path/to/your-project --name my-project --json
+forge repo list --json
+```
+
+保存返回的 `repoId`，它是 ChatGPT 和 Controller 使用的稳定仓库身份。
+
+## 5. 确认环境就绪
+
+```bash
+forge setup status
+forge doctor
+forge status --json
+forge repo list --json
+```
+
+运行态应保存在 Controller Home 和被忽略的仓库链接中，不应进入公开源码。不要提交 token、MCP runtime 文件、Local Job、日志或 worktree。
+
+下一步阅读[教程 2：连接 ChatGPT](02-connect-chatgpt.zh-CN.md)，出现问题时看[故障排查](../operations/troubleshooting.zh-CN.md)。

package/docs/tutorials/02-connect-chatgpt.md

@@ -0,0 +1,82 @@
+# Tutorial 2: Connect ChatGPT
+
+This tutorial starts the local MCP service, publishes only its MCP endpoint through HTTPS, and verifies the default facade tools.
+
+## 1. Before you start
+
+You need:
+
+- a repository already registered with `forge repo register`;
+- a healthy `forge doctor` result;
+- a stable public HTTPS address ending in `/mcp`;
+- ChatGPT access to Developer Mode and custom MCP connectors.
+
+Coding agents are not required. Install Codex or Claude only when you intend to delegate implementation.
+
+Windows users should run the Controller and tunnel inside WSL2 for the full supported workflow. Native PowerShell operation remains preview scope.
+
+## 2. Generate the MCP configuration
+
+```bash
+forge mcp setup chatgpt --repo /path/to/your-project
+```
+
+The local endpoint is loopback-only:
+
+```text
+http://127.0.0.1:8765/mcp
+```
+
+Do not expose the local Controller UI at port 8766.
+
+## 3. Verify the canonical Runtime service
+
+`forge mcp setup chatgpt` installs or updates the configuration consumed by the single `forge-runtime`. Install the macOS service owner with `forge runtime service install`; launchd then owns startup and unexpected-exit restart of that one root process. There is no MCP KeepAlive wrapper or component-level lifecycle command.
+
+```bash
+forge runtime service install \
+  --controller-home /path/to/controller-home \
+  --repo /path/to/forge-source-or-runtime-root \
+  --host 127.0.0.1 \
+  --port 8765 \
+  --auth-token-file /path/to/controller-home/mcp/runtime-token
+forge runtime status --controller-home /path/to/controller-home --json
+forge mcp doctor --repo /path/to/your-project
+```
+
+Publish only the configured loopback MCP endpoint through a stable Tailscale or Cloudflare HTTPS tunnel. Temporary tunnel URLs are suitable for testing but are poor long-lived Connector identities. Enable Codex or Claude only after their CLIs are installed and authenticated; provider availability does not change the Runtime process topology.
+
+## 4. Add the Connector in ChatGPT
+
+1. Open **Settings → Apps & Connectors → Advanced settings**.
+2. Enable Developer Mode.
+3. Create a custom MCP Connector.
+4. Enter the public HTTPS URL ending in `/mcp`.
+5. Add the Connector to a new conversation.
+
+## 5. Verify the safe default surface
+
+The core Connector should expose:
+
+- `rh_status` — runtime and repository readiness;
+- `rh_context` — bounded context for the selected repository;
+- `rh_work` — start or continue bounded work;
+- `rh_inbox` — decisions, approvals, and items requiring attention.
+
+It also exposes a few repository bootstrap and selection tools. Do not switch to `full` merely to see more names; `advanced` and `full` are maintainer and compatibility surfaces.
+
+Test in this order:
+
+```text
+Use Forge. Check system readiness with rh_status. Then load bounded context for my registered repository with rh_context. Do not make changes yet.
+```
+
+## 6. Security checks
+
+- Keep MCP bound to loopback and publish it only through a controlled HTTPS endpoint.
+- Keep the local UI private.
+- Start read-only, then authorize bounded writes when needed.
+- Remote Git, GitHub, email, destructive cleanup, and publication remain separately authorized.
+- Never paste MCP tokens or OAuth secrets into chat.
+
+Continue with [Tutorial 3: First Repository Task](03-first-repository-task.md). Use [Troubleshooting](../operations/troubleshooting.md) if the Connector or tool surface is not healthy.

package/docs/tutorials/02-connect-chatgpt.zh-CN.md

@@ -0,0 +1,80 @@
+# 教程 2：连接 ChatGPT
+
+本教程启动本地 MCP 服务，只通过 HTTPS 公开 MCP endpoint，并验证默认 facade 工具。
+
+## 1. 开始前需要
+
+- 已通过 `forge repo register` 注册仓库；
+- `forge doctor` 状态正常；
+- 一个稳定、以 `/mcp` 结尾的公网 HTTPS 地址；
+- ChatGPT Developer Mode 和自定义 MCP Connector 权限。
+
+编码 Agent 不是必需环境。只有准备委派实现时才安装 Codex 或 Claude。
+
+Windows 用户建议在 WSL2 内运行 Controller 和隧道；Windows 原生 PowerShell 仍属于预览范围。
+
+## 2. 生成 MCP 配置
+
+```bash
+forge mcp setup chatgpt --repo /path/to/your-project
+```
+
+本地 endpoint 只监听 loopback：
+
+```text
+http://127.0.0.1:8765/mcp
+```
+
+不要把 8766 端口的本地 Controller UI 暴露到公网。
+
+## 3. 验证唯一 Forge Runtime 服务
+
+`forge mcp setup chatgpt` 会安装或更新唯一 `forge-runtime` 使用的配置。通过 `forge runtime service install` 安装 macOS 服务后，launchd 负责该根进程的开机启动与异常退出自动拉起；系统不再提供 MCP KeepAlive 包装器或组件级生命周期命令。
+
+```bash
+forge runtime service install \
+  --controller-home /path/to/controller-home \
+  --repo /path/to/forge-source-or-runtime-root \
+  --host 127.0.0.1 \
+  --port 8765 \
+  --auth-token-file /path/to/controller-home/mcp/runtime-token
+forge runtime status --controller-home /path/to/controller-home --json
+forge mcp doctor --repo /path/to/your-project
+```
+
+只将配置好的 loopback MCP endpoint 通过稳定的 Tailscale 或 Cloudflare HTTPS tunnel 发布。Codex/Claude CLI 安装并登录后才启用对应 provider，但 provider 可用性不会改变 Runtime 进程拓扑。
+
+## 4. 在 ChatGPT 添加 Connector
+
+1. 打开 **Settings → Apps & Connectors → Advanced settings**。
+2. 开启 Developer Mode。
+3. 创建自定义 MCP Connector。
+4. 填入以 `/mcp` 结尾的公网 HTTPS URL。
+5. 在新会话中添加该 Connector。
+
+## 5. 验证默认安全工具面
+
+core Connector 应显示：
+
+- `rh_status`：运行时和仓库就绪状态；
+- `rh_context`：当前仓库的有界上下文；
+- `rh_work`：开始或继续有边界工作；
+- `rh_inbox`：需要决定、审批或处理的事项。
+
+此外只会暴露少量仓库初始化和选择工具。不要为了“工具更多”直接切到 `full`；`advanced` 和 `full` 是维护/兼容工具面。
+
+按以下顺序测试：
+
+```text
+使用 Forge。先用 rh_status 检查系统状态，再用 rh_context 获取当前注册仓库的有界上下文，暂时不要修改文件。
+```
+
+## 6. 安全检查
+
+- MCP 保持监听 loopback，只通过受控 HTTPS 地址公开。
+- 本地 UI 不公开。
+- 先只读，确有需要时再授权有边界写入。
+- 远程 Git、GitHub、邮件、破坏性清理和发布仍分别授权。
+- 不要把 MCP token 或 OAuth secret 粘贴到聊天中。
+
+下一步阅读[教程 3：完成第一个仓库任务](03-first-repository-task.zh-CN.md)。Connector 或工具面异常时看[故障排查](../operations/troubleshooting.zh-CN.md)。

package/docs/tutorials/03-first-repository-task.md

@@ -0,0 +1,57 @@
+# Tutorial 3: Complete the First Repository Task
+
+Use a small documentation or configuration change for the first run. The goal is to verify routing, bounded editing, review evidence, and cleanup before delegating complex code.
+
+## 1. Start read-only
+
+Ask ChatGPT:
+
+```text
+Use Forge. Check rh_status, then load rh_context for my selected repository. Summarize the current branch, working-tree state, relevant files, and available named checks. Do not modify anything yet.
+```
+
+Resolve a dirty tree or ambiguous repository selection before writing.
+
+## 2. Give a bounded task
+
+Example:
+
+```text
+Update the installation note in docs/example.md. Keep the change limited to that file, show the diff, and run the most relevant named documentation check. Do not push or publish anything.
+```
+
+Good first tasks name the desired outcome, allowed area, verification, and remote-write boundary.
+
+## 3. Understand the execution mode
+
+Forge should prefer Direct Edit for a small known change. A Direct Edit records file fingerprints, revisions, a persisted diff, and check evidence. Larger or dependency-aware work may be promoted to a durable Issue/Task/Run. Coding agents remain optional workers, not the default controller.
+
+## 4. Review before acceptance
+
+Check:
+
+- only intended files changed;
+- the diff matches the request;
+- the named check actually ran and passed;
+- no credentials, logs, runtime state, or personal paths were added;
+- no remote action occurred without authorization.
+
+Request corrections through `rh_work` when needed. Use `rh_inbox` for explicit decisions or approvals.
+
+## 5. Commit and remote actions
+
+A local commit may be part of an authorized repository workflow, but pushing, opening a pull request, editing GitHub state, tagging, or publishing are separate external actions. State the desired boundary explicitly, for example “commit locally but do not push.”
+
+## 6. Confirm cleanup and resumability
+
+At the end, ask for:
+
+- final Git status;
+- changed files and checks;
+- commit hash when a commit was requested;
+- any remaining worktree, branch, Job, or attention item;
+- the next safe action.
+
+A completed local task should leave either a clean working tree or clearly identified unrelated concurrent changes. Runtime logs and evidence remain in ignored Controller storage.
+
+Read [Features and Setup Levels](../operations/features.md) before enabling agents, GitHub, browser, schedules, or Workspace plugins.

package/docs/tutorials/03-first-repository-task.zh-CN.md

@@ -0,0 +1,57 @@
+# 教程 3：完成第一个仓库任务
+
+第一次运行请选择一个小型文档或配置修改。目标是先验证仓库路由、有边界编辑、审查证据和清理流程，再处理复杂代码。
+
+## 1. 先只读检查
+
+对 ChatGPT 说：
+
+```text
+使用 Forge。先检查 rh_status，再为我选择的仓库加载 rh_context。总结当前分支、工作区状态、相关文件和可用命名检查，暂时不要修改。
+```
+
+如果工作区不干净或仓库目标不明确，先处理这些问题再写入。
+
+## 2. 给出有边界任务
+
+示例：
+
+```text
+更新 docs/example.md 中的安装说明。修改只限这个文件，展示 diff，并运行最相关的文档命名检查。不要 push，也不要发布。
+```
+
+好的首个任务应写清目标、允许范围、验证方式和远程写入边界。
+
+## 3. 理解执行方式
+
+小而明确的修改应优先 Direct Edit。它会记录文件 fingerprint、revision、持久 diff 和检查证据。范围较大、存在依赖或需要跨会话恢复时，才升级为持久 Issue/Task/Run。编码 Agent 是可选执行者，不是默认总控。
+
+## 4. 接受前审查
+
+确认：
+
+- 只修改了预期文件；
+- diff 与需求一致；
+- 命名检查真实执行且通过；
+- 没有加入凭据、日志、运行态或个人绝对路径；
+- 没有未经授权的远程动作。
+
+需要修改时通过 `rh_work` 打回；需要明确决定或审批时查看 `rh_inbox`。
+
+## 5. 提交与远程动作
+
+本地 commit 可以属于已授权仓库流程，但 push、创建 PR、修改 GitHub、打 tag 和发布都是独立外部动作。应明确写出边界，例如“只在本地提交，不要 push”。
+
+## 6. 确认清理和可恢复性
+
+结束时要求返回：
+
+- 最终 Git 状态；
+- 改动文件和检查；
+- 如果要求提交，则返回 commit hash；
+- 是否还存在 worktree、branch、Job 或 attention item；
+- 下一步安全动作。
+
+完成的本地任务应留下干净工作区，或明确标识其他并行任务的改动。日志和执行证据只保存在被忽略的 Controller 运行态中。
+
+开启 Agent、GitHub、Browser、Schedule 或 Workspace 插件前，先阅读[功能与配置层级](../operations/features.zh-CN.md)。

package/docs/tutorials/README.md

@@ -0,0 +1,13 @@
+# Tutorials
+
+Follow these in order:
+
+1. [Install and start](01-install-and-start.md)
+2. [Connect ChatGPT](02-connect-chatgpt.md)
+3. [Complete the first repository task](03-first-repository-task.md)
+
+The tutorials use the stable default `advanced` MCP schema. Prefer `rh_status`, `rh_access`, `rh_context`, `rh_work`, and `rh_inbox`, but Direct Edit, Git, Agent, iOS, plugin, and recovery tools are intentionally available without switching permissions. `core` is a compatibility alias; `full` is only for legacy exhaustive exposure.
+
+For project maintenance, see [Contributing](../../CONTRIBUTING.md), [Support](../../SUPPORT.md), [Security](../../SECURITY.md), and the [release process](../operations/releasing.md).
+
+中文版本：[README.zh-CN.md](README.zh-CN.md)

package/docs/tutorials/README.zh-CN.md

@@ -0,0 +1,13 @@
+# 快速教程
+
+按顺序完成：
+
+1. [安装并启动](01-install-and-start.zh-CN.md)
+2. [连接 ChatGPT](02-connect-chatgpt.zh-CN.md)
+3. [完成第一个仓库任务](03-first-repository-task.zh-CN.md)
+
+教程使用固定的默认 `advanced` MCP schema。优先使用 `rh_status`、`rh_access`、`rh_context`、`rh_work` 和 `rh_inbox`，但 Direct Edit、Git、Agent、iOS、插件和恢复工具无需切换权限即可使用。`core` 是兼容别名，`full` 仅用于旧集成的全量暴露。
+
+仓库维护入口见：[贡献指南](../../CONTRIBUTING.md)、[支持说明](../../SUPPORT.md)、[安全策略](../../SECURITY.md) 与 [发布流程](../operations/releasing.zh-CN.md)。
+
+English: [README.md](README.md)

package/docs/wiki/Architecture.md

@@ -0,0 +1,85 @@
+# Architecture
+
+Forge is organized around one rule: **the client decides intent; Forge owns deterministic local execution state and safety boundaries.** ChatGPT can choose how much reasoning or planning a task needs, while Forge keeps repository identity, execution, evidence, and Runtime authority coherent.
+
+## System map
+
+```text
+ChatGPT / CLI / local UI
+        |
+        v
+Authenticated MCP transport
+        |
+        v
+Gateway + bounded 19-tool controller surface
+        |
+        +---- Direct reads / Direct Edit / explicit ephemeral workspace
+        |
+        +---- Managed Process Runtime ---- commands / checks
+        |            |
+        |            +---- Process record + output + completion receipt
+        |            +---- Claims / Leases / exact process identity
+        |
+        +---- Durable Work / Scheduler ---- long-lived or dependency-aware work
+        |            |
+        |            +---- repository/check-out ownership
+        |            +---- optional isolated worktrees / workers / agents
+        |
+        v
+Controller Home + repository state + evidence
+
+One Canonical Forge Runtime
+        |
+        +---- whole-release authority
+        +---- Runtime ownership / readiness / MCP
+        +---- independent standalone Recovery outside the primary failure domain
+```
+
+## Major boundaries
+
+### Client and tool surface
+
+The default ChatGPT-facing surface is bounded rather than exposing every internal handler. The five preferred facades are `rh_status`, `rh_access`, `rh_inbox`, `rh_context`, and `rh_work`; repository, patch, check, Process, plugin-dispatch, and result tools complete the current 19-tool connector schema. The exhaustive compatibility profile remains an implementation detail for explicit diagnostic clients.
+
+### Repository identity
+
+Every registered-repository execution is bound to a stable `repoId` and an explicit `checkoutId`. The current working directory cannot silently override that identity. Explicit unregistered workspace execution is a separate authority and does not create a repository registration behind the user's back.
+
+### Direct versus durable work
+
+Investigation is not itself a reason to create Work. A small, understood change can stay Direct. Durable Work, worktrees, campaigns, or workers are introduced when recovery, dependency tracking, isolation, long-running execution, or real risk requires them.
+
+### Process Runtime
+
+Repository commands and checks have one managed process lifecycle. Starting a command creates one Process identity; later status, wait, log, and cancel calls attach to that same process instead of spawning it again. Resource claims and leases protect conflicting writes without globally serializing unrelated repositories.
+
+### Verification and evidence
+
+Evidence is bound to repository identity, checkout, revision, command/check definition, and environment where applicable. Equivalent checks may coalesce or reuse valid evidence. A content or environment change invalidates stale evidence rather than silently reusing it.
+
+### MCP session lifecycle
+
+A client session is a transport boundary, not a work owner. If the canonical tool schema changes, a stale session receives a bounded `MCP_TOOL_SURFACE_CHANGED` reinitialization signal while its transport remains alive long enough for the host to initialize the replacement session. The replacement initialize then supersedes the old session. A schema fence must not make the entire Forge namespace disappear from the host conversation.
+
+### Runtime and release authority
+
+One Canonical Runtime owns the active local execution authority and one whole-release identity. Runtime source, release manifest, service definition, process ownership, and readiness must agree. Standalone Recovery is intentionally separate so the primary MCP process cannot be its own only recovery mechanism.
+
+## Concurrency model
+
+- Different repositories can run independently under global capacity limits.
+- Different checkouts/worktrees of one repository can run independently when their resource claims do not conflict.
+- The same checkout remains single-writer.
+- Integration and Git-ref mutation stay exclusive even when worktree implementation is parallel.
+- Shared checks can single-flight and reuse evidence rather than repeat physical execution for each session.
+
+## Authoritative documents
+
+- [System overview](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/system-overview.md)
+- [Architecture invariants](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/architecture-invariants.md)
+- [Multi-repository execution](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/multi-repository-execution.md)
+- [Verification and release gates](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/verification-and-release-gates.md)
+- [Implementation status](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/implementation-status.md)
+- [Runtime directory map](https://github.com/moretea-labs/forge/blob/main/docs/architecture/current/runtime-directory-map.md)
+
+Historical snapshots explain previous designs but are not current Runtime contracts.

package/docs/wiki/Core-Concepts.md

@@ -0,0 +1,27 @@
+# Core Concepts
+
+## Local-first controller
+
+Forge keeps execution and durable state on the operator-controlled machine. ChatGPT sends authenticated requests and receives bounded results; it does not become the process owner of the local runtime.
+
+## Explicit repository scope
+
+The controller can know many repositories, but each repository action resolves to a stable repository identity and, when needed, a checkout identity. A repository switch must be explicit.
+
+## Durable work
+
+Complex work is represented by persistent plans, tasks, jobs, runs, handoffs, checks, and evidence. A transport timeout does not imply that execution stopped, so status must be checked before replaying a write.
+
+## Bounded effects
+
+Reading, local edits, remote writes, destructive operations, and secret access are distinct effect classes. Local access mode changes convenience, not the authorization requirements for remote, destructive, or secret-bearing actions.
+
+## Evidence before completion
+
+A task is complete only when the relevant diff, checks, integrated revision, and cleanup state are known. Release claims require stronger evidence: exact revision identity, immutable artifacts, cold-start health, and external verification.
+
+## Immutable runtime releases
+
+Forge Runtime releases are built from a clean canonical source tree. Source commit, immutable manifest, service registration, active whole-release authority, database compatibility, Worker protocol, and the running Runtime identity must agree exactly.
+
+Continue with [Work Lifecycle](Work-Lifecycle), [Security Model](Security-Model), and [Runtime Architecture](Runtime-Architecture).

package/docs/wiki/Home.md

@@ -0,0 +1,36 @@
+# Forge Wiki
+
+Forge is a local-first action assistant that gives ChatGPT a durable, policy-bounded execution layer for local software work. The product is intentionally Direct-first: ordinary bounded work stays lightweight, while Process Runtime, Work, worktrees, scheduling, and Recovery exist for the cases that actually need lifecycle or isolation.
+
+## Start here
+
+- New user: [Quick Start](Quick-Start)
+- Installation choices: [Installation](Installation)
+- Product model: [Core Concepts](Core-Concepts)
+- Request-to-evidence flow: [Work Lifecycle](Work-Lifecycle)
+- System boundaries: [Architecture](Architecture)
+- Runtime behavior: [Runtime Architecture](Runtime-Architecture)
+- Source implementation map: [Implementation](Implementation)
+- Run and recover the service: [Operations](Operations)
+- Optional capabilities: [Integrations](Integrations)
+- Diagnose a problem: [Troubleshooting](Troubleshooting)
+- Trust boundaries: [Security Model](Security-Model)
+- Upgrade or publish: [Releases and Upgrades](Releases-and-Upgrades)
+
+## Current baseline
+
+The normal ChatGPT connector uses a bounded 19-tool surface with five preferred facades. Small understood work can go directly from context to patch to verification. Long commands and checks use the managed Process Runtime; separate worktrees are used when concurrency or isolation actually requires them. One Canonical Forge Runtime owns active execution authority, while standalone Recovery remains an independent failure domain.
+
+Plugin capability completeness is deliberately separate from the core Runtime baseline: a plugin can be unavailable without redefining whether repository execution, Process Runtime, or Runtime recovery is correct.
+
+## What belongs where
+
+The Wiki explains stable concepts, architecture, implementation boundaries, and common operator decisions. Exact source contracts, compatibility matrices, tests, and incident procedures remain versioned in the [repository documentation](https://github.com/moretea-labs/forge/tree/main/docs). When Wiki content and repository source disagree, the versioned repository source is authoritative.
+
+## Project links
+
+- [Repository](https://github.com/moretea-labs/forge)
+- [Documentation hub](https://github.com/moretea-labs/forge/blob/main/docs/README.md)
+- [Issues](https://github.com/moretea-labs/forge/issues)
+- [Support](https://github.com/moretea-labs/forge/blob/main/SUPPORT.md)
+- [Security policy](https://github.com/moretea-labs/forge/blob/main/SECURITY.md)