docs(skills): point the doc skills at the paths that exist

The skills still targeted a docs/en tree the site does not serve, a changelog
sync script that was never added, and a breaking-changes page that does not
exist. Also drops a bilingual parity check left over from the removed second
locale, a duplicated verification command, and an example import that could not
resolve from the package it was written for.

Author: elkaix

.agents/skills/agent-core-dev/server-align.md

@@ -94,8 +94,8 @@ packages/agent-core-v2/src/<domain>Legacy/
 Skeleton (matches `prompt/`):
 
 ```ts
-// prompt.ts — contract shaped by the v1 wire schema (agent-gateway/src/protocol)
-import type { PromptSubmitResult, PromptSubmission } from '../../protocol/rest-prompt';
+// prompt.ts — contract shaped by the v1 wire schema (@pymodel/protocol)
+import type { PromptSubmitResult, PromptSubmission } from '@pymodel/protocol';
 import { createDecorator, type ServiceIdentifier } from '#/_base/di/instantiation';
 
 export interface IAgentPromptService {
@@ -204,7 +204,6 @@ Where the route mirrors v1, the test is the regression guard for the schema-fide
 
 ### 7. Verify
 
-- `pnpm -C packages/agent-gateway test` — server routes green.
 - `pnpm -C packages/agent-gateway test` — server routes green (incl. any wire-schema guards).
 - `pnpm -C packages/agent-core-v2 test` — native + Legacy Service tests green.
 - `pnpm -C packages/agent-core-v2 run lint:imports` — the import boundaries (v1 ban, kosong subtree) still hold for a LegacyService.

.agents/skills/gen-docs/SKILL.md

@@ -17,9 +17,9 @@ For a **full pre-release audit** of all pages (detecting hallucinations and cove
 
 This skill depends on the following being in place. If any are missing, stop and report to the user before continuing:
 
-- `docs/` directory with `docs/en/` and `docs/.vitepress/config.ts` set up (VitePress site).
+- `docs/` directory with `docs/.vitepress/config.ts` set up (VitePress site).
 - `docs/AGENTS.md` style guide — defines source-of-truth rules, terminology table, typography, and writing style.
-- `docs/scripts/sync-changelog.mjs` — auto-syncs root `CHANGELOG.md` to `docs/en/release-notes/changelog.md`.
+- The `sync-changelog` skill — syncs `apps/pythinker-code/CHANGELOG.md` into `docs/release-notes/changelog.md`.
 
 ## Workflow
 
@@ -40,41 +40,34 @@ This skill depends on the following being in place. If any are missing, stop and
 
    If after the scan you conclude there is no user-facing impact, say so and stop.
 
-3. **Sync English changelog**
+3. **Sync the changelog**
 
-   Run:
-
-   ```bash
-   node docs/scripts/sync-changelog.mjs
-   ```
-
-   This updates `docs/en/release-notes/changelog.md` from the root `CHANGELOG.md`. Never edit the docs changelog by hand.
+   Run the `sync-changelog` skill. It curates `apps/pythinker-code/CHANGELOG.md`
+   into `docs/release-notes/changelog.md`. Never edit the docs changelog by hand.
 
 4. **Update user docs**
 
-   Following the rules in `docs/AGENTS.md`, edit the affected pages in whichever locale you are working in, then sync the mirror. Match terminology with the term table in `docs/AGENTS.md` and the existing wording in surrounding pages.
+   Following the rules in `docs/AGENTS.md`, edit the affected pages under `docs/`. Match terminology with the term table in `docs/AGENTS.md` and the existing wording in surrounding pages.
 
    Cover all relevant sections:
 
    - Guides (getting-started, use cases, interaction, sessions, IDE integration)
    - Customization (skills, agents, MCP, hooks, plugins, etc.)
    - Configuration (config files, env vars, providers, data locations)
    - Reference (CLI subcommands, slash commands, keyboard shortcuts)
-   - Release notes (`docs/en/release-notes/breaking-changes.md` if a breaking change is involved)
+   - Release notes (`docs/release-notes/changelog.md`, via the `sync-changelog` skill)
 
 ## Rules and conventions
 
 - **Terminology**: Use the term table in `docs/AGENTS.md` exactly. Do not invent synonyms.
 - **Scope discipline**: Only update sections affected by the recent changes. Do not opportunistically rewrite unrelated docs.
 - **Public examples**: Never write real internal endpoints, key names, account names, or service names into docs. Use neutral placeholders such as `https://api.example.com/v1`, `https://registry.example.com/v1/models/api.json`, `example.test`, and `YOUR_API_KEY`.
-- **Breaking changes**: If any change is breaking, also update `docs/en/release-notes/breaking-changes.md` (under `## Unreleased`) with `**Affected**` + `**Migration**` subsections.
-- **Do not edit auto-synced files**: `docs/en/release-notes/changelog.md` is regenerated by the sync script; any manual edit will be overwritten.
+- **Breaking changes**: If any change is breaking, say so in the changeset and describe the migration there; the changelog carries it into `docs/release-notes/changelog.md`.
+- **Do not edit auto-synced files**: `docs/release-notes/changelog.md` is regenerated by the sync script; any manual edit will be overwritten.
 
 ## Common mistakes
 
 - Describing what code changed instead of what the user can now do (or can no longer do).
 - Adding a new section heading per feature instead of weaving the change into existing prose.
-- Updating only one locale and leaving its mirror stale.
-- Editing only the mirror to fix wording that should be corrected in the locale you changed first.
 - Inventing new terminology that drifts from the `docs/AGENTS.md` term table.
 - Using real internal values in examples instead of neutral `example` placeholders.

