docs: openclaw-refactor-docs points at a skill renamed in 0dabb70 (#119394)

* docs: point openclaw-refactor-docs at technical-documentation

The openclaw-docs skill was removed in 0dabb7010b,
which replaced it with technical-documentation. openclaw-refactor-docs was not
updated and still told the agent to read ../openclaw-docs/SKILL.md first, so the
read returned nothing and the refactor proceeded without the style and page-type
rules it was supposed to apply.

* docs: use a workspace-relative path for the technical-documentation read

OpenClaw resolves relative read paths from the session workspace cwd
(resolveReadPath -> resolveToCwd -> resolvePath(cwd, path) in
src/agents/sessions/tools/path-utils.ts), not from the directory holding
the skill file. ../technical-documentation/SKILL.md therefore resolved
outside the workspace and the read still failed.

Use .agents/skills/technical-documentation/SKILL.md, which is the path
that exists from the workspace root.

* docs: resolve technical-documentation support files via {baseDir}

The skill names ten support files relatively (six references/*.md and four
agents/*.md). read resolves relative paths from the session workspace cwd,
so none of them resolved: they exist only under the skill directory.

{baseDir} is the documented mechanism for exactly this and resolves against
the skill own directory, so it works regardless of where the skill is
installed. CONTRIBUTING.md is left alone: it is a workspace-root file and
already resolves.

* Revert the {baseDir} rewrite: it was cleanup, not a fix

The skills catalog prompt already instructs the model to resolve a relative
reference against the skill directory and use the resulting absolute path
(src/skills/loading/skill-contract.ts). These ten references were therefore
never broken, and rewriting them does not belong in a rename follow-up.

Restores this file to its state on main.

* Restore the sibling-relative read path

The skills catalog prompt resolves a relative reference against the skill
directory, so ../technical-documentation/SKILL.md resolves to
.agents/skills/technical-documentation/SKILL.md and was already correct.
Rewriting it workspace-relative was churn on a line whose only defect was
the retired skill name.

This leaves the PR as what it claimed to be: three references to a skill
that was renamed in 0dabb70.

.agents/skills/openclaw-refactor-docs/SKILL.md

@@ -10,7 +10,7 @@ description: Refactor an existing OpenClaw docs page with source-audited preserv
 Use this skill when the user gives a target OpenClaw docs page and asks to
 rewrite, refactor, reorganize, split, shorten, or improve it.
 
-This skill builds on `openclaw-docs`: use that skill for style, page types,
+This skill builds on `technical-documentation`: use that skill for style, page types,
 structure, examples, discoverability, and verification. This skill adds the
 rewrite workflow needed to avoid losing accurate behavior during a major docs
 refactor.
@@ -53,7 +53,7 @@ Prefer this split:
 
 ### 1. Load the doc standard
 
-Read `../openclaw-docs/SKILL.md` first. Apply its page-type, style,
+Read `../technical-documentation/SKILL.md` first. Apply its page-type, style,
 examples, navigation, and verification guidance throughout the refactor.
 
 Run `pnpm docs:list` when available, then read only the target page and the
@@ -61,7 +61,7 @@ likely entry points, references, or related pages needed for the refactor.
 
 ### 2. Classify the page
 
-Before editing, decide the intended page type from `openclaw-docs`.
+Before editing, decide the intended page type from `technical-documentation`.
 
 If the current page mixes page types, choose the main page type and plan where
 the other material belongs: