legal: audit LICENSE and NOTICE for the first release artifacts

[M4n5ter]

English

Part of #2974 — G3: release legal files.

Outcome

Make the legal files match the exact contents of the Apache source release and
the required npm and Desktop convenience artifacts.

Exit criteria

• Inventory third-party material separately for the source, npm, macOS, and
  Windows artifacts.
• Confirm that every artifact's LICENSE contains the Apache License 2.0
  text and only the additional licensing information required by its contents.
• Keep Category B binary-only material out of the source release and label
  it prominently in each convenience artifact where inclusion is permitted.
• Reject Category X material from every source and convenience artifact.
• Rewrite NOTICE in ASF form and retain only notices legally required by
  the exact contents of each artifact.
• Verify generated notices cannot leak licensing information between source,
  npm, and platform-specific Desktop artifacts.
• Obtain the required human and mentor/legal review of the complete artifact
  matrix.
• Update DISCLAIMER-WIP when its NOTICE disclosure is no longer true.

Existing work

• docs: declare the bundled Geist webfonts in LICENSE #3140 and fix(licenses): regenerate the notices after the bundled-font declaration #3155 are useful historical work on font licensing and generated
  notices, but do not perform this artifact-specific audit.
• docs: add DISCLAIMER-WIP for podling releases #3141 added the current DISCLAIMER-WIP disclosure.

Out of scope

• Adding ASF headers or RAT.
• Implementing npm/Desktop packaging behavior beyond the legal-file boundary.
• Choosing the technical replacement for bundled Git.

References

• ASF release policy
• ASF third-party license policy
• Incubator distribution guidelines

Ownership

Leave this issue unassigned until someone explicitly claims the complete
artifact-specific review. Prior work in this area does not imply ownership.

简体中文

#2974 的一部分——G3：发行包法律文件。

目标结果

使法律文件与 Apache 源码 release，以及要求同时发布的 npm 和 Desktop convenience
artifacts 的实际内容完全匹配。

完成条件

• 分别盘点源码、npm、macOS 和 Windows artifacts 中实际包含的第三方材料。
• 确认每个 artifact 的 LICENSE 包含 Apache License 2.0 全文，并且只增加其实际
  内容所要求的许可证信息。
• Category B binary-only 材料不能进入源码 release；在允许进入 convenience
  artifact 时必须显著标注。
• 从全部源码和 convenience artifacts 中拒绝 Category X 材料。
• 按 ASF 格式重写 NOTICE，只保留每个 artifact 的精确内容依法必须携带的 notice。
• 验证自动生成的 notices 不会在源码、npm 和平台特定 Desktop artifacts 之间泄漏
  不属于对方的许可证信息。
• 对完整 artifact 矩阵取得所需的人工及 mentor/legal 审查。
• 当 NOTICE 问题解决后，更新 DISCLAIMER-WIP 中不再成立的披露。

已有工作

• docs: declare the bundled Geist webfonts in LICENSE #3140 和 fix(licenses): regenerate the notices after the bundled-font declaration #3155 是字体许可证和生成 notice 的有用历史工作，但没有完成针对该 artifact
  的审计。
• docs: add DISCLAIMER-WIP for podling releases #3141 添加了当前 DISCLAIMER-WIP 的相关披露。

不在范围内

• 添加 ASF headers 或 RAT。
• 实现法律文件边界之外的 npm/Desktop 打包行为。
• 选择 bundled Git 的具体技术替代方案。

参考资料

• ASF 发版政策
• ASF 第三方许可证政策
• Incubator 分发指南

负责人边界

在有人明确认领完整的 artifact-specific 审查前保持 unassigned。此前参与过该区域的工作
不代表自动承担本 issue。

[Astro-Han]

English

Two pieces of incoming third-party material are missing attribution. Recording them here because they advance the first exit criterion (inventory third-party material) without closing this gate. Full evidence is in the code origin audit report on #2907.

One shared cause

scripts/generate-third-party-notices.mjs derives its inventory by walking npm production dependency trees. Vendored source, adapted source, and generated data are therefore invisible to it by construction — not missed by accident — and npm run check:third-party-notices cannot guard what the generator never enumerates. Both gaps below follow from that, and so will the next one.

1. Adapted opencode source

packages/runtime/src/tool-output.ts and packages/runtime/src/edit-replace.ts both state in a header comment that they are adapted from opencode. The statements are accurate and the adaptation is substantial: the truncation helper follows upstream line for line down to its local names and its asymmetric newline accounting, and the escape-normalizing regular expression is identical character for character with its nine branches in upstream order. Maka's additions are real, but the material is a derivative work.

Upstream is MIT, Copyright (c) 2025 opencode, compared at commit fc80874 (the repository now resolves to anomalyco/opencode). "opencode" appears in none of LICENSE, NOTICE, packages/cli/THIRD_PARTY_NOTICES.txt, or the desktop notices, while both files ship in @maka/runtime.

