frontend-project-context 1.0.0

package/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+## 1.0.0 — release candidate
+
+- 冻结 model-neutral Project Contract、来源追溯、scope compiler、Context Bundle 和受管投影边界。
+- 提供通用来源登记、四类 item、三类 scope、显式批准和知识维护闭环。
+- 提供只读中英双语治理看板、schema 2 View Model 与 renderer 3。
+- 加固路径写入、verification schema、同 ID revision、原子失败恢复和输出精简。
+- 增加 Contract schema 2 的 active/deprecated source 生命周期、显式 `deprecate-source`、schema 1 延迟迁移和 deprecated provenance 保留。
+- Dashboard View Model 升为 schema 3；deprecated source 不再读取已退役 locator，并显示双语审计信息。
+- 以 `Copyright 2026 Fushan` 采用 Apache License 2.0，并把 LICENSE/NOTICE 纳入发布包。
+- A-01 至 A-45、B0-01/B0-02 与 CLI 共 49 项本地验收通过。
+
+公开 npm 发布已获授权并固定为 public access；npmjs.org CLI 身份已验证，当前进入最终发布。

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,4 @@
+Frontend Project Context
+Copyright 2026 Fushan
+
+This product is licensed under the Apache License, Version 2.0.

package/PROJECT_STATE.json