.agents/skills/sync-changelog/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sync-changelog
-description: Use after a release succeeds, when maintainers need to sync apps/pythinker-code/CHANGELOG.md into docs/en/release-notes/changelog.md, then open a PR on a dedicated branch.
+description: Use after a release succeeds, when maintainers need to sync apps/pythinker-code/CHANGELOG.md into docs/release-notes/changelog.md, then open a PR on a dedicated branch.
 ---
 
 # Sync Changelog
@@ -20,7 +20,7 @@ After the release flow finishes (Release PR merged → `Version Packages` comple
 ## When To Use
 
 - A new version has been published to npm.
-- The top of `apps/pythinker-code/CHANGELOG.md` contains version blocks that are not yet in `docs/en/release-notes/changelog.md`.
+- The top of `apps/pythinker-code/CHANGELOG.md` contains version blocks that are not yet in `docs/release-notes/changelog.md`.
 - The `gen-docs` flow does not run this automatically; maintainers must explicitly do it after release.
 
 Do **not** run this before the Release PR is merged. At that point, changesets has not yet written the new version into `apps/pythinker-code/CHANGELOG.md`.
@@ -30,7 +30,7 @@ Do **not** run this before the Release PR is merged. At that point, changesets h
 | File | Role | Edited by |
 |---|---|---|
 | `apps/pythinker-code/CHANGELOG.md` | **Only upstream source**, generated by changesets | Never edit manually |
-| `docs/en/release-notes/changelog.md` | English docs changelog; source of truth for docs | This skill |
+| `docs/release-notes/changelog.md` | English docs changelog; source of truth for docs | This skill |
 
 Core rule: `apps/pythinker-code/CHANGELOG.md` is the only upstream source; the English docs changelog is what this skill writes.
 
@@ -61,7 +61,7 @@ Before creating the branch, peek at the version range so the branch name matches
 
 ```bash
 rg '^## ' apps/pythinker-code/CHANGELOG.md | head -5
-rg '^## ' docs/en/release-notes/changelog.md | head -5
+rg '^## ' docs/release-notes/changelog.md | head -5
 ```
 
 Name the branch after the newest upstream version that is not yet in the English docs page:
@@ -238,14 +238,13 @@ Doc links: an entry that changes a documented config surface may end with a poin
 Review:
 
 ```bash
-git diff docs/en/release-notes/changelog.md
+git diff docs/release-notes/changelog.md
 ```
 
 Check:
 
 - Every version heading carries its release date from the published tag, in half-width parentheses.
-- Each version has the same section set and order on both pages.
-- Each section has the same number of entries on both pages.
+- Section order within each version follows the canonical order.
 - Within each section, the most valuable, obvious, and larger entries appear before smaller or narrower entries.
 - Low-signal entries were collapsed into the single catch-all line, placed last under `Bug Fixes` — or under `Polish` when nothing folded is a fix (both the reader-action test and the channel test applied); the catch-all wording matches what was folded and never claims fixes that did not happen; section sizes stay within the density defaults (about 2 Polish, 3 Bug Fixes) unless extra qualifying entries were deliberately kept and flagged for review. The catch-all line ends with the upstream changelog pointer (file link, no version anchor).
 - PR links and commit hashes were stripped.
@@ -273,7 +272,7 @@ If the user chooses review:
 1. Show the uncommitted diff:
 
    ```bash
-   git diff docs/en/release-notes/changelog.md
+   git diff docs/release-notes/changelog.md
    ```
 
 2. Summarize synced versions, section counts, and anything that needed manual classification. List every entry folded into a catch-all line (short titles, one line each), any section that exceeds the density defaults, and every borderline call flagged during curation — the reviewer cannot own a cutoff they cannot see.
@@ -289,7 +288,7 @@ Only run this step when the user skipped review or confirmed review is complete.
 Stage only the changelog docs files:
 
 ```bash
-git add docs/en/release-notes/changelog.md
+git add docs/release-notes/changelog.md
 ```
 
 Use a neutral docs-sync commit message:
@@ -336,7 +335,7 @@ The docs-site changelog has not yet been synced for `<version range>` after the
 
 ## What changed
 
-- Synced `<version range>` from `apps/pythinker-code/CHANGELOG.md` into `docs/en/release-notes/changelog.md`
+- Synced `<version range>` from `apps/pythinker-code/CHANGELOG.md` into `docs/release-notes/changelog.md`
 - Verified with `pnpm --filter docs run build`
 
 ## Checklist

.agents/skills/write-tui/SKILL.md

@@ -68,7 +68,7 @@ Themes are managed centrally under `src/tui/theme/`:
 - `bundle.ts` — packs `colors`, `styles`, `markdownTheme` into a `PythinkerTUIThemeBundle`.
 - `index.ts` / `detect.ts` — theme type and auto/dark/light resolution.
 
-> **Keep the color-token set in sync.** `ColorPalette` in `colors.ts` is the source of truth for color tokens. When you add, rename, or remove one, update its mirrors in the same change: the custom-theme JSON schema (`apps/pythinker-code/src/tui/theme/theme-schema.json`), the token table in the custom-theme docs (`docs/en/customization/themes.md`), and the token table in the `custom-theme` built-in skill (`packages/agent-core/src/skill/builtin/custom-theme.md`).
+> **Keep the color-token set in sync.** `ColorPalette` in `colors.ts` is the source of truth for color tokens. When you add, rename, or remove one, update its mirrors in the same change: the custom-theme JSON schema (`apps/pythinker-code/src/tui/theme/theme-schema.json`), the token table in the custom-theme docs (`docs/customization/themes.md`), and the token table in the `custom-theme` built-in skill (`packages/agent-core/src/skill/builtin/custom-theme.md`).
 
 Apply / switch flow: