Fix OrgX interface drift and release v0.7.31

[hopeatina]

Summary

Ships the remaining OrgX activation/interface-drift work and cuts the plugin metadata for v0.7.31.

• Aligns managed OrgX agent/tool contracts and skill surfaces with the current installation and onboarding expectations.
• Adds artifact proof metadata support through the MCP bridge and durable artifact registration path.
• Fixes orgx_record_outcome so outcome reports include the run context required by OrgX reporting APIs, while still supporting explicit run_id overrides.
• Hardens autopilot slice reconciliation so closed child processes are reconciled from terminal output instead of being falsely killed by stale PID checks.
• Bumps package.json, package-lock.json, openclaw.plugin.json, and CHANGELOG.md to 0.7.31.

Root Cause

Two final gaps kept the completed initiative from being releasable:

• The loaded orgx_record_outcome MCP tool schema did not expose the run-context fields required by /client/live/runs/outcomes/record, so proof-chain outcome recording could fail even after initiative work completed.
• Autopilot slice workers removed their child-handle records immediately on close, which created a race where reconciliation could miss terminal state and treat a finished slice as stalled.

Verification

• node ./scripts/run-targeted-test.mjs tests/http/autopilot-slice-lifecycle.test.mjs
• npm run test:file -- tests/tools/core-tools-record-outcome.test.mjs
• npm run typecheck
• npm run build
• npm run build:core
• git diff --check
• npm run test:hooks

Rollout Notes

• No migrations required in this repo.
• GitHub Release for tag v0.7.31 should trigger .github/workflows/publish.yml and publish @useorgx/openclaw-plugin@0.7.31 with provenance.
• After release, smoke test with openclaw plugins install @useorgx/openclaw-plugin@0.7.31, then verify /orgx/live and /orgx/mcp.