@@ -0,0 +1,176 @@
+{
+  "schemaVersion": 43,
+  "status": "1.0.0-public-npm-release-ready",
+  "product": {
+    "name": "Frontend Project Context",
+    "identity": "A project-local, model-neutral context governance and compilation layer between a repository and existing AI coding tools.",
+    "promise": "Maintain one human-approved project contract with provenance, compile scoped context for existing AI tools, and detect source, contract, and projection drift.",
+    "kernel": [
+      "source-registration-and-provenance",
+      "human-governed-project-contract",
+      "scope-aware-context-compiler",
+      "tool-projection-boundary",
+      "conflict-and-drift-checking"
+    ],
+    "discoveryRole": "Optional conservative bootstrap; never a requirement to understand every frontend technology or project convention."
+  },
+  "hardBoundaries": {
+    "humanAuthority": "Only an explicit human action may approve or change normative contract content.",
+    "runtime": "No model Provider or agent loop.",
+    "businessCode": "No user development task execution or application-code edits.",
+    "git": "No Git state management.",
+    "externalEffects": "No automatic dependency installation, network access, external mutation, or shell workflow execution.",
+    "generatedFiles": "Only explicitly managed and still-owned projections may be overwritten after an explicit write action.",
+    "conflicts": "Report stale sources and conflicts; never silently resolve or promote them.",
+    "taskContext": "Ephemeral task constraints cannot expand authority or rewrite the persistent Contract."
+  },
+  "implementation": {
+    "version": "1.0.0",
+    "license": "Apache-2.0",
+    "copyright": "Copyright 2026 Fushan",
+    "entrypoint": "bin/project-context.mjs",
+    "modules": "src/project-context/",
+    "tests": "test/project-context/",
+    "runtime": "node-standard-library-only",
+    "dependenciesAdded": 0,
+    "schemas": {
+      "contract": 2,
+      "contractReadable": [
+        1,
+        2
+      ],
+      "proposal": 1,
+      "sourceLock": 1,
+      "projectionLock": 1,
+      "projectionRenderer": 3,
+      "dashboardViewModel": 3
+    },
+    "closures": [
+      "v1-authoring",
+      "knowledge-maintenance",
+      "read-only-governance-dashboard",
+      "context-efficiency-and-governance-hardening",
+      "formal-release-readiness",
+      "source-lifecycle"
+    ],
+    "hardening": [
+      "symlink-safe-parent-creation",
+      "verification-kind-schema-semantics",
+      "proposal-create-only-same-id-revision-guard",
+      "strict-contract-value-json-compatibility",
+      "grouped-multipath-context-rendering",
+      "primary-locale-context-with-explicit-en-or-all",
+      "compact-approval-json-receipt",
+      "dashboard-derived-data-deduplication",
+      "deprecated-source-io-suppression",
+      "projection-lock-snapshot-precondition"
+    ],
+    "acceptance": {
+      "command": "npm run check",
+      "range": "A-01-through-A-45-plus-B0-01-B0-02-and-CLI",
+      "testCount": 49,
+      "status": "passed-source-lifecycle-closure-local",
+      "teamMaintenance": {
+        "date": "2026-09-08",
+        "fixture": "isolated-temporary-project",
+        "workflow": "source-change-review-accept-revise-deprecate-reapprove-republish-final-check",
+        "result": "passed"
+      },
+      "releaseReadiness": {
+        "date": "2026-09-08",
+        "package": "frontend-project-context@1.0.0",
+        "publicSurface": "project-context-cli",
+        "packagePrivate": false,
+        "registry": "https://registry.npmjs.org/",
+        "access": "public",
+        "license": "Apache-2.0",
+        "result": "public-release-configured-authenticated-ready"
+      }
+    },
+    "compatibility": "Contract schema 1 and 2 are readable. Existing schema-1 stores remain byte-stable until the first successful deprecate-source write lazily upgrades the Contract to schema 2; proposal and both locks remain schema 1. Renderer 1 and 2 projections remain readable and stale until explicit owned republish to renderer 3. Dashboard JSON consumers must opt into View Model schema 3; --full-json preserves the former verbose approval result on demand."
+  },
+  "planning": {
+    "releaseBlocker": {
+      "id": "source-lifecycle-closure",
+      "classification": "kernel-defect",
+      "targetPackageVersion": "1.0.0",
+      "status": "implemented-local-verified-release-hold-resolved",
+      "design": "docs/15-SOURCE-LIFECYCLE-CLOSURE-DESIGN.md",
+      "evidence": [
+        "accept-source-change rejects missing or unreadable registered sources",
+        "register rejects a changed locator under an existing source ID",
+        "contract schema 1 has no safe source retirement state",
+        "a missing, relocated, or retired source therefore requires direct store editing to return check to clean"
+      ],
+      "frozenScope": [
+        "contract-schema-2-active-and-deprecated-source-lifecycle",
+        "explicit-deprecate-source-command",
+        "schema-1-lazy-compatibility-migration",
+        "checker-dashboard-context-and-publish-lifecycle-consistency",
+        "A-40-through-A-45"
+      ],
+      "result": {
+        "date": "2026-09-08",
+        "tests": 49,
+        "contractSchemasReadable": [
+          1,
+          2
+        ],
+        "contractSchemaWrittenByLifecycle": 2,
+        "dashboardViewModel": 3,
+        "selfHostedContractSchema": 1,
+        "selfHostedMigrationReason": "No self-hosted source is obsolete; schema 1 remains valid until a real source retirement requires lazy migration."
+      }
+    },
+    "laterCandidates": [
+      {
+        "id": "ci-reconciliation-artifacts",
+        "classification": "optional-adapter",
+        "status": "candidate-after-release-decision",
+        "boundary": "Reuse check and dashboard in external CI; do not add a scheduler, daemon, automatic acceptance, or approval."
+      },
+      {
+        "id": "targeted-context-consumer-protocol",
+        "classification": "optional-adapter",
+        "status": "candidate-requires-separate-design-authorization",
+        "boundary": "Coding Agent or IDE resolves candidate paths and consumes context --path; no Provider, Agent Runtime, business-code execution, or automatic authority expansion."
+      }
+    ]
+  },
+  "executionAuthority": {
+    "providerCallsAllowed": false,
+    "dependencyInstallationAllowed": false,
+    "networkAllowed": true,
+    "productImplementationAllowed": false,
+    "realProjectBetaAllowed": false,
+    "teamAcceptanceAllowed": false,
+    "releaseWorkAllowed": true,
+    "gitWriteOperationsAllowed": true,
+    "note": "The user authorized completing the public release and npmjs.org CLI authentication is verified as fushanyx1. Public npm visibility, private:false, release verification, Git release commit/tag/push, and npm publication are in scope for this release workflow. Provider calls, dependency installation, real-project access, and product expansion remain unauthorized."
+  },
+  "sourceOfTruth": {
+    "constitution": "docs/00-PRODUCT-CONSTITUTION.md",
+    "startup": "RTK.md",
+    "overview": "README.md",
+    "documentationIndex": "docs/README.md",
+    "programDesign": "docs/04-PROGRAM-DESIGN.md",
+    "acceptanceContract": "docs/05-ACCEPTANCE-CONTRACT.md",
+    "v1AuthoringClosureDesign": "docs/11-V1-AUTHORING-CLOSURE-DESIGN.md",
+    "knowledgeMaintenanceClosureRoadmap": "docs/12-KNOWLEDGE-MAINTENANCE-CLOSURE-ROADMAP.md",
+    "readOnlyGovernanceDashboardDesign": "docs/13-READ-ONLY-GOVERNANCE-DASHBOARD-DESIGN.md",
+    "formalReleaseReadiness": "docs/14-FORMAL-RELEASE-READINESS.md",
+    "sourceLifecycleClosureDesign": "docs/15-SOURCE-LIFECYCLE-CLOSURE-DESIGN.md",
+    "license": "LICENSE",
+    "notice": "NOTICE",
+    "installationAndDistribution": "docs/08-INSTALLATION-AND-DISTRIBUTION.md",
+    "historicalEvidence": [
+      "docs/06-HISTORICAL-PROTOTYPE.md",
+      "docs/07-REAL-TASK-EVIDENCE.md",
+      "docs/09-B0-DTG-TMC-MOBILE.md",
+      "docs/10-B0-DTG-TMC-PC.md"
+    ]
+  },
+  "next": [
+    "publish-frontend-project-context-1.0.0-to-public-npm"
+  ]
+}

package/README.md

@@ -0,0 +1,148 @@
+# Frontend Project Context
+
+Frontend Project Context 是位于前端项目与 AI 编程工具之间的模型无关上下文层。
+
+[产品宪法](./docs/00-PRODUCT-CONSTITUTION.md)是产品身份、边界、完成条件和变更规则的唯一规范真源。
+
+它把分散在设计资料、文档、配置、代码和团队约定中的项目知识，整理成一份有来源、有人负责批准的 `Project Contract`，再为不同 Coding Agent 生成一致的项目上下文，并检查规则漂移。
+
+```text
+项目事实与人工规范
+→ Project Contract（唯一真源）
+→ Context Compiler
+→ AGENTS.md / Ruler / Kiro / 其他 Agent
+→ Drift Check
+```
+
+## 产品核心
+
+- **Register / Discover**：登记项目明确提供的来源；自动发现只负责保守地提出接入候选，不尝试理解所有前端技术。
+- **Govern**：人类确认哪些内容是事实、规范或参考样例；AI 不能自行批准长期规则。
+- **Compile**：按目录范围和任务目标生成最小、可追溯的 Context Bundle。
+- **Project**：把同一合同投影到现有 AI 工具，而不是为每个模型维护一套手写规则。
+- **Check**：发现来源变化、合同冲突和生成文件漂移。
+
+## 与现成工具的关系
+
+- [Ruler](https://github.com/intellectronica/ruler) 和 [Rulesync](https://github.com/dyoshikawa/rulesync) 已经覆盖多 Agent 规则分发，本项目不重建完整适配矩阵。
+- [Kiro Steering](https://kiro.dev/docs/steering/) 已经展示项目知识、规则和 Specs 的完整产品体验，本项目保持 Runtime 和模型中立。
+- [GitHub Spec Kit](https://github.com/github/spec-kit) 与 [OpenSpec](https://openspec.dev/) 负责规格驱动的功能开发流程，可以消费本项目上下文，但不属于本项目内核。
+
+本项目只在现有工具前面补一层：**从真实设计和代码中形成有来源、可审查、可按作用域编译的项目合同，并持续检查漂移。**
+
+## 明确不做
+
+- 不调用模型 Provider，也不实现 Coding Agent Runtime。
+- 不执行真实开发任务或自动修复代码。
+- 不管理 Git 分支、commit、merge、push、PR 或部署。
+- 不自动安装依赖或访问外部系统。
+- 不保存 candidate、DecisionRecord 或 DeliveryRecord。
+- 不复制 Kiro、Spec Kit、Ruler 等工具已有的能力。
+
+## 当前状态
+
+```text
+1.0.0-public-npm-release-ready
+```
+
+核心引擎、通用 authoring、knowledge maintenance、只读治理看板和来源生命周期闭环均已完成本地、零第三方依赖实现。`0.9.0` 在不扩大产品边界的前提下加固路径/合同安全，并压缩 Context、CLI JSON、Dashboard 和启动上下文的重复内容。团队维护验收已在隔离 fixture 完整走通来源变化、接受、修订、废弃、重新批准、重新投影和最终检查；加上 A-39 与 A-40 至 A-45，A-01 至 A-45、2 项 B0 回归和 CLI 端到端测试共 49 项均已通过。
+
+正式发布准备已经把上述能力冻结为 `frontend-project-context@1.0.0` 候选包，公共稳定面为 `project-context` CLI。后续重大调整审查发现并已关闭一个发布前缺口：已登记来源被删除、搬迁或永久退役时，现在可用稳定 CLI 完成替代、修订、重新批准、旧来源废弃、重新投影和 clean check，无需手改内部 JSON。
+
+[Source Lifecycle Closure 设计与实现记录](./docs/15-SOURCE-LIFECYCLE-CLOSURE-DESIGN.md) 已按冻结范围落地 Contract schema 2 的 active/deprecated source、显式 `deprecate-source` 命令和 A-40 至 A-45。schema 1 项目继续原样可读，只有首次成功废弃来源时才延迟升级。公开 npm 发布已经获得授权并固定到 `https://registry.npmjs.org/`，发布者 CLI 身份已验证，当前处于最终发布就态。
+
+## 许可证
+
+本项目采用 [Apache License 2.0](./LICENSE)，版权声明见 [NOTICE](./NOTICE)：`Copyright 2026 Fushan`。
+
+本仓库已经使用同一 CLI 初始化 `.project-context/` 自托管真源。收录本次实现后，22 个精确来源和 20 个治理项均经显式批准，`check` 零 finding。根 `AGENTS.md` 继续由人维护，没有被生成投影接管。
+
+只读治理看板仍提供总览、知识、来源、scope、投影、finding 六个视图；默认输出确定性、自包含的离线 HTML，`--json` 输出短生命周期 View Model schema 3，并能双语解释 deprecated source 的负责人、时间与理由。HTML 只包含渲染所需内容，不再重复嵌入整份 View Model。
+
+`0.7.0 — Knowledge Maintenance Closure` 已实现来源变化 review/accept、影响集撤销旧批准、同 ID revision、deprecation、pending reapproval、projection stale 和并发失败封闭。两个真实项目 B0 仍只作为既有证据；本次实现没有访问真实项目。
+
+## 本地使用
+
+```bash
+node bin/project-context.mjs init --project /path/to/project --id project-id --name "Project Name" --write
+node bin/project-context.mjs register --project /path/to/project --id source-package --kind file --path package.json --write
+node bin/project-context.mjs register --project /path/to/project --id source-src --kind path --path src --write
+node bin/project-context.mjs register --project /path/to/project --id source-team --kind human-decision --reference "decision:team" --write
+node bin/project-context.mjs propose --project /path/to/project --id policy-visible-copy --kind policy --subject ui.visible-copy --value required --statement "Use the approved visible-copy convention." --sources source-team --scope path-prefix --scope-path src --output .project-context/policy-visible-copy.proposal.json --write
+node bin/project-context.mjs approve --project /path/to/project --proposal .project-context/policy-visible-copy.proposal.json --ids policy-visible-copy --by NAME --write
+node bin/project-context.mjs discover --project /path/to/project
+node bin/project-context.mjs context --project /path/to/project --path src --locale zh-CN
+node bin/project-context.mjs publish --project /path/to/project --target agents --output AGENTS.md --write
+node bin/project-context.mjs check --project /path/to/project
+node bin/project-context.mjs dashboard --project /path/to/project > project-context-dashboard.html
+node bin/project-context.mjs dashboard --project /path/to/project --json
+```
+
+知识来源发生变化后的维护流程：
+
+```bash
+node bin/project-context.mjs review-source --project /path/to/project --id source-package --json
+node bin/project-context.mjs accept-source-change --project /path/to/project --id source-package --expected-digest SHA256_FROM_REVIEW --affected-items ITEM_ID... --write
+node bin/project-context.mjs revise --project /path/to/project --id ITEM_ID --kind policy --subject SUBJECT --value NEW_VALUE --statement "NEW STATEMENT" --sources source-package --scope project --json
+node bin/project-context.mjs revise --project /path/to/project --id ITEM_ID --expected-item-digest SHA256_FROM_PREVIEW --kind policy --subject SUBJECT --value NEW_VALUE --statement "NEW STATEMENT" --sources source-package --scope project --write
+node bin/project-context.mjs approve --project /path/to/project --pending --ids ITEM_ID... --by NAME --write
+node bin/project-context.mjs publish --project /path/to/project --target agents --output AGENTS.md --write
+node bin/project-context.mjs check --project /path/to/project
+```
+
+来源已经搬迁或永久退役时，先登记替代 source、用 `revise` 和 `approve --pending` 移走全部当前引用，再执行：
+
+```bash
+node bin/project-context.mjs deprecate-source --project /path/to/project --id source-old --by NAME --rationale "Replaced by source-new." --json
+node bin/project-context.mjs deprecate-source --project /path/to/project --id source-old --expected-source-digest SHA256_FROM_PREVIEW --by NAME --rationale "Replaced by source-new." --write
+node bin/project-context.mjs publish --project /path/to/project --target agents --output AGENTS.md --write
+node bin/project-context.mjs check --project /path/to/project
+```
+
+preview 中若 `blockingItems` 非空，必须先处理这些 proposed/approved 引用；命令不会级联改 item 或自动批准。需要退役 item 时，先运行 `deprecate` preview 取得 current item digest，再以同一命令增加 `--expected-item-digest ... --by NAME --rationale TEXT --write`。所有命令默认只读；`init`、`register`、保存 proposal、`accept-source-change`、`revise`、`deprecate`、`deprecate-source`、`approve` 和 `publish` 只有在自身显式包含 `--write` 时才会写文件。
+
+`context` 默认从 `[zh-CN] ...\n[en] ...` statement 中只选择中文主解释；可用 `--locale en` 选择英文，或 `--locale all` 保留双语原文。多条 `--path` 若得到相同知识集，只渲染一个 Targets 分组。`approve --json` 默认返回 digest 和 ID 摘要；只有确实需要完整 next Contract 时才使用 `--full-json`。
+
+验证：
+
+```bash
+npm test
+npm run check
+```
+
+发布候选与升级资料：
+
+- [正式发布准备](./docs/14-FORMAL-RELEASE-READINESS.md)
+- [变更记录](./CHANGELOG.md)
+- [升级说明](./UPGRADING.md)
+- [最小团队接入示例](./examples/README.md)
+
+检查或读取本仓库自身治理上下文：
+
+```bash
+node bin/project-context.mjs check --project .
+node bin/project-context.mjs context --project . --path . --path src/project-context --path docs --locale zh-CN
+node bin/project-context.mjs dashboard --project . > /tmp/frontend-project-context-dashboard.html
+```
+
+现行文档按以下顺序阅读：
+
+1. [产品宪法](./docs/00-PRODUCT-CONSTITUTION.md)
+2. [当前状态](./PROJECT_STATE.json)
+3. [产品核心](./docs/01-PRODUCT-CORE.md)
+4. [市场与自研边界](./docs/02-MARKET-BOUNDARY.md)
+5. [最终产品方案](./docs/03-FINAL-SOLUTION.md)
+6. [v1 程序设计](./docs/04-PROGRAM-DESIGN.md)
+7. [验收合同](./docs/05-ACCEPTANCE-CONTRACT.md)
+8. [v1 authoring closure 设计与实现结果](./docs/11-V1-AUTHORING-CLOSURE-DESIGN.md)
+9. [0.7.0 Knowledge Maintenance Closure 冻结设计与实现记录](./docs/12-KNOWLEDGE-MAINTENANCE-CLOSURE-ROADMAP.md)
+10. [0.8.0 Read-only Governance Dashboard 冻结设计与实现记录](./docs/13-READ-ONLY-GOVERNANCE-DASHBOARD-DESIGN.md)
+11. [1.0.0 正式发布准备](./docs/14-FORMAL-RELEASE-READINESS.md)
+12. [1.0.0 Source Lifecycle Closure 设计与实现记录](./docs/15-SOURCE-LIFECYCLE-CLOSURE-DESIGN.md)
+
+历史任务执行 Harness 的结论和第一次真实业务任务只作为反例与证据保留：
+
+- [历史原型](./docs/06-HISTORICAL-PROTOTYPE.md)
+- [真实任务证据](./docs/07-REAL-TASK-EVIDENCE.md)
+
+当前实现不调用 Provider、网络、shell 或 Git，不执行项目验证，也不修改业务代码。历史 Harness 的源码、入口、测试和任务模板已从工作树清理，可通过 Git 历史追溯。真实项目报告只作为既有能力证据，不能自动产生新的内核需求。

package/RTK.md

@@ -0,0 +1,13 @@
+# Frontend Project Context — 启动路由
+
+按顺序读取：
+
+1. `docs/00-PRODUCT-CONSTITUTION.md`：产品身份、内核、永久边界与治理规则；
+2. `PROJECT_STATE.json`：当前版本、实现、授权和唯一下一步；
+3. 仅在任务需要时读取 `PROJECT_STATE.json.sourceOfTruth` 指向的设计或证据。
+
+当前摘要：`1.0.0-public-npm-release-ready`。v1 已冻结为 `frontend-project-context@1.0.0`，采用 Apache-2.0 与 `Copyright 2026 Fushan`；Source Lifecycle Closure 和全部 49 项本地验收通过。Contract reader 支持 schema 1/2，schema 1 只在首次成功 `deprecate-source --write` 时延迟升级为 2；proposal 与两个 lock 保持 1，projection renderer 为 3，Dashboard View Model 为 3。
+
+根 `AGENTS.md` 由人工维护；`.project-context/` 是本仓库自托管真源；投影只是可重新生成的消费端文件。任何历史文档与宪法冲突时以宪法为准，任何动态状态与 `PROJECT_STATE.json` 冲突时以后者为准。
+
+用户已授权完成公开发布；package 已固定 `private: false`、public access 和官方 npm registry，npmjs.org CLI 身份已验证。当前唯一下一步是完成最终 pack、release commit、`v1.0.0` tag/push 与 `npm publish`。Provider、依赖安装、真实业务项目访问和产品扩张仍未授权。

package/UPGRADING.md

@@ -0,0 +1,15 @@
+# 升级到 1.0.0
+
+从本地 `0.9.0` 升级到 `1.0.0` 不需要预先迁移 Project Contract、proposal、source lock 或 projection lock。Contract reader 同时接受 schema 1/2；既有 schema 1 项目保持原字节，只有首次成功执行 `deprecate-source --write` 时才把所有来源显式标为 active、目标标为 deprecated 并写成 schema 2。proposal、source lock 和 projection lock 继续使用 schema 1。Dashboard JSON 使用 schema 3，projection renderer 使用 3。
+
+建议步骤：
+
+1. 将项目依赖锁定到 `frontend-project-context@1.0.0`。
+2. 运行 `project-context check --project .`，先处理来源、批准或所有权 finding。
+3. 仍使用 renderer 1/2 的受管投影会被报告 stale；确认所有权后显式运行原 publish 命令升级到 renderer 3。
+4. 若脚本消费 dashboard JSON，确认其明确支持 View Model schema 3 和 source `deprecated` 状态。
+5. 运行项目自己的 `context:check`，与依赖和受管投影一起审查 diff。
+
+5. 来源搬迁或永久退役时，先登记替代来源并修订/重新批准所有当前引用，再 preview `deprecate-source`，最后用 preview 返回的 source object digest 显式写入并重新发布投影。
+
+旧 `1.0.0` RC reader 不支持 Contract schema 2，因此成功废弃来源后不能用旧 reader 继续维护该项目。升级不会自动迁移、接受来源变化、修改 item、批准知识、覆盖非受管文件或执行 Git。

package/bin/project-context.mjs

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+import { runCli } from "../src/project-context/cli.mjs";
+
+const result = await runCli(process.argv.slice(2));
+if (result.stdout) process.stdout.write(result.stdout);
+if (result.stderr) process.stderr.write(result.stderr);
+process.exitCode = result.exitCode;