Auto-bootstrap prompt agents in empty Foundry projects

[placerda]

Summary

Adds an optional prompt_agent_bootstrap block to �gentops.yaml. When the prompt-agent deploy workflow runs against a dev / qa / prod Foundry project that does not yet contain the seed agent, it reads that block plus prompt_file and creates the first version automatically (recorded as action: ""bootstrapped"" in oundry-agent.json).

This eliminates the previous per-environment manual seeding step that forced operators to recreate the same prompt agent in every Foundry project before CI could promote prompts to it.

Why

The current prompt-agent quickstart asked the user to manually create travel-agent:1 in two Foundry projects (sandbox + dev). PO feedback: Não faz sentido. Eu deveria criar apenas no sandbox; o dev deve sempre atualizar com pipeline de continuous deployment. This change makes sandbox-only seeding the supported path.

Scope

Code:

• core/agentops_config.py – PromptAgentBootstrap Pydantic model (required model; optional description, model_parameters, ools) + prompt_agent_bootstrap field on AgentOpsConfig.
• pipeline/prompt_deploy.py – stage_prompt_agent_candidate now branches on 404 lookup; new _bootstrap_prompt_agent and strict _is_not_found_error helpers. New action: ""bootstrapped"".
• services/workflow_analysis.py – emits prompt_agent_bootstrap_missing warning when prompt-agent mode lacks the block.
• emplates/agentops.yaml – commented bootstrap example.

Docs:

• utorial-prompt-agent-quickstart.md – sandbox-only seeding (section 4), updated yaml example + bootstrap callout + project_endpoint warning (section 9), stage-on-empty flow (section 11), action: bootstrapped first-deploy artifact (section 13).
• utorial-end-to-end.md – multi-env bootstrap callout pointing to the prompt-agent quickstart.
• �gentops-config and �gentops-workflow SKILL.md – documented the new block and the bootstrap-on-empty branch.
• CHANGELOG.md Unreleased – Added entry.

Tests (16 new):

• est_prompt_deploy.py – bootstrap path, missing config raises, auth errors propagate, ignores bootstrap when seed exists, sanity check on _is_not_found_error.
• est_agentops_config.py – schema validation (default None, model-only, full payload, empty-model rejected, unknown fields rejected).
• est_workflow_analysis.py – warning fires when bootstrap missing, silent when present.

Full suite: 784 passed, 3 skipped.

Safety

• 401 / 403 and other non-404 errors continue to propagate. The bootstrap path only triggers on a genuine agent does not exist 404. Test test_stage_prompt_agent_propagates_auth_errors confirms.
• prompt_agent_bootstrap is optional. Existing configs that don't set it keep the old behavior: the stage step raises on 404 with the original error.
• Schema is additive; no breaking change to agentops.yaml.

Rubber-duck review

Pre-implementation critique surfaced several blind spots that shaped the final design:

• Field name (prompt_agent_bootstrap over prompt_agent_defaults) to communicate one-time semantics.
• Strict 404 detection so RBAC issues never get masked.
• project_endpoint precedence warning in the tutorial (yaml wins over env, breaks multi-env).
• Required description for workflow analyze warning so users learn about the block before hitting CI.