2. models.dev data snapshot

packages/core/src/model-metadata.generated.ts and packages/runtime/src/telemetry/model-pricing.generated.ts are checked-in, shipped derivations of https://models.dev/api.json, together about 27,800 lines. Upstream sst/models.dev is MIT, Copyright (c) 2025 models.dev.

The individual entries are facts and are not themselves copyrightable; what comes from upstream is the selection and arrangement. The generated headers record no snapshot date or revision, so the fixed source cannot currently be identified.

Proposed work

1. Add an attribution block to each adapted file — upstream source, pinned revision, license, copyright — keeping the existing "what changed" prose. These files are mixed-origin, so mark the adapted portion rather than applying a whole-file SPDX identifier; packages/ui/src/astryx-chat-reasoning.tsx is the in-repo precedent.
2. Add LICENSE entries for opencode and models.dev, following the existing trycua/cua format.
3. Have scripts/sync-model-metadata.mjs write the snapshot revision and date into the generated headers.
4. Give the notice generator a checked manual inventory for non-npm sources.

Items 1–3 are mechanical once the wording is agreed. Item 4 is the one that stops this recurring, and it changes a checked artifact's contract, so it deserves its own review.

简体中文

有两处引入的第三方材料缺少署名。记录在此是因为它们推进了第一条完成条件（盘点第三方材料），但并不关闭这个 gate。完整证据在 #2907 的代码来源审计报告中。

共同根因

scripts/generate-third-party-notices.mjs 通过遍历 npm production 依赖树来生成清单。因此 vendored 源码、改编源码和生成数据在结构上就不可能被它发现——不是偶然遗漏——而 npm run check:third-party-notices 也无法守护生成器从未枚举过的东西。下面两处都源于此，以后新增的也会一样。

1. 改编自 opencode 的源码

packages/runtime/src/tool-output.ts 和 packages/runtime/src/edit-replace.ts 的文件头注释都写明改编自 opencode。这两处陈述准确，且改编程度很深：截断函数与上游逐行对应，连局部变量名和非对称的换行计数都一致；转义归一化的正则逐字符相同，九个分支的顺序也与上游一致。Maka 确有自己的增强，但这些材料构成 derivative work。

上游为 MIT，Copyright (c) 2025 opencode，比对基于 commit fc80874（该仓库现已指向 anomalyco/opencode）。而 LICENSE、NOTICE、packages/cli/THIRD_PARTY_NOTICES.txt 和 desktop notices 中都没有出现 "opencode"，这两个文件却随 @maka/runtime 一起分发。

2. models.dev 数据快照

packages/core/src/model-metadata.generated.ts 和 packages/runtime/src/telemetry/model-pricing.generated.ts 是 https://models.dev/api.json 的派生结果，已入库并随产品分发，合计约 27,800 行。上游 sst/models.dev 为 MIT，Copyright (c) 2025 models.dev。

其中单条记录属于事实，本身不受版权保护；来自上游的是选择与编排。生成文件头也没有记录快照日期或上游修订，因此目前无法确定固定来源。

建议的工作

1. 为每个改编文件添加署名块——上游来源、固定修订、许可证、版权——并保留现有的"改动了什么"说明。这些文件来源混合，因此应标注被改编的部分，而不是给整个文件打 SPDX 标识；packages/ui/src/astryx-chat-reasoning.tsx 是仓库内已有的先例。
2. 在 LICENSE 中添加 opencode 和 models.dev 条目，格式参照现有的 trycua/cua。
3. 让 scripts/sync-model-metadata.mjs 把快照修订和日期写入生成文件头。
4. 为 notice 生成器提供一份受检的非 npm 来源手工清单。

第 1–3 项在措辞确定后属于机械工作。第 4 项才是阻止此类问题重演的那一项，且它改变了受检 artifact 的契约，应当单独评审。

[Astro-Han]

Guarding the attribution is not in #3325.

#3325 lands the attribution itself — LICENSE entries and in-file notices for the adapted opencode sources and the models.dev snapshot. It does not add anything that fails when an attribution is dropped.

The generator is structurally blind here: it walks npm production dependency trees, and none of this material is an npm package. Two designs were tried and both were rejected in review — restating the inventory in code creates a second authority that drifts from LICENSE, and parsing LICENSE imposes an undocumented grammar on a legal file that a human edits.

What a working guard needs is a per-artifact declaration. The CLI package and the desktop app carry different material — the fonts and the cursor overlay are desktop-only — and today no single place says which artifact carries what; that knowledge is split across electron-builder.config.mjs, release-cli-package.mjs, and the npm closure. Until that exists, any check either over-claims in the CLI notice or has to be hand-maintained.

Filing this as the remaining half of the G3 exit criterion rather than stretching #3325 to cover it.