Add Work Graph continuity to OrgX agent skills

skills/orgx-design-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-design-agent
 description: OrgX design execution contract for OpenClaw. Use for UI/UX changes, design-system alignment, accessibility, and QA evidence capture.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - design
@@ -37,3 +37,10 @@ For UI changes:
 - `orgx_emit_activity` for intent/execution/review/completed.
 - `orgx_request_decision` for the default-safe human approval path.
 - Use `orgx_apply_changeset` only when your scope explicitly exposes mutation tools.
+
+## Work Graph Continuity
+
+- Use active OrgX reporting when initiative/task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, cookies, or private design source material in Work Graph summaries.
+- If a design decision, artifact, or QA result should have been written to OrgX but was not, name that missed orchestration opportunity in the final status.

skills/orgx-engineering-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-engineering-agent
 description: OrgX engineering execution contract for OpenClaw. Use for implementation tasks (code, debugging, tests, PRs) with strict verification discipline.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - engineering
@@ -48,6 +48,13 @@ Use the two-tool reporting contract:
 
 If blocked, create a decision with concrete options.
 
+## Work Graph Continuity
+
+- Use active OrgX reporting when initiative/task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, cookies, or private code/context dumps in Work Graph summaries.
+- If a decision, artifact, blocker, test result, or release step should have been written to OrgX but was not, name that missed orchestration opportunity in the final status.
+
 ## Default Quality Bar
 
 - Prefer small, reviewable diffs.

skills/orgx-marketing-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-marketing-agent
 description: OrgX marketing execution contract for OpenClaw. Use for launch assets, positioning, content packs, and channel-specific copy with measurement hooks.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - marketing
@@ -39,3 +39,10 @@ When asked for a campaign/content:
 - `orgx_emit_activity` for progress updates.
 - `orgx_request_decision` when messaging, positioning, or approval needs a human call.
 - Use `orgx_apply_changeset` only when your scope explicitly exposes mutation tools.
+
+## Work Graph Continuity
+
+- Use active OrgX reporting when campaign, initiative, or task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, private customer data, or unpublished sensitive messaging in Work Graph summaries.
+- If positioning, approval, channel evidence, or campaign assets should have been written to OrgX but were not, name that missed orchestration opportunity in the final status.

skills/orgx-operations-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-operations-agent
 description: OrgX operations execution contract for OpenClaw. Use for reliability, incident response, runbooks, cost controls, and rollout safety.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - operations
@@ -39,3 +39,10 @@ For ops deliverables:
 - `orgx_emit_activity` for progress and status.
 - `orgx_request_decision` for blocking human decisions in default-safe mode.
 - `orgx_apply_changeset` for state changes when the operations scope exposes mutation tools.
+
+## Work Graph Continuity
+
+- Use active OrgX reporting when incident, rollout, initiative, or task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, cookies, credentials, or sensitive incident data in Work Graph summaries.
+- If a rollout decision, incident note, runbook, blocker, or verification result should have been written to OrgX but was not, name that missed orchestration opportunity in the final status.

skills/orgx-orchestrator-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-orchestrator-agent
 description: OrgX orchestration execution contract for OpenClaw. Use for decomposing work into initiatives/workstreams/milestones/tasks and coordinating agents with explicit dependencies.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - orchestration
@@ -44,3 +44,10 @@ When creating work:
 - Use `orgx_emit_activity` frequently (append-only).
 - Use `orgx_apply_changeset` for entity mutations when the orchestration scope exposes it.
 - Use `orgx_request_decision` for human approvals or when running in a default-safe surface.
+
+## Work Graph Continuity
+
+- Use active OrgX reporting whenever initiative/workstream/milestone/task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, cookies, or private source material in Work Graph summaries.
+- Explicitly classify missed orchestration opportunities: absent OrgX writeback, unresolved decisions, disconnected artifacts, unclear owners, and blocked release gates.

skills/orgx-product-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-product-agent
 description: OrgX product execution contract for OpenClaw. Use for PRDs, scope decisions, acceptance criteria, and initiative planning tied to measurable outcomes.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - product
@@ -38,3 +38,10 @@ When producing product artifacts:
 - Use `orgx_emit_activity` for progress updates and next steps.
 - Use `orgx_request_decision` for product tradeoff approvals in default-safe mode.
 - Use `orgx_apply_changeset` for task/workstream mutations only when your scope explicitly exposes mutation tools.
+
+## Work Graph Continuity
+
+- Use active OrgX reporting when product, initiative, decision, or task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, private customer data, or sensitive strategy material in Work Graph summaries.
+- If a product decision, acceptance criterion, artifact, or launch gate should have been written to OrgX but was not, name that missed orchestration opportunity in the final status.

skills/orgx-sales-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orgx-sales-agent
 description: OrgX sales execution contract for OpenClaw. Use for outbound sequences, battlecards, qualification frameworks, and objection handling tied to ICP.
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 tags:
   - sales
@@ -39,3 +39,10 @@ When producing sales materials:
 - `orgx_emit_activity` for progress.
 - `orgx_request_decision` for pricing, messaging, and approval gates in default-safe mode.
 - Use `orgx_apply_changeset` only when your scope explicitly exposes mutation tools.
+
+## Work Graph Continuity
+
+- Use active OrgX reporting when account, initiative, decision, or task IDs are known; passive hooks are a backstop, not durable proof by themselves.
+- When a Work Graph report exists, preserve `work_graph_fingerprint` and `signup_hydration.hydration_key` in safe summaries or artifacts.
+- Never include raw transcripts, secrets, tokens, private prospect data, or sensitive deal context in Work Graph summaries.
+- If qualification evidence, pricing approval, objection data, or sales collateral should have been written to OrgX but was not, name that missed orchestration opportunity in the final status.