fix: point the code-docs skill at deployed pages and harden the lint floor

The docs table listed pages that were never deployed; each row now
names a verified page of the published site, and rows describing
undeployed pages are dropped. The lint coverage wrapper rejects a
non-numeric LINT_MIN_FILES before running instead of silently
disabling the guard.

Author: elkaix

packages/agent-core-v2/src/features/skill/catalog/builtin/check-pythinker-code-docs.md

@@ -1,11 +1,11 @@
 ---
 name: check-pythinker-code-docs
-description: Answer questions about the Pythinker Code product using the official documentation — CLI usage, configuration, slash commands, features, membership and quota, API onboarding, third-party tool setup, and error codes. Use when the user asks how Pythinker Code works, how to set something up, or what a Pythinker Code error message means.
+description: Answer questions about the Pythinker Code product using the official documentation — CLI usage, configuration, slash commands, features, and guides. Use when the user asks how Pythinker Code works, how to set something up, or how a documented feature behaves.
 ---
 
 # Check Pythinker Code docs (check-pythinker-code-docs)
 
-Answer Pythinker Code **product** questions from the official documentation site, not from memory. This skill covers product usage ("how do I configure a provider", "what does this error mean", "how does membership quota work"); it is not for developing the Pythinker Code repository itself.
+Answer Pythinker Code **product** questions from the official documentation site, not from memory. This skill covers product usage ("how do I configure a provider", "what does this error message mean", "how does Remote Control work"); it is not for developing the Pythinker Code repository itself.
 
 ## The single source of truth
 
@@ -21,18 +21,14 @@ Fetch pages with **FetchURL** before answering. All page links below are relativ
 
 | Question topic | Page (relative to the base URL) |
 | --- | --- |
-| What Pythinker Code is; Base URL / API Key; standard vs high-speed model; platform comparison | `./` (home overview) |
-| Membership plans, quota and rate limits, fuel packs | `pythinker-code/membership.html` |
-| Install / login / usage FAQ | `pythinker-code/faq.html` |
-| Error codes and their meaning (e.g. 401 for high-speed model access) | `pythinker-code/error-reference.html` |
-| Product news and recent changes | `pythinker-code/whats-new.html` |
-| Community guidelines; contact and feedback | `pythinker-code/community-guidelines.html`, `pythinker-code/contact-and-feedback.html` |
-| `config.toml` fields, providers/models, environment variables, data locations, config overrides | `pythinker-code-cli/configuration/` — `config-files.html`, `providers.html`, `env-vars.html`, `data-locations.html`, `overrides.html` |
-| Skills, MCP, hooks, plugins, themes, agents/sub-agents, Pythinker Datasource | `pythinker-code-cli/customization/` — `skills.html`, `mcp.html`, `hooks.html`, `plugins.html`, `themes.html`, `agents.html`; Pythinker Datasource lives at `plugins.html#pythinker-datasource` |
-| Getting started, sessions and context, goals, interaction and input, IDEs, migration, use cases | `pythinker-code-cli/guides/` — `getting-started.html`, `sessions.html`, `goals.html`, `interaction.html`, `ides.html`, `migration.html`, `use-cases.html` |
-| Slash commands, keyboard shortcuts, builtin tools, `pythinker` command flags, ACP | `pythinker-code-cli/reference/` — `slash-commands.html`, `keyboard.html`, `tools.html`, `pythinker-command.html`, `pythinker-acp.html` |
-| CLI changelog | `pythinker-code-cli/release-notes/changelog.html` |
-| Using Pythinker Code in Claude Code and other third-party agents | `third-party-tools/other-coding-agents.html` |
+| What Pythinker Code is; getting started; install and first run | `./` (home overview), `guides/getting-started.html` |
+| Providers and models, API keys | `configuration/providers.html` |
+| `config.toml` fields, environment variables, data locations, config overrides | `configuration/` — `config-files.html`, `env-vars.html`, `data-locations.html`, `overrides.html` |
+| Skills, MCP, hooks, plugins, themes, agents/sub-agents | `customization/` — `skills.html`, `mcp.html`, `hooks.html`, `plugins.html`, `themes.html`, `agents.html` |
+| Sessions and context, interaction and input, IDEs, use cases | `guides/` — `sessions.html`, `interaction.html`, `ides.html`, `use-cases.html` |
+| Desktop app, Remote Control, browser web UI | `guides/` — `desktop.html`, `remote-control.html`, `web.html` |
+| Slash commands, keyboard shortcuts, builtin tools, `pythinker` command flags, ACP, server API, release channels | `reference/` — `slash-commands.html`, `keyboard.html`, `tools.html`, `pythinker-command.html`, `pythinker-acp.html`, `server-api.html`, `release-channels.html` |
+| CLI changelog | `release-notes/changelog.html` |
 
 If no row fits the question, fetch the docs home page and follow its navigation links.
 

scripts/oxlint-coverage.mjs

@@ -10,6 +10,10 @@ import { fileURLToPath } from 'node:url';
 // format included); afterwards a small probe run with a forced plain format
 // walks a known directory and must report a real file count.
 const MIN_FILES = Number(process.env.LINT_MIN_FILES ?? '10');
+if (!Number.isFinite(MIN_FILES) || MIN_FILES <= 0) {
+  process.stderr.write(`oxlint coverage check failed: LINT_MIN_FILES must be a positive number, got ${String(process.env.LINT_MIN_FILES)}\n`);
+  process.exit(2);
+}
 const PROBE_DIR = 'scripts';
 
 const repoBin = join(fileURLToPath(new URL('..', import.meta.url)), 'node_modules', '.bin', 'oxlint');