silvermoon 0.1.3-rc.1 → 0.1.3-rc.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -11
- package/README.zh-CN.md +11 -11
- package/docs/npm-package-releases.md +11 -7
- package/package.json +4 -2
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
<p align="center">
|
|
4
4
|
<!-- markdownlint-disable-next-line MD013 -->
|
|
5
|
-
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@
|
|
5
|
+
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@ec4b02387df98c108b30f7266e3711a686249107/assets/silvermoon.svg" width="960" alt="Silvermoon, the artifact spirit of the project">
|
|
6
6
|
</p>
|
|
7
7
|
|
|
8
8
|
<p align="center">
|
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
</p>
|
|
18
18
|
|
|
19
19
|
<p align="center">
|
|
20
|
-
English | <a href="https://github.com/shazhou-ww/silvermoon/blob/
|
|
20
|
+
English | <a href="https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/README.zh-CN.md">简体中文</a>
|
|
21
21
|
</p>
|
|
22
22
|
|
|
23
23
|
# Silvermoon
|
|
@@ -69,14 +69,14 @@ silvermoon whats-next <idea> --language zh-CN
|
|
|
69
69
|
Describe the desired world in the generated `Idea.md`, review it, and approve
|
|
70
70
|
that exact revision. From then on, Silvermoon keeps the goal, implementation,
|
|
71
71
|
repository state, and real-world result connected. See
|
|
72
|
-
[Getting Started](https://github.com/shazhou-ww/silvermoon/blob/
|
|
72
|
+
[Getting Started](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/getting-started.md) for the complete first workflow.
|
|
73
73
|
Default dialogue output uses lightweight Markdown headings for intent,
|
|
74
74
|
observation, and next instructions, plus actions and outcomes only when an
|
|
75
75
|
operation was attempted. Add `--json` only when a programmatic consumer needs
|
|
76
76
|
the `intention / observation / outcomes / instructions` envelope. For
|
|
77
77
|
pre-commit validation, run `silvermoon check --staged`: unlike the default
|
|
78
78
|
`check` (committed `HEAD`), it checks the index and exits `0` only when the
|
|
79
|
-
project snapshot is valid. See the [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/
|
|
79
|
+
project snapshot is valid. See the [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/reference.md)
|
|
80
80
|
for validation targets and exit codes. Add `--trace <file.trace.jsonl>` to any
|
|
81
81
|
command to write paired task and Git timing spans for performance analysis.
|
|
82
82
|
If the argument does not end with the exact lowercase `.trace.jsonl` suffix,
|
|
@@ -89,7 +89,7 @@ Projects may optionally add `.silvermoon/guidance/preparing.md`,
|
|
|
89
89
|
actionable phase's snapshot-bound, repository-owned Markdown after canonical
|
|
90
90
|
instructions; `create-idea` can return preparing guidance. This guidance is
|
|
91
91
|
additive, never a fourth contract or decision fact, and `check` validates the
|
|
92
|
-
complete fixed directory. See [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/
|
|
92
|
+
complete fixed directory. See [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/core-concepts.md).
|
|
93
93
|
|
|
94
94
|
## Why Silvermoon
|
|
95
95
|
|
|
@@ -119,7 +119,7 @@ sessions, Agents, and hosting platforms.
|
|
|
119
119
|
<tr>
|
|
120
120
|
<td width="160" align="center" valign="top">
|
|
121
121
|
<!-- markdownlint-disable-next-line MD013 -->
|
|
122
|
-
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@
|
|
122
|
+
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@ec4b02387df98c108b30f7266e3711a686249107/assets/silvermoon-avatar.svg" width="128" alt="Line portrait of Silvermoon, the project's artifact spirit">
|
|
123
123
|
</td>
|
|
124
124
|
<td valign="top">
|
|
125
125
|
Silvermoon is named after a character in <em>A Record of a Mortal's
|
|
@@ -167,13 +167,13 @@ the project, not to a fleeting conversation.
|
|
|
167
167
|
|
|
168
168
|
## Further Reading
|
|
169
169
|
|
|
170
|
-
- [Getting Started](https://github.com/shazhou-ww/silvermoon/blob/
|
|
170
|
+
- [Getting Started](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/getting-started.md) — installation, configuration,
|
|
171
171
|
and the first idea.
|
|
172
|
-
- [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/
|
|
172
|
+
- [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/core-concepts.md) — project ownership, the three
|
|
173
173
|
worlds, revisions, and decision boundaries.
|
|
174
|
-
- [Operating Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/
|
|
174
|
+
- [Operating Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/operations.md) — navigation, creation,
|
|
175
175
|
publication, hygiene, and continuation.
|
|
176
|
-
- [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/
|
|
176
|
+
- [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/reference.md) — storage, derived state, CLI
|
|
177
177
|
reports, validation targets, and schemas.
|
|
178
|
-
- [Maintaining Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/
|
|
178
|
+
- [Maintaining Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/maintaining.md) — development checks,
|
|
179
179
|
documentation ownership, and release guidance.
|
package/README.zh-CN.md
CHANGED
|
@@ -2,11 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
<p align="center">
|
|
4
4
|
<!-- markdownlint-disable-next-line MD013 -->
|
|
5
|
-
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@
|
|
5
|
+
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@ec4b02387df98c108b30f7266e3711a686249107/assets/silvermoon.svg" width="960" alt="Silvermoon,项目的器灵">
|
|
6
6
|
</p>
|
|
7
7
|
|
|
8
8
|
<p align="center">
|
|
9
|
-
<a href="https://github.com/shazhou-ww/silvermoon/blob/
|
|
9
|
+
<a href="https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/README.md">English</a> | 简体中文
|
|
10
10
|
</p>
|
|
11
11
|
|
|
12
12
|
# Silvermoon(银月)
|
|
@@ -53,13 +53,13 @@ silvermoon whats-next <idea> --language zh-CN
|
|
|
53
53
|
|
|
54
54
|
在生成的 `Idea.md` 中描述想要抵达的世界,审阅并批准这个精确 revision。此后,
|
|
55
55
|
Silvermoon 会让目标、实现、仓库状态与现实结果始终相连。完整的首次工作流见英文
|
|
56
|
-
[Getting Started](https://github.com/shazhou-ww/silvermoon/blob/
|
|
56
|
+
[Getting Started](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/getting-started.md)。
|
|
57
57
|
对话命令默认以轻量 Markdown 标题呈现意图、观察和下一步;只有实际尝试了操作,
|
|
58
58
|
才出现动作与结果段落。程序消费者可使用 `--json` 获取
|
|
59
59
|
`intention / observation / outcomes / instructions` envelope。提交前使用
|
|
60
60
|
`silvermoon check --staged` 验证 index;无参数 `check` 只验证已提交的 `HEAD`,
|
|
61
61
|
不能替代提交前检查。只有项目快照有效时检查才以退出码 `0` 放行,详见英文
|
|
62
|
-
[Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/
|
|
62
|
+
[Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/reference.md)。任何命令都可以添加
|
|
63
63
|
`--trace <file.trace.jsonl>`,写出用于性能分析的成对任务与 Git 计时 span。参数若
|
|
64
64
|
没有以精确的小写 `.trace.jsonl` 结尾,Silvermoon 会自动追加;repository 内的
|
|
65
65
|
`*.trace.jsonl` 会被忽略。trace 文件只在待测命令工作完成后创建,并且绝不覆盖
|
|
@@ -70,7 +70,7 @@ Silvermoon 会让目标、实现、仓库状态与现实结果始终相连。完
|
|
|
70
70
|
阶段中与 snapshot 绑定的 repository-owned Markdown;`create-idea` 可返回
|
|
71
71
|
preparing guidance。这些 guidance 只能追加约束,不是第四份 contract 或 decision
|
|
72
72
|
fact;`check` 会验证完整的固定目录。详见英文
|
|
73
|
-
[Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/
|
|
73
|
+
[Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/core-concepts.md)。
|
|
74
74
|
|
|
75
75
|
## 为什么需要 Silvermoon
|
|
76
76
|
|
|
@@ -93,7 +93,7 @@ fact;`check` 会验证完整的固定目录。详见英文
|
|
|
93
93
|
<tr>
|
|
94
94
|
<td width="160" align="center" valign="top">
|
|
95
95
|
<!-- markdownlint-disable-next-line MD013 -->
|
|
96
|
-
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@
|
|
96
|
+
<img src="https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@ec4b02387df98c108b30f7266e3711a686249107/assets/silvermoon-avatar.svg" width="128" alt="项目器灵银月的线稿头像">
|
|
97
97
|
</td>
|
|
98
98
|
<td valign="top">
|
|
99
99
|
Silvermoon 得名于《凡人修仙传》中的银月。她来自灵界的银月狼族,是玲珑公主分裂出的
|
|
@@ -133,8 +133,8 @@ fact;`check` 会验证完整的固定目录。详见英文
|
|
|
133
133
|
|
|
134
134
|
## 延伸阅读
|
|
135
135
|
|
|
136
|
-
- [Getting Started](https://github.com/shazhou-ww/silvermoon/blob/
|
|
137
|
-
- [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/
|
|
138
|
-
- [Operating Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/
|
|
139
|
-
- [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/
|
|
140
|
-
- [Maintaining Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/
|
|
136
|
+
- [Getting Started](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/getting-started.md) — 安装、配置与第一个 idea。
|
|
137
|
+
- [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/core-concepts.md) — 项目归属、三重世界、revision 与决策边界。
|
|
138
|
+
- [Operating Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/operations.md) — 导航、创建、发布、仓库卫生与持续推进。
|
|
139
|
+
- [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/reference.md) — 存储、派生状态、CLI report、验证 target 与 schema。
|
|
140
|
+
- [Maintaining Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/maintaining.md) — 开发检查、文档职责与发布指南。
|
|
@@ -97,13 +97,17 @@ The [`publish-npm.yml`](../.github/workflows/publish-npm.yml) workflow then:
|
|
|
97
97
|
`pnpm check:skills`;
|
|
98
98
|
5. creates an isolated `git archive` staging tree and generates commit-pinned
|
|
99
99
|
English and Chinese package READMEs without changing the tagged checkout;
|
|
100
|
-
6. records the tagged commit as `gitHead`
|
|
101
|
-
creates one tarball, records its path,
|
|
102
|
-
integrity, and complete file list, then passes
|
|
103
|
-
`npm run pack:check` and `npm run test:e2e`; the
|
|
104
|
-
requires the tarball manifest to contain that exact
|
|
105
|
-
|
|
106
|
-
|
|
100
|
+
6. records the tagged commit as `gitHead` and the canonical `README.md` content
|
|
101
|
+
in the isolated package manifest, creates one tarball, records its path,
|
|
102
|
+
SHA-256, npm shasum, registry integrity, and complete file list, then passes
|
|
103
|
+
that same file to `npm run pack:check` and `npm run test:e2e`; the
|
|
104
|
+
pre-publication check requires the tarball manifest to contain that exact
|
|
105
|
+
commit and README metadata and requires a fresh directory pack to be
|
|
106
|
+
byte-identical;
|
|
107
|
+
7. publishes the unchanged staged directory with provenance and the derived npm
|
|
108
|
+
dist-tag when the version was absent, allowing npm to include package-level
|
|
109
|
+
README metadata while the deterministic pack check and post-publication
|
|
110
|
+
verifier guarantee the registry tarball matches the candidate bytes; and
|
|
107
111
|
8. runs `verify-npm-release.mjs` until the registry is consistent or the
|
|
108
112
|
bounded retry window expires.
|
|
109
113
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "silvermoon",
|
|
3
|
-
"version": "0.1.3-rc.
|
|
3
|
+
"version": "0.1.3-rc.3",
|
|
4
4
|
"description": "The project spirit that checks repository state and answers what's next.",
|
|
5
5
|
"packageManager": "pnpm@11.22.0",
|
|
6
6
|
"type": "module",
|
|
@@ -66,5 +66,7 @@
|
|
|
66
66
|
"mdast-util-to-markdown": "^2.1.2",
|
|
67
67
|
"yaml": "^2.9.1"
|
|
68
68
|
},
|
|
69
|
-
"gitHead": "
|
|
69
|
+
"gitHead": "ec4b02387df98c108b30f7266e3711a686249107",
|
|
70
|
+
"readme": "<!-- markdownlint-disable-file MD041 -->\n\n<p align=\"center\">\n <!-- markdownlint-disable-next-line MD013 -->\n <img src=\"https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@ec4b02387df98c108b30f7266e3711a686249107/assets/silvermoon.svg\" width=\"960\" alt=\"Silvermoon, the artifact spirit of the project\">\n</p>\n\n<p align=\"center\">\n <!-- markdownlint-disable-next-line MD013 -->\n <a href=\"https://npmx.dev/package/silvermoon\"><img src=\"https://img.shields.io/npm/v/silvermoon?style=flat-square\" alt=\"npm version\"></a>\n <!-- markdownlint-disable-next-line MD013 -->\n <a href=\"https://npmx.dev/package/silvermoon\"><img src=\"https://img.shields.io/node/v/silvermoon?style=flat-square\" alt=\"Node.js version\"></a>\n <!-- markdownlint-disable-next-line MD013 -->\n <a href=\"https://npmx.dev/package/silvermoon\"><img src=\"https://img.shields.io/npm/unpacked-size/silvermoon?style=flat-square\" alt=\"npm unpacked size\"></a>\n <!-- markdownlint-disable-next-line MD013 -->\n <a href=\"https://github.com/shazhou-ww/silvermoon/actions/workflows/ci.yml?query=branch%3Amain\"><img src=\"https://img.shields.io/github/actions/workflow/status/shazhou-ww/silvermoon/ci.yml?branch=main&style=flat-square&label=CI\" alt=\"CI status\"></a>\n</p>\n\n<p align=\"center\">\n English | <a href=\"https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/README.zh-CN.md\">简体中文</a>\n</p>\n\n# Silvermoon\n\n**The artifact spirit of the project.**\n\n## Quick Start\n\nSilvermoon needs Node.js 22 or newer and Git access to the repository's primary\nbranch.\n\n```sh\nnpm install --global silvermoon\nsilvermoon whats-next\n```\n\nSilvermoon is ecosystem-neutral: the target repository does not need\n`package.json`, a package manager, a Silvermoon dependency, or `node_modules`.\nThe first report lists every applicable setup step in order, including the\nexact `npx skills add ... --agent universal` command that registers the\ncanonical skill at `.agents/skills/silvermoon`.\n\nCreate `.silvermoon/config.yaml`:\n\n```yaml\nversion: 1\nprimaryRepository: https://github.com/example/repository.git\nprimaryBranch: main\npreferredLanguage: en\n```\n\n`preferredLanguage` is optional. A specific idea can override it with\n`language` in `status.yaml`, and `create-idea --language <tag>` can set that\noverride when the idea is created. Otherwise Silvermoon checks\n`~/.config/silvermoon/config.yaml` and finally defaults to `en-US`.\nThese stored values choose the language for project-owned content. To change\nonly one command's built-in output, use `whats-next --language en-US|zh-CN` or\n`check --language en-US|zh-CN`; the temporary override is never persisted.\n\nThen create an idea and let the registered Silvermoon skill guide one safe\nnext action at a time:\n\n```sh\nsilvermoon create-idea\nsilvermoon whats-next <idea>\nsilvermoon whats-next <idea> --language zh-CN\n```\n\nDescribe the desired world in the generated `Idea.md`, review it, and approve\nthat exact revision. From then on, Silvermoon keeps the goal, implementation,\nrepository state, and real-world result connected. See\n[Getting Started](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/getting-started.md) for the complete first workflow.\nDefault dialogue output uses lightweight Markdown headings for intent,\nobservation, and next instructions, plus actions and outcomes only when an\noperation was attempted. Add `--json` only when a programmatic consumer needs\nthe `intention / observation / outcomes / instructions` envelope. For\npre-commit validation, run `silvermoon check --staged`: unlike the default\n`check` (committed `HEAD`), it checks the index and exits `0` only when the\nproject snapshot is valid. See the [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/reference.md)\nfor validation targets and exit codes. Add `--trace <file.trace.jsonl>` to any\ncommand to write paired task and Git timing spans for performance analysis.\nIf the argument does not end with the exact lowercase `.trace.jsonl` suffix,\nSilvermoon appends it. Repository-local `*.trace.jsonl` files are ignored.\nTrace files are created only after the measured command work completes and\nnever overwrite an existing file.\n\nProjects may optionally add `.silvermoon/guidance/preparing.md`,\n`implementing.md`, and `deploying.md`. Silvermoon returns only the current\nactionable phase's snapshot-bound, repository-owned Markdown after canonical\ninstructions; `create-idea` can return preparing guidance. This guidance is\nadditive, never a fourth contract or decision fact, and `check` validates the\ncomplete fixed directory. See [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/core-concepts.md).\n\n## Why Silvermoon\n\nLong-running Agent work usually asks people to carry too much invisible state.\nSomeone must remember what was intended, whether the code still matches the\ntask, and which conversation or machine knows the latest truth. Silvermoon\nmakes those concerns part of the project instead.\n\nIt lets people step back from continuous supervision and return at the\ndecisions that belong to them: approving the intended outcome, accepting the\nimplementation, and accepting that the result is true in the outside world.\nBetween those boundaries, an Agent can inspect repository facts and continue\nthe highest-priority safe action.\n\nIt also refuses to let a detached task card declare success. Current artifacts\nand explicit decisions jointly determine state, so a changed goal or\nimplementation naturally invalidates conclusions that depended on the older\nrevision. Because those facts live in Git, work can continue across devices,\nsessions, Agents, and hosting platforms.\n\n## The Project's Artifact Spirit\n\n> Fellow Daoist, you wouldn't want your lifebound project to be without an\n> artifact spirit, would you?\n\n<table>\n <tr>\n <td width=\"160\" align=\"center\" valign=\"top\">\n <!-- markdownlint-disable-next-line MD013 -->\n <img src=\"https://cdn.jsdelivr.net/gh/shazhou-ww/silvermoon@ec4b02387df98c108b30f7266e3711a686249107/assets/silvermoon-avatar.svg\" width=\"128\" alt=\"Line portrait of Silvermoon, the project's artifact spirit\">\n </td>\n <td valign=\"top\">\n Silvermoon is named after a character in <em>A Record of a Mortal's\n Journey to Immortality</em>. She comes from the Silvermoon Wolf Clan in\n the Spirit Realm and is one of the split souls of Ling Long. After losing\n part of her memory in the human realm, she lives as an artifact spirit\n first in a wolf-headed jade scepter and later in Han Li's Bamboo\n Cloudswarm Swords.\n <br><br>\n That image fits this project: Silvermoon does not belong to one operator\n or one chat. It lives with the project's artifacts, understands their\n state, and helps each companion find what comes next. The biography is\n inspiration, not a prerequisite for using the tool.\n </td>\n </tr>\n</table>\n\nWatch *A Record of a Mortal's Journey to Immortality*:\n\n<!-- markdownlint-disable-next-line MD013 -->\n- YouTube: [Episode 150: Overseas Turmoil 26](https://www.youtube.com/watch?v=GJgezoCBIHM \"A Record of a Mortal's Journey to Immortality — Episode 150: Overseas Turmoil 26\")\n<!-- markdownlint-disable-next-line MD013 -->\n- Bilibili: [Episode 150: Overseas Turmoil 26](https://www.bilibili.com/bangumi/play/ep1231558 \"A Record of a Mortal's Journey to Immortality — Episode 150: Overseas Turmoil 26\")\n\n## From Ideal To Real\n\nA project is more than a task list or a transcript. It is an ideal becoming\nreal through three nested worlds.\n\n**Ideal World (道心)** names the outcome worth pursuing. **Inner World (内景)**\ngives that intent shape in repository artifacts. **Outer World (现世)** asks\nwhether the shaped work is true where it must actually operate.\n\n> 道心立意,内景成形,现世验真。\n\nThe worlds nest from the inside out. Implementation contains the ideal it\nserves, and deployment contains both. This is an engineering relationship, not\njust a metaphor: when an inner world changes, conclusions from an outer world\nno longer have the same foundation and must be proven again.\n\nHumans own approval and acceptance. Agents own continuation: they read the\ncontracts, the ledger, and Git facts; preserve concurrent work; execute one\nsafe action; and reobserve only after something changes. The context belongs to\nthe project, not to a fleeting conversation.\n\n## Further Reading\n\n- [Getting Started](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/getting-started.md) — installation, configuration,\n and the first idea.\n- [Core Concepts](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/core-concepts.md) — project ownership, the three\n worlds, revisions, and decision boundaries.\n- [Operating Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/operations.md) — navigation, creation,\n publication, hygiene, and continuation.\n- [Technical Reference](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/reference.md) — storage, derived state, CLI\n reports, validation targets, and schemas.\n- [Maintaining Silvermoon](https://github.com/shazhou-ww/silvermoon/blob/ec4b02387df98c108b30f7266e3711a686249107/docs/maintaining.md) — development checks,\n documentation ownership, and release guidance.\n",
|
|
71
|
+
"readmeFilename": "README.md"
|
|
70
72
|
}
|