Update to OrgX

{
  "name": "orgx-runtime-reporting",
  "description": "Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.",
  "included_files": [],
  "skill_md_contents": "---\nname: orgx-runtime-reporting\ndescription: Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.\n---\n\n# OrgX Runtime Reporting\n\nUse this skill when Codex should keep OrgX updated during execution.\n\n## Reporting contract\n\nThere are two reporting paths:\n\n- **Active path:** call OrgX MCP tools during the work when you know the\n  initiative, task, decision, blocker, or artifact context.\n- **Chronicle readout:** for operator reporting, call\n  `get_operator_chronicle` first when available and present\n  `reportingNarrative.briefMarkdown` before drilling into individual entities.\n- **Stale-client fallback:** if bootstrap or docs advertise\n  `get_operator_chronicle` but the current AI client session has not refreshed\n  its callable tool list, immediately call `orgx_recommend` or\n  `_orgx_recommend` with `mode: \"morning_brief\"` and present the returned\n  `reportingNarrative.briefMarkdown`. Do not ask the user to reconnect before\n  giving the report.\n- **Passive backstop:** Codex runtime hooks installed by `orgx-wizard hooks\n  install` record compact session events and run summary-only local Work Graph\n  reconciliation on `Stop`.\n\nDo not treat hook presence as a substitute for intentional OrgX writes. Hooks\nanswer whether OrgX was used and can write a local report automatically; MCP\ncalls, or an explicitly opted-in successful Work Graph post, make the work\ndurable in OrgX while the session is still fresh.\n\n## Workflow\n\n1. Resolve available IDs from args, env, or the current OrgX context:\n- `ORGX_INITIATIVE_ID`\n- `ORGX_WORKSTREAM_ID`\n- `ORGX_TASK_ID`\n- `ORGX_RUN_ID`\n- `ORGX_CORRELATION_ID`\n\n2. For reporting questions, retrieve the operator chronicle:\n- Use `get_operator_chronicle` with `period: \"30d\"` for broad clarity when it\n  is callable in the current client.\n- Use `period: \"day\"` or `period: \"week\"` when the user asks for yesterday or\n  this week.\n- If `get_operator_chronicle` is not callable in the current client, use the\n  existing `orgx_recommend` / `_orgx_recommend` fallback with\n  `mode: \"morning_brief\"` and the broadest supported period. Treat the direct\n  tool as preferred, but do not block on client schema refresh.\n- Lead with `reportingNarrative.briefMarkdown`, then call out gaps and the\n  next action.\n\n3. Emit activity at meaningful milestones:\n- `intent`\n- `execution`\n- `handoff`\n- `blocked`\n- `completed`\n\n4. Register proof of work:\n- When you produce a file, diff, document, screenshot, or report, register it as an artifact with a concrete summary.\n\n5. Handle blockers structurally:\n- If judgment is required, request a decision with explicit options.\n- If context is missing, report the exact missing dependency.\n\n6. Close execution cleanly:\n- When the task is complete and verified, emit completion activity and update entity state if the task ID is available.\n\n7. If no OrgX IDs are available:\n- Continue the work, but make the final response easy for the hook reconciler to\n  classify: name decisions, artifacts, blockers, next actions, and verification.\n- Do not claim OrgX was updated unless an MCP tool or API call actually\n  succeeded.\n\n8. Preserve Work Graph continuity:\n- When a Work Graph report is generated, include its `work_graph_fingerprint`\n  and `signup_hydration.hydration_key` in summaries or artifacts that are safe\n  to store.\n- Automatic Stop-hook reconciliation writes the latest local report to\n  `~/.config/useorgx/wizard/hooks/reports/latest-work-graph-report.json`.\n- Stop-hook posting requires `ORGX_HOOK_RECONCILE_POST=true` or\n  `ORGX_WIZARD_HOOK_RECONCILE_POST=true` plus `ORGX_API_KEY`.\n- Treat the fingerprint as the durable claim key that lets OrgX hydrate\n  pre-signup audit value into a user's future workspace.\n- Never derive the fingerprint from secrets or raw transcripts that would need\n  to leave the local machine.\n\n## Quality bar\n\n- Never post empty status updates.\n- Messages must be evidence-based and specific.\n- Include OrgX IDs whenever available.\n- Use `source_client=codex`.\n- Preserve secrets: never emit tokens, cookies, API keys, or storage state into\n  activity, retro, hook summaries, or final reports.\n"
}