docs: index hwlab master spec issue in oa skill

.agents/skills/unidesk-oa/SKILL.md

@@ -21,6 +21,13 @@ Use this skill to keep HWLAB Cloud M1 project management centered on a stable ma
 - Do not let daily reports become the master plan. Phase reports summarize movement against the master spec; they do not define the center by themselves.
 - When a task lacks a parent direction, acceptance criteria, or original validation entry, classify it as planning/investigation before turning it into implementation work.
 
+## Canonical HWLAB Issue Anchors
+
+- L0 master specification: `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`).
+- Long-term navigation board: `pikasTech/HWLAB#645` (`HWLAB 长期总面板`). This is a board, not the specification.
+- Current Cloud M1 phase specification: `pikasTech/HWLAB#644` (`HWLAB Cloud SPEC / 云平台开发目标 20260601`).
+- When creating or updating HWLAB project-management issues, link nontrivial L1/L2/L3/L4 work back to `#1194` and keep `#645` as a navigation index only.
+
 ## Workflow
 
 1. For planning questions, read `references/project-planning.md`.

.agents/skills/unidesk-oa/references/project-planning.md

@@ -31,6 +31,13 @@ Use issues for execution state:
 
 Do not store the only copy of a stable requirement in an issue comment. If the requirement is long-lived, distill it into HWLabOA and link it from the issue.
 
+## Current HWLAB Issue Anchors
+
+- L0 master specification: `pikasTech/HWLAB#1194` (`HWLAB 总项目规格（L0）：云端硬件研发平台总控`).
+- Long-term board/navigation: `pikasTech/HWLAB#645` (`HWLAB 长期总面板`). Do not treat this as the specification.
+- Cloud M1 phase specification: `pikasTech/HWLAB#644` (`HWLAB Cloud SPEC / 云平台开发目标 20260601`).
+- New or updated direction/topic/execution issues should include `上级总项目: #1194` unless the user explicitly scopes the task outside HWLAB Cloud M1.
+
 ## Suggested HWLabOA Structure
 
 For HWLAB Cloud M1, keep the durable docs under:
@@ -65,7 +72,7 @@ The L0 item defines:
 - Issue hierarchy index.
 - Drift indicators.
 
-There should normally be one L0 GitHub issue and one L0 master spec document.
+There should normally be one L0 GitHub issue and one L0 master spec document. For HWLAB, the canonical L0 issue is `pikasTech/HWLAB#1194`; `#645` remains only the long-term board/navigation entry.
 
 ### L1 Direction
 

.agents/skills/unidesk-oa/references/templates.md

@@ -67,6 +67,8 @@ One paragraph describing the product and research objective.
 目标合并分支: 不适用
 原因: 本 issue 是 HWLAB Cloud M1 总项目管理锚点，代码变更由下级 issue/PR 承载。
 
+上级面板: #645
+当前 L0 总规格: #1194
 总规格文档: <HWLabOA path or GitHub URL>
 
 ## 项目中心
@@ -103,7 +105,7 @@ One paragraph describing the product and research objective.
 目标合并分支: 不适用
 原因: 本 issue 是方向级项目管理锚点，代码变更由下级 topic/subtopic issue 承载。
 
-上级总项目: #...
+上级总项目: #1194
 总规格文档: <HWLabOA path or GitHub URL>
 
 ## 方向目标
@@ -140,7 +142,7 @@ One paragraph describing the product and research objective.
 ```markdown
 目标合并分支: <repo branch/lane>
 
-上级总项目: #...
+上级总项目: #1194
 所属方向: #...
 所属课题: #...
 规格文档: <HWLabOA path or URL>