session-bootstrap

name	session-bootstrap
description	Thin Codex skill shim for node_session_bootstrap. Use to initialize a session contract snapshot and launchd scheduler plan.

Session Bootstrap

This skill is a thin Codex runtime request adapter shim over the OmniMarket node_session_bootstrap node. The node owns session contract validation, snapshot persistence, and scheduler-plan emission. Do not add timer setup logic or fallback scheduler logic to this skill.

Arguments

Argument	Description	Default
session_id	UUID for the session run	Required
session_label	Human-readable session label	<today> session
phases_expected	Comma-separated expected phases	build_loop,merge_sweep,platform_readiness
max_cycles	Maximum build loop cycles (0 = unlimited)	0
cost_ceiling	Advisory cost ceiling in USD	10.0
session_mode	Session mode: build, close-out, or reporting	build
active_sprint_id	Explicit Linear cycle id or auto-detect	auto-detect
model_routing_preference	local-first, frontier-only, or hybrid	local-first
state_dir	State output directory	.onex_state
dry_run	Build artifacts without mutating scheduler state	false
target_runtime_address	Optional runtime://... runtime target	Uses ONEX_TARGET_RUNTIME_ADDRESS when set

Dispatch

Run from the omnimarket repo or an omnimarket worktree:

env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py \
  --command-name "session_bootstrap" \
  --payload '<json-payload>' \
  --timeout-ms 30000

If the user supplies a runtime://... target, add --target-runtime-address '<runtime-address>' to the request command. If the argument is omitted, the wrapper uses ONEX_TARGET_RUNTIME_ADDRESS when set.

For event-bus-free preflight, add --compile-only. This validates the payload, command topic, response topic, correlation id, timeout, and target runtime address without publishing to Kafka or starting a runtime.

Build the payload with a nested contract object. A minimal shape is:

{
  "session_id": "<session-id>",
  "session_mode": "build",
  "active_sprint_id": "auto-detect",
  "model_routing_preference": "local-first",
  "state_dir": ".onex_state",
  "dry_run": false,
  "contract": {
    "session_id": "<same session-id>",
    "session_label": "<today> session",
    "phases_expected": ["build_loop", "merge_sweep", "platform_readiness"],
    "max_cycles": 0,
    "cost_ceiling_usd": 10.0,
    "session_mode": "build",
    "active_sprint_id": "auto-detect",
    "model_routing_preference": "local-first"
  }
}

Map user arguments into that shape:

• cost_ceiling -> contract.cost_ceiling_usd
• session_label -> contract.session_label
• phases_expected -> contract.phases_expected as a JSON array of strings
• max_cycles -> contract.max_cycles
• dry_run -> top-level dry_run, and mirror it into contract.dry_run if the user explicitly asks for that contract flag

Keep session_id, session_mode, active_sprint_id, and model_routing_preference aligned between the top-level request and the nested contract.

If ok is true and output_payloads is present, treat output_payloads[0] as the primary node result.

If ok is false, surface error.code and error.message directly.

Contract

• Backing node: src/omnimarket/nodes/node_session_bootstrap/
• Pattern B request wrapper: scripts/run_codex_runtime_request.py
• Command name: session_bootstrap
• Runtime topic: onex.cmd.omnimarket.session-bootstrap-start.v2
• Completion topic: onex.evt.omnimarket.session-bootstrap-completed.v2

Output

Prefer output_payloads[0]. Render the node result with status, contract_path, crons_registered, and warnings. Treat an empty crons_registered list as valid when the node emits the launchd scheduler plan without activating any cron shim.