Import + run-verify the project-bootstrap pipeline bundle (cortex #749)

[rafeekpro]

From cortex-project team agent — handing off a new pipeline bundle for DAP import + run-verification. No live channel needed; work this on your own clock.

What this is

The project-bootstrap pipeline (cortex epic #749, nodes built in #759–#767) now has a hand-built DAP export bundle. It's a 13-node, 5-human-gate pipeline that turns an idea-arena verdict into a fully scaffolded, cortex-managed project (GitHub repo + seeded files → wired PR-review-gate → dedicated DB → cortex registration → MVP decomposed into filed GitHub issues), then hands off to issue-implementer.

Where the bundle is

• Path: cortex/dap_bundles/project-bootstrap.pipeline-bundle.json
• Lands on cortex develop via lagowski/cortex-project#777 (in review now). Pull develop after that merges, or fetch the PR branch feat/project-bootstrap-dap-bundle.
• Format: pipeline-export/2, min_dap_version: 0.8.0.

Cortex-side verification already done (so you can trust the shape)

• cortex bundle validate → valid.
• All 9 distinct callable_paths import and resolve to real functions.
• tests/test_bundle_format.py + tests/test_imports.py green.

What I need from you (in-scope for DAP)

1. Import the bundle (strip _comment + install_instructions first): dap pipeline import … or POST /pipelines/import. Confirm it imports without schema error and report the assigned pipeline_id.
2. Graph sanity: confirm DAP builds the 13-node graph with the 5 gates (gate_params, gate_scope, gate_scaffold, gate_provision, gate_decompose) registered as interrupt_before pause points, and that the declarative conditional edges on the *_approved boolean flags resolve (no orphan/no-matching-edge hangs — especially the decompose_issues ⇄ gate_decompose dual-phase loop on gate_decompose_approved).
3. Do NOT do a full live run yet — the wire_gate / provision_db / register_project live paths (claude-bridge to lagoboard/pr-review-gate; k8s token resolution in the cortex namespace) are blocked on lagowski/cortex-project#747 until the LAGOVAULT→k8s secrets land. A dry import + graph-build validation is the ask; a gated dry-run that pauses at gate_params is a bonus if cheap.

Key contract notes (read before importing)

• State is top-level: project-bootstrap uses its own BootstrapState, NOT CortexState — there is no extensions.* carrier. Run inputs go at initial_state.{project_slug, repo_layout, stack, db_choice, arena_verdict} (+ optional arena_lens_flags). Nesting under extensions drops them.
• Gates are cortex.dap_steps.human_gate:noop markers; pause is via interrupt_before (approval_required_nodes), never POST /pause from a node (docs/ux: gate approval requires skip-node, not resume — document and add dedicated approve endpoint #164).
• gate_scaffold is a pure pass-through (no reject edge) — always continues on resume.

Out of scope (route elsewhere, don't action)

• Anything that mutates the cortex repo or merges PR feat(designer): LLM-per-node panel — assign backend profiles per node from the UI #777 — that's owner-only / cortex-side.
• Unblocking feat: 'what this agent does' from the callable's docstring (#747) #747 (LAGOVAULT→k8s) — operator-owned ops task.

Reply

Report under 200 words: import result (+ pipeline_id), graph-build outcome per item 2, and any schema/edge issue with the exact message. If anything here is outside DAP's domain, say so and I'll re-route.

Reference

• Bundle authoring spec: cortex .claude/rules/pipeline-design.md
• A2A protocol: AGENT_TO_AGENT_COMMUNICATION.md (LAGOVAULT GENERAL CONFIG)