@adamchanadam/agent-handoff-kit 0.3.43 → 0.3.44
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.en.md +197 -81
- package/README.md +1 -1
- package/bin/migration-baselines/official-origin-catalog.json +10039 -10039
- package/package.json +1 -1
- package/packs/release.md +2 -0
- package/packs/writing.md +5 -0
- package/runtime-core/PROJECT_INDEX.md +1 -1
package/package.json
CHANGED
package/packs/release.md
CHANGED
|
@@ -16,11 +16,13 @@ Use for release, publish, deploy, tag, version bump, hotfix, or GA completion cl
|
|
|
16
16
|
3. Do not publish, deploy, tag, or upload without explicit user approval.
|
|
17
17
|
4. Keep rollback or recovery notes when release risk is non-trivial.
|
|
18
18
|
5. Preserve migration and upgrade safety for existing users.
|
|
19
|
+
6. If this candidate changes a public language counterpart, load the Writing Pack and require its independent semantic review for each changed source/target pair before release. Do not repeat that review for unchanged pairs; the candidate evidence records only the pairs this release changed.
|
|
19
20
|
|
|
20
21
|
## Checks
|
|
21
22
|
|
|
22
23
|
- Run build/test/package checks required by `dev/PROJECT_INDEX.md`.
|
|
23
24
|
- Check README, changelog, migration notes, and `dev/DOC_SYNC_REGISTRY.md`.
|
|
25
|
+
- When public bilingual material changed, check the candidate evidence identifies the changed pair, its source and target hashes after review, and the independent verdict. Do not substitute length, emoji, keyword, link, or an older PASS for that review.
|
|
24
26
|
- Record exact command results or blockers.
|
|
25
27
|
|
|
26
28
|
## Closeout
|
package/packs/writing.md
CHANGED
|
@@ -20,6 +20,10 @@ Use for drafting, editing, style, structure, publication copy, documentation pro
|
|
|
20
20
|
7. For public README, onboarding, and other user-facing docs, use the product-journey rule: the user states the goal, the AI handles technical work. Keep one primary user path. Do not make users choose between install, upgrade, doctor, dry-run, or terminal commands when an AI-assisted path exists. Put technical commands in the dedicated AI install page, CLI help, or advanced examples instead of duplicating them in the main README flow.
|
|
21
21
|
8. When writing or revising Markdown files, decide whether the output is a durable source, a reference, a runbook, a public document, a reusable generated artifact, a draft, or one-time evidence. Durable outputs must be indexed or tied to a registered source/sync home before completion; drafts and one-time evidence must be labeled so they do not become hidden current state.
|
|
22
22
|
9. If a new document repeats requirements, instructions, acceptance rules, or process already owned by another file, consolidate into the existing source or make the new file explicitly subordinate. Do not let writing work create parallel truth.
|
|
23
|
+
10. For a translation or language counterpart of a user-facing document, the source-language document is the sole content authority unless the user explicitly changes the content. Read the whole source before drafting. Preserve its section order, cases, examples, figures, prompts, commands, confirmations, user-visible limits, navigation, and meaningful visual cues such as emoji; do not translate from an old counterpart, a summary, or remembered discussion.
|
|
24
|
+
11. Build a source-to-target section map before claiming completion. Do not compress several source steps into an overview, merge distinct user choices, reorder the journey, replace the source example with a different story, or add a new user rule, external action, format promise, or safety boundary that the source does not contain. If the source itself conflicts with the current product contract, flag that source drift and reconcile the source first; do not silently make the target language say something different.
|
|
25
|
+
12. A language counterpart needs semantic acceptance, not just mechanical checks. An independent reviewer who did not draft the target must read source and target section by section and decide: (a) what the source promises; (b) whether the target preserves the same action, limit, example, and consequence; (c) whether a reader can actually follow it; and (d) what user harm follows from a difference. Any mismatch is `FAIL`; correct the affected section and re-review it. File size, headings, keywords, emoji counts, links, HTML structure, or a similar overall gist are only mechanical floors and never a semantic pass.
|
|
26
|
+
13. For a release candidate or other durable public counterpart, record the semantic verdict and current source/target hashes in the existing candidate QA evidence **only when that language pair changed in the candidate**. Any source or target content change invalidates that pair's verdict and requires a new independent readback. Unchanged language pairs do not require a new review merely because another version is being released. A target may pass only when every mapped source section passes; do not claim a partial score as translation completion.
|
|
23
27
|
|
|
24
28
|
## Checks
|
|
25
29
|
|
|
@@ -30,6 +34,7 @@ Use for drafting, editing, style, structure, publication copy, documentation pro
|
|
|
30
34
|
- Check duplicate-source risk before keeping a new requirement, checklist, process, or instruction document.
|
|
31
35
|
- For public Chinese docs, read the final text as a new user journey: the next action should be clear without technical background.
|
|
32
36
|
- For README-style docs, confirm the main path does not become parallel instructions: no repeated manual install section, no competing command table, and no requirement that the reader understand internal files before taking the first action.
|
|
37
|
+
- For a translation or language counterpart, complete the source-to-target semantic review above when the source or target changed. Record its verdict in the existing candidate QA owner when the document is public or release-bound; use hash, link, and format checks only to detect drift after the human review, not to replace it. Do not rerun an unchanged counterpart as a standing release ritual.
|
|
33
38
|
|
|
34
39
|
## Closeout
|
|
35
40
|
|
|
@@ -6,7 +6,7 @@ Purpose: give a stateless AI a compact map of the project before it reads or edi
|
|
|
6
6
|
|
|
7
7
|
| Field | Value | Last verified |
|
|
8
8
|
|---|---|---|
|
|
9
|
-
| Agent Handoff Kit template version | 0.3.
|
|
9
|
+
| Agent Handoff Kit template version | 0.3.44 | current template version |
|
|
10
10
|
| Runtime | TBD | TBD |
|
|
11
11
|
| Framework | TBD | TBD |
|
|
12
12
|
| Package manager | TBD | TBD |
|