@mudssky/trellis 0.6.16-mudssky.5

package/AGENT_INSTALL.md

@@ -0,0 +1,100 @@
+# Install and migrate to the personal Trellis CLI
+
+This is the installation entry for `@mudssky/trellis`, executable **`mtrellis`**, maintained by mudssky. It is not the official `@mindfoldhq/trellis` package and not the historical `.4` project patch archive. The prepared release is `0.6.16-mudssky.5`, with upstream project template baseline `0.6.16` and explicit npm channel `latest`. These instructions do not assert that npm publication has already occurred.
+
+## Install without replacing the official CLI
+
+After the desired version is published and verified, the user may explicitly authorize a global installation:
+
+```bash
+npm install --global @mudssky/trellis@latest --registry=https://registry.npmjs.org/
+mtrellis --version
+mtrellis --help
+```
+
+For a pinned install use `@mudssky/trellis@0.6.16-mudssky.5` instead of `@latest`. For pre-publication testing install the exact local npm tarball produced by `prepare-release.py` into an isolated prefix; see [README.md](./README.md). A fork checkout, Git URL or Gitea patch archive is not an installable substitute for this npm tarball.
+
+Coding Agents must not silently install globally, replace a user's CLI, publish, or inspect credentials. Prefer a fresh isolated prefix for evaluation. On POSIX an npm prefix places executables in `<prefix>/bin`; on Windows they are under `<prefix>`. Add only the chosen prefix to the current process PATH when testing generated command instructions.
+
+`mtrellis` is the only personal executable. Existing official `trellis` and `tl` remain untouched and can coexist. Do not alias `trellis` to the personal binary or fall back to official `trellis` when `mtrellis` is missing; install/select the intended distribution explicitly.
+
+## New projects
+
+From the project root, inspect existing files and use the normal initialization UI:
+
+```bash
+mtrellis init
+mtrellis configure
+mtrellis status
+```
+
+Use `mtrellis init --help` to select supported host flags or noninteractive options. The normal complete workflow and subagent capabilities are retained. Integration controls currently cover Pi, OMP, Codex, Claude and ZCode; unsupported platforms and external/global resources are described in [INTEGRATION.md](./INTEGRATION.md).
+
+## Existing upstream projects
+
+1. Inspect the target project's status and preserve a recoverable snapshot of relevant project configuration. Do not discard uncommitted changes or overwrite user-managed resources.
+2. Confirm the target `.trellis/.version` and read `mtrellis update --help`. Projects newer than the selected personal template baseline must wait for a matching personal release; never force a downgrade.
+3. Preview with `mtrellis update --dry-run`. Review proposed changes, especially user-modified templates and mixed host settings.
+4. Run `mtrellis update` and resolve conflicts through the normal update choices. Do not automatically pass force/overwrite flags.
+5. Use `mtrellis status`, then `mtrellis configure` to set desired integration preferences. Verify in newly started host sessions.
+
+The release version reported by `mtrellis --version` is not the project baseline: `.trellis/.version` remains `0.6.16` for this release. A same-baseline update may still introduce personal template changes; inspect its preview rather than assuming no work based on the version string.
+
+## Migrate prior downstream patch projects (.1–.4)
+
+Historical patch bundles were applied **after** official Trellis initialization. The personal CLI now owns the downstream templates directly: do not keep running `apply.py` after personal updates.
+
+Before migration obtain the **exact archive originally applied to this project**, including its `BASE`, `patches/`, `files/`, `apply.py` and metadata. A current/latest bundle is not interchangeable merely because it has the same upstream baseline. If the original archive cannot be identified, stop and reconstruct provenance through the user's records; never guess or force.
+
+1. Preserve the original archive outside the project, inspect repository changes, and take a recoverable project snapshot. Extract the trusted archive into a fresh private directory, never directly over the project. Inspect members first: only expected relative paths, no links or traversal.
+2. Check that archive `BASE` (without the leading `v`) exactly equals target `.trellis/.version`.
+3. With that archive's `apply.py`, inspect current patch status:
+
+   ```bash
+   python3 /absolute/original-bundle/apply.py --target /absolute/project --check
+   ```
+
+   On Windows use `python`. Proceed only when the originally installed patches are `applied` or `empty`. `drift` means user changes or a different baseline: stop and reconcile manually without overwriting whole files. `pending` may indicate an incomplete/historical patch state; understand it before proceeding.
+
+4. Reverse using that same archive:
+
+   ```bash
+   python3 /absolute/original-bundle/apply.py --target /absolute/project --reverse
+   python3 /absolute/original-bundle/apply.py --target /absolute/project --check
+   ```
+
+   After reversal all statuses must be `pending` or `empty`; any `applied` means reversal is incomplete, and `drift` requires a stop. The check returns 1 when patches are pending, so inspect statuses, not merely the exit code. Do not use `--force` to bulldoze local modifications.
+
+5. From the target project run `mtrellis update --dry-run`, review, then `mtrellis update`. **Do not insert official `trellis update` or reapply the old patch archive afterward.** Inspect template updates and resolve normal user-modification conflicts deliberately.
+6. Check `mtrellis status`, configure the desired hosts, and test new host sessions. Preserve project tasks/spec/workspace and unrelated host configuration. Keep the original archive as historical evidence rather than replacing it with the npm package.
+
+Rollback is a deliberate return to the saved project snapshot and original installation path, not arbitrary reverse-patching personal templates. `.4` remote tags and attachments remain unchanged.
+
+## Project update versus CLI upgrade
+
+```bash
+# Update templates/configuration in the current project, preserving personal switch preferences.
+mtrellis update --dry-run
+mtrellis update
+
+# Inspect the CLI's own upgrade command; installation changes require authorization.
+mtrellis upgrade --help
+```
+
+`mtrellis upgrade` upgrades the **personal npm package**, using `latest` by default, not the official package and not a channel inferred from `-mudssky.N`. A manually pinned package install is also supported. Neither CLI self-upgrade nor installation automatically updates every project.
+
+Both official and personal CLIs share `.trellis` state in a given project. Official `trellis update` does not understand personal integration state and can replace personal templates or expose disabled resources. Once migrated, use **`mtrellis update`** for that project. Keep official CLI usage in other projects or deliberately migrate back from a saved snapshot; coexistence of commands does not imply safe alternating updates.
+
+## Recovery and source availability
+
+When all Trellis project integrations are off, recovery remains available through the external CLI:
+
+```bash
+mtrellis status
+mtrellis enable --dry-run
+mtrellis enable -y
+```
+
+Do not delete `.trellis/.integration` or parked resource entries. Existing sessions retain already injected context; reload or start fresh sessions as requested. Global/plugin copies are outside project ownership.
+
+Every personal npm artifact includes `corresponding-source.tar.gz`, both original licenses/attribution and exact build instructions in [README.md](./README.md). Public recipients do not need access to the maintainer's intranet Gitea to inspect or rebuild the corresponding source.

package/COPYRIGHT

@@ -0,0 +1,15 @@
+Trellis - All-in-one AI framework & toolkit for Claude Code & Cursor
+Copyright (C) 2026 Mindfold LLC
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU Affero General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU Affero General Public License for more details.
+
+You should have received a copy of the GNU Affero General Public License
+along with this program. If not, see <https://www.gnu.org/licenses/>.

package/INTEGRATION.md

@@ -0,0 +1,140 @@
+# Trellis 项目集成开关
+
+这组开关控制当前项目如何向 Agent 宿主暴露 Trellis，不改变 Plan / Execute / Finish 工作流，也不取消启用状态下的 subagent 和质量检查。
+
+个人发行包为 `@mudssky/trellis`，唯一可执行命令为 **`mtrellis`**。旧的 `0.6.16-mudssky.4` 补丁附件不包含这些 CLI 命令；仅把 fork 加为 submodule 也不会安装个人 CLI。安装、现有项目与旧补丁迁移见 [AGENT_INSTALL.md](./AGENT_INSTALL.md)，打包、发布和内嵌对应源码重建见 [README.md](./README.md)。文档中的版本与流程不代表已经完成远端 npm 发布。
+
+## 使用个人 CLI
+
+安装经过验证的 npm 发行包后，在需要配置的项目根目录运行：
+
+```bash
+mtrellis configure
+```
+
+个人 `mtrellis` 与官方 `trellis` / `tl` 可以并装，但同项目仍共享 `.trellis`。官方 `trellis update` 不理解个人集成状态，不保证保留停用行为；迁移后请使用 `mtrellis update`。CLI 自身升级使用个人包的 `latest`，项目模板基线仍为 `0.6.16`，不是个人发行号 `0.6.16-mudssky.5`。
+
+源码开发仍保留上游包名：在 fork 根目录 `pnpm install --frozen-lockfile`、`pnpm build` 后，可用 `node /absolute/fork/packages/cli/bin/trellis.js configure`。未经过个人发行打包的源码 CLI 默认命令身份仍为 `trellis`；验证个人身份和生成指引应使用安装后的个人 npm 产物，而非将源码运行当作发行验收。
+
+## 勾选式界面
+
+```bash
+mtrellis configure
+```
+
+复用现有 Inquirer 终端问答，不另起全屏 TUI。按界面提示使用方向键和空格选择、Enter 确认。界面列出当前项目已配置的宿主，提供能力调整、整体停用、恢复和状态查看；写入前显示变更摘要，取消不保存。
+
+- Skills 和 Hooks 可以分别选择。
+- 总开关会遮蔽分项偏好，不将它们重写为 false；恢复后仍使用原偏好。
+- 未适配宿主不会被当作已关闭；界面和状态输出会说明限制。
+- 手工修改 YAML 后，通过配置界面的应用操作使宿主资源与配置对齐。
+
+## 非交互命令
+
+```bash
+mtrellis status
+mtrellis status --json
+
+mtrellis disable --dry-run
+mtrellis disable -y
+mtrellis enable -y
+
+mtrellis disable --platform pi,omp --hooks -y
+mtrellis enable --platform pi,omp --hooks -y
+
+mtrellis disable --platform codex --skills -y
+mtrellis enable --platform codex --skills -y
+```
+
+- 不指定 `--platform`：操作当前项目的公共默认设置；不安装新宿主。
+- 不指定 `--skills` / `--hooks`：修改总开关。
+- 指定能力标志：只改变该能力偏好，不隐式打开总开关。
+- `--dry-run` 只做计划与冲突检查，不写配置或恢复记录。
+- 非交互写操作必须显式 `-y`；状态和预览不需要。
+- `status --json` 用于脚本，区分期望配置、资源应用状态和限制；不是正在运行的宿主已经热卸载的证明。
+
+`--platform` 使用稳定平台 ID：`pi`、`omp`、`codex`、`claude-code`、`zcode`。其中 Claude 的 ID 是 `claude-code`，与初始化时的 `--claude` 选项名称不同。
+
+## 项目配置
+
+配置保存在 `.trellis/config.yaml`。省略 `integration` 时保持原有全部启用行为。
+
+```yaml
+integration:
+  enabled: true
+  skills: true
+  hooks: true
+  platforms:
+    omp:
+      hooks: false
+    codex:
+      skills: false
+```
+
+公共总开关 `integration.enabled: false` 优先于一切宿主覆盖。宿主的 `enabled: false` 关闭该宿主；宿主 skills/hooks 覆盖公共分项默认值，但不能越过总开关。
+
+配置是期望状态。手改 YAML 后需要应用；不要以“文件已经改了”判断所有宿主资源已经撤下。CLI 不会修改用户全局配置，因此也不会关闭其他项目。
+
+## 关闭、恢复与升级
+
+- 独立关闭 skills/hook 不修改其他能力的偏好。
+- 整体关闭包括该宿主的受管 commands/agents；共享静态 Trellis 指引仅在相关受管宿主都关闭后处理。
+- 只处理 Trellis 已确认拥有的字段、块和发现入口；不按文件名前缀批量删除用户文件。
+- `.trellis/tasks`、`spec`、`workspace` 与用户自写规则保持原位。
+- 恢复只处理本工具改过的内容，保留关闭期间添加的无关配置；同一受管位置发生冲突时停止，不强制覆盖。
+- 重复开关不会叠加恢复快照。
+- 使用个人版 `mtrellis init` / `mtrellis update` 时继续遵循关闭偏好，不使用 `update.skip` 冻结旧模板。
+- 官方和旧版 CLI 不认识这份策略；不要交替用它们更新已配置新开关的项目。
+
+恢复记录位于 `.trellis/.integration/state.json`，私有入口保存在 `.trellis/.integration/parked/`，共享技能的隐藏入口保留在原技能目录。不要手工删除这些内容。如果要共享已停用的项目状态，配置、恢复记录和对应入口必须一起保留。记录不复制完整混合设置文件，但可能包含你自定义的受管 hook 命令或 Agent 文本；提交前仍需检查敏感信息。
+
+## 会话和外部来源边界
+
+本功能是项目级持久开关，不是仅当前会话的开关。同项目其他会话可能读取新配置。
+
+关闭不会抹除已注入的上下文。按 CLI 提示重载，或新建 Agent 会话验证最终状态。不要为了“热卸载”重写历史消息或清空会话。
+
+全局安装的同名 skills、插件、全局 hooks、管理策略等不属于项目受管资源。它们即使在项目关闭后仍可能可用；状态或文档列出的外部来源需在对应宿主里单独处理，不会被静默修改。
+
+已有临时入口的局限：
+
+- `no-trellis`：仅跳过支持入口的当轮 workflow breadcrumb，不隐藏 skills/agents。
+- `TRELLIS_HOOKS=0` / `TRELLIS_DISABLE_HOOKS=1`：支持该入口的 hooks 停止逻辑；不是删除注册，不移除旧上下文。
+- shell 子进程设置环境变量不能改变已经运行的父 Agent 进程。
+- Pi hooks-only 模式下，显式子代理失败通过原生异常通道报告；Pi 0.85.1 的最终异常结果只保留错误文本，不携带结构化 progress details。默认 hooks-on 的详情展示保持原样。
+
+本次不提供 `--session`、全局开关或跨宿主热卸载。
+
+## 适配矩阵
+
+下表是本功能的适配边界，不是 Trellis 原有平台支持清单。宿主版本差异仍应通过实际加载结果确认。
+
+| 宿主   | Skills                     | Hooks                  | Commands / Agents | 生效和限制                                                          |
+| ------ | -------------------------- | ---------------------- | ----------------- | ------------------------------------------------------------------- |
+| Pi     | 宿主资源过滤               | 扩展集成策略           | 随总开关处理      | hooks-only 保留显式子代理工具；新会话验证                           |
+| OMP    | 原生技能过滤               | 扩展事件注册策略       | 随总开关处理      | 多来源技能需区分项目受管项；新会话验证                              |
+| Codex  | 项目内可逆隐藏共享技能入口 | 精确处理受管 hook 注册 | 随总开关处理      | 不写用户配置；为仍启用的 Pi 添加显式项目内入口                      |
+| Claude | 逐技能配置                 | 精确处理受管 handler   | 随总开关处理      | plugin skills 不受普通 skillOverrides 控制                          |
+| ZCode  | 受管发现入口               | 精确处理 hooks.events  | 随总开关处理      | 不使用 hooks.enabled 关闭所有 hooks；外部补丁插件不在本项目控制范围 |
+
+Codex 0.153.4 的原生探针显示：项目 `skills.config` 虽进入有效配置，技能仍被标记为启用；用户配置中的同项才生效。为坚持项目内修改，本功能可逆地将受管 `SKILL.md` 隐藏为同目录入口文件，并让仍启用的 Pi 显式加载该文件。目录中的 scripts/references 保持原位置，不复制技能正文；恢复时还原标准入口。若有未适配宿主依赖同一共享入口，操作会在写入前拒绝并说明原因，不以停用 Codex 为代价悄悄关闭其他宿主。
+
+当前配置解析使用受限的块式 YAML，不接受 `integration: { enabled: false }` 等行内映射或带引号的布尔值。OMP 的 `skills.ignoredSkills` 需要两空格键缩进的块式列表；行内列表等形态会在写入前报错，不会猜测或覆盖。这些格式扩展可在后续适配中补齐。
+
+### 尚未适配新开关的宿主
+
+Cursor、OpenCode、Kilo、Kiro、Gemini、Antigravity、Devin、Qoder、CodeBuddy、Copilot、Factory Droid、DeepSeek Harness、Trae、Reasonix、Grok、Kimi Code、Snow。
+
+这些宿主仍可使用原有 Trellis 功能，但新开关不能被当作已经覆盖它们。当前项目包含这些宿主时，不能将“支持的五个宿主已停用”理解为整个项目没有任何 Trellis 自动入口。
+
+### 后续补齐位置与验收
+
+- 平台枚举与配置根：`packages/cli/src/types/ai-tools.ts`、`configurators/index.ts`。
+- 开关配置、状态、变更计划与适配：`packages/cli/src/utils/integration.ts` 及同目录的集成实现。
+- CLI / 勾选界面：`packages/cli/src/commands/integration.ts`。
+- Pi / OMP 运行时：`packages/cli/src/templates/pi/extensions/trellis/index.ts.txt`、`packages/cli/src/templates/omp/extensions/trellis/index.ts.txt`；同时保持 fork 自身对应 `.pi` / `.omp` 扩展文件一致。
+- ZCode 受管输出：`packages/cli/src/configurators/zcode.ts`；注意部分版本的全局 hook fallback 插件。
+
+新增适配必须记录宿主版本、资源发现来源、停用机制、恢复行为、是否需重启，以及未支持项的原因。至少覆盖 skills-only、hooks-only、整体关闭、恢复、保留非 Trellis 邻居、共享资源隔离、关闭后 update 的场景。仅解析配置或脚本无输出不能作为真实宿主加载验收。
+
+未适配的跨五宿主会话热卸载，需先确认各宿主的会话级 API；不能通过改项目文件实现后声称只影响当前会话。

package/LICENSE

@@ -0,0 +1,235 @@
+GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+                            Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+                       TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     <one line to give the program's name and a brief idea of what it does.>
+     Copyright (C) <year>  <name of author>
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
+
+     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.