@apexops/cli 0.10.0-next.5 → 0.11.0-next.1

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-governance.instructions.md

@@ -1,12 +0,0 @@
----
-description: "Consumer governance evidence and IaC planning boundaries"
-applyTo: "**/04-governance-constraints.md, **/04-governance-constraints.json, **/04-implementation-plan.md"
----
-
-# APEX Governance And Planning
-
-- Treat governance constraints as evidence-bound inputs, not assumptions.
-- Record unavailable policy evidence as a blocker or explicit uncertainty.
-- Bind cost, resilience, security, and naming decisions to the selected project and environment.
-- Keep implementation plans track-neutral until the kernel selects Bicep or Terraform generation.
-- Do not query, exempt, assign, or deploy Azure resources directly from planning guidance.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-instruction-authoring.instructions.md

@@ -1,12 +0,0 @@
----
-description: "Consumer custom instruction authoring and scope rules"
-applyTo: ".github/instructions/**/*.instructions.md"
----
-
-# APEX Instruction Authoring
-
-- Use `description` and a narrow `applyTo` pattern in YAML frontmatter.
-- Name consumer instructions with the `apex-` prefix.
-- Keep instructions imperative, concise, and scoped to consumer files.
-- Do not duplicate skill content, repository maintenance rules, or direct operational authority.
-- State evidence and safety boundaries where guidance could otherwise be interpreted as authorization.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-javascript.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer JavaScript and Node.js implementation guidance"
-applyTo: "**/*.{js,mjs,cjs}"
----
-
-# APEX JavaScript Rules
-
-- Use ESM syntax and explicit error handling.
-- Keep command execution bounded, argument-based, and free of shell interpolation.
-- Parse structured input with a parser and validate external data before use.
-- Avoid writing consumer state outside the owning APEX MCP or CLI operation.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-json.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer JSON and JSONC configuration rules"
-applyTo: "**/*.{json,jsonc}"
----
-
-# APEX JSON Rules
-
-- Format JSON with two-space indentation and a final newline.
-- Use JSONC comments only where the consumer client supports JSONC.
-- Keep configuration declarative and free of secrets, tokens, or connection strings.
-- Preserve project, run, environment, and track identifiers exactly when they are contract fields.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-markdown.instructions.md

@@ -1,13 +0,0 @@
----
-description: "Consumer Markdown formatting and evidence language rules"
-applyTo: "**/*.md"
----
-
-# APEX Markdown Rules
-
-- Use one H1 and structured H2 sections.
-- Keep lines within 120 characters and specify languages on fenced code blocks.
-- Use descriptive links and avoid feature claims that lack evidence.
-- Keep generated artifact content consistent with its accepted APEX contract.
-- Use accepted APEX templates before adding presentation or diagram content.
-- Use `mermaid` for inline flows and `python-diagrams` for standalone `.py`, `.png`, and `.svg` artifacts.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-powershell.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer PowerShell safety and idempotent scripting guidance"
-applyTo: "**/*.{ps1,psm1}"
----
-
-# APEX PowerShell Rules
-
-- Use approved cmdlets and explicit parameters.
-- Keep scripts non-interactive and idempotent where possible.
-- Require explicit confirmation through APEX project lifecycle prompts before destructive work.
-- Do not embed credentials, tokens, or direct cloud deployment authority in scripts.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-prompt-authoring.instructions.md

@@ -1,12 +0,0 @@
----
-description: "Consumer prompt and model instruction boundaries"
-applyTo: ".github/agents/**/*.agent.md, .github/prompts/**/*.prompt.md"
----
-
-# APEX Prompt Rules
-
-- Use the model assigned by the managed role and do not override it redundantly.
-- Keep prompts outcome-focused with explicit scope, input, output, and stop conditions.
-- Keep tool lists minimal and use native client questions for user-owned decisions.
-- Do not grant direct mutation, secrets, repository maintenance, or cloud lifecycle authority.
-- Route workflow state changes through the declared APEX MCP operation.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-python.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer Python implementation and validation guidance"
-applyTo: "**/*.py"
----
-
-# APEX Python Rules
-
-- Use explicit dependencies, typed boundaries, and structured parsing.
-- Keep Azure and workflow state operations behind declared APEX capabilities.
-- Validate external input and produce concise, actionable errors.
-- Do not embed secrets, credentials, or direct deployment commands.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-safe-file-edits.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer safe file editing and generated artifact boundaries"
-applyTo: "**/*.{js,mjs,cjs,ts,tsx,jsx,py,ps1,sh,bicep,tf}"
----
-
-# APEX Safe File Edits
-
-- Use the client file-editing capability for source changes; do not create files through shell redirection.
-- Do not use heredocs, `tee`, or inline interpreters to write project code or artifacts.
-- Write accepted workflow outputs only through the owning APEX MCP operation.
-- Keep generated files inside the selected project and run boundaries.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-safe-shell.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer shell safety and non-interactive command rules"
-applyTo: ".github/agents/**/*.agent.md, .github/prompts/**/*.prompt.md, .github/skills/**/SKILL.md"
----
-
-# APEX Shell Safety
-
-- Use non-interactive commands only; do not use confirmation flags or prompt-driven shell builtins.
-- Keep command output bounded and summarize results instead of replaying large logs.
-- Do not request, print, store, or pass secrets through chat or command arguments.
-- Use explicit paths and arguments; avoid shell interpolation for consumer workflow operations.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-shell.instructions.md

@@ -1,11 +0,0 @@
----
-description: "Consumer shell script structure and safety guidance"
-applyTo: "**/*.sh"
----
-
-# APEX Shell Rules
-
-- Use `set -euo pipefail` when compatible with the script's contract.
-- Validate arguments and quote variable expansions.
-- Use structured tools for JSON instead of string parsing.
-- Keep scripts non-interactive and do not embed secrets or direct cloud lifecycle commands.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-skill-authoring.instructions.md

@@ -1,13 +0,0 @@
----
-description: "Consumer skill authoring and progressive disclosure rules"
-applyTo: ".github/skills/**/SKILL.md"
----
-
-# APEX Skill Authoring
-
-- State the supported decision or workflow outcome in the skill description.
-- Keep the main skill concise and place detailed guidance in `references/` files.
-- Describe prerequisites and evidence boundaries before operational guidance.
-- Do not grant new MCP tools, shell access, state mutation, deployment, or secret handling.
-- Route state changes through the owning APEX MCP operation.
-- Keep examples decision-oriented; do not claim live Azure facts without current evidence.

package/assets/client-projections/github-copilot-vscode/.github/instructions/apex-terraform.instructions.md

@@ -1,12 +0,0 @@
----
-description: "Consumer Terraform security, provider, and repeatability guidance"
-applyTo: "**/*.tf"
----
-
-# APEX Terraform Rules
-
-- Prefer Azure Verified Modules and explicit provider constraints.
-- Keep backend, provider, and environment inputs separate from generated resource intent.
-- Use managed identity and Entra-based access patterns instead of shared keys or secrets.
-- Derive names from approved workload and environment inputs.
-- Validate the exact generated configuration and lock state through the APEX workflow before preview.

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-architecture/SKILL.md

@@ -1,36 +0,0 @@
----
-name: apex-architecture
-description: "Provides internal APEX architecture guidance for traceable WAF, identity, network, recovery, and cost decisions."
-user-invocable: false
----
-
-## APEX Architecture
-
-Use this skill only for an active architecture task.
-
-## Prerequisites
-
-- Requirements and recorded architecture decisions are projected by `apex/taskContext`.
-- Required governance, pricing, quota, region, and service-availability evidence is present and current.
-
-## Workflow
-
-1. Use only accepted requirements and current task-context evidence. Trace each proposed resource and decision to
-   projected requirements, evidence references, and required SLO or workload decisions where supplied.
-2. Explain Security, Reliability, Cost, Operational Excellence, and Performance Efficiency trade-offs where material.
-3. Keep identity, networking, diagnostics, recovery, data, and lifecycle decisions explicit.
-4. Present user-owned choices only when `apex/nextTask` returns `needs_input`; record them through `apex/recordInput`
-   before reading the architecture task context.
-5. Return missing, unavailable, or stale discovery as a blocker rather than inventing evidence or asserting a live
-   provider contract.
-6. Stage `architecture`, `cost-estimate`, and `workload-decision-manifest`, then call `apex/completeTask` once with
-   every required output in `outputs`. Do not submit a single-output completion.
-
-## Output
-
-Return the kernel result, unresolved decisions, and evidence references supplied by the task envelope.
-
-## Boundaries
-
-Do not claim an evidence shape, freshness duration, external provider result, or gate outcome beyond the task envelope
-and kernel result. Do not emit secret values; preserve only typed references accepted by the current contract.

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/SKILL.md

@@ -1,65 +0,0 @@
----
-name: apex-artifacts
-description: "Presents accepted APEX typed artifacts as bounded Markdown views. Use for renderer templates, document slots, provenance receipts, resource inventories, cost views, runbooks, and reference-only document outlines."
-user-invocable: false
----
-
-# APEX Artifact Presentations
-
-Present accepted typed artifacts without creating a second source of truth. The artifact schema, accepted values,
-kernel decisions, and accepted object hash remain canonical; Markdown is a derived view.
-
-## Prerequisites
-
-- An accepted typed artifact and `apex/taskContext` are available.
-- The document registry exposes the matching renderer and all required slots.
-- Any referenced evidence is accepted, immutable, and safe to disclose.
-
-## Rules
-
-1. Select an active template only when the renderer binds it to the accepted artifact kind.
-2. Preserve the selected template's heading order, slot meaning, and provenance receipt.
-3. Fill slots only from `apex/taskContext`, accepted artifact values, accepted evidence, or explicit kernel decisions.
-4. Preserve accepted unknown, unavailable, not-applicable, and deferred states exactly; never turn them into facts.
-5. Stop when a required slot, source identifier, template identifier, or renderer capability is unavailable.
-6. Return the bounded document request or kernel-rendered receipt. Never write workflow files or mutate artifact state.
-7. Do not use Markdown as gate evidence, claim validation or deployment occurred, or alter values to fit an outline.
-
-## Workflow
-
-1. Confirm artifact acceptance, kind, disclosure boundary, and renderer support.
-2. Choose an active binding below. Use an advisory outline only to shape a supported custom presentation.
-3. Map every required slot to an accepted source and retain source identifiers for traceability.
-4. Render once, then check heading order, unresolved slots, status language, links, and provenance.
-5. Correct the bounded request and re-render until the renderer accepts it; otherwise return the blocker.
-
-Read [presentation conventions](references/presentation-conventions.md) before preparing any document request.
-
-## Available Documents
-
-- [Requirements document](templates/requirements.md) - present an accepted `requirements` artifact.
-
-The registry also exposes direct, non-template renderers for run status, deployment preview, approval evidence, and
-resource inventory. They are read-only views of their accepted typed sources.
-
-## Reference-Only Outlines
-
-- [Architecture assessment](templates/architecture-assessment.md), [cost estimate](templates/cost-estimate.md),
-  [governance constraints](templates/governance-constraints.md), [implementation plan](templates/implementation-plan.md),
-  [deployment summary](templates/deployment-summary.md), [operations runbook](templates/operations-runbook.md), and
-  [resource inventory](templates/resource-inventory.md) are reference-only until the registry has a matching source
-  producer and renderer.
-- [Additional document outlines](references/reference-only-outlines.md) preserve useful source-document semantics.
-
-Reference-only outlines never authorize rendering, file creation, cloud queries, repository reads, or state changes.
-If a caller needs one, require a supported custom-document capability or clearly report that the capability is absent.
-
-Source template structure may inform an outline, but it is not a producer or renderer registration. A template becomes
-renderable only when a typed producer, registry binding, and document receipt are all available.
-
-The current registry declares no Mermaid-capable slots. Do not request inline diagrams for these documents.
-
-## Output
-
-Return a bounded document request or kernel-rendered Markdown receipt. Include projected source and template identifiers,
-unknowns, deferrals, evidence references, and capability blockers.

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/references/presentation-conventions.md

@@ -1,52 +0,0 @@
-## Presentation Conventions
-
-Use a template only after the kernel accepts the matching typed artifact. Keep the artifact and its kernel-rendered
-document receipt canonical; the Markdown presentation is a derived view.
-
-### Authority And Provenance
-
-- Record the renderer-projected artifact identifier and template identifier.
-- Keep accepted values, units, scopes, status, and evidence references unchanged.
-- Label design, planned, simulated, expected, and observed values distinctly.
-- Never claim current Azure state, successful validation, or deployment from a template placeholder.
-
-### Slot Rules
-
-- Replace every required `{slot-name}` from accepted values or explicit kernel decisions.
-- Preserve `unknown`, `deferred`, `unavailable`, and `not applicable` as supplied by the renderer.
-- Keep optional sections only when accepted data supports them; do not manufacture empty success claims.
-- Stop and report a blocker when a required slot, renderer, artifact kind, or disclosure permission is unavailable.
-- Do not infer, invent, normalize, or use a presentation to change artifact meaning.
-
-### Traceability
-
-- Connect requirements to decisions, controls, implementation intent, risks, and accepted evidence where slots permit.
-- For governance, map each accepted constraint to a control, adaptation, exemption, or unsatisfied blocker.
-- For plans and inventories, account for every accepted resource and identify coverage gaps explicitly.
-- For as-built views, show design-versus-observed variance only when both accepted values exist.
-
-### Cost Semantics
-
-- State currency, region, pricing basis, usage quantities, query or evidence time, and expected variance.
-- Separate fixed or baseline cost from usage-sensitive cost and list redesign or scale triggers.
-- Represent savings as `quantified`, `not quantified`, or `not applicable`; never render zero as "not evaluated."
-- Do not present mutable prices as current unless accepted pricing evidence carries that claim.
-
-### Document Shape
-
-- Preserve template H2 order and use H3 sections for detail.
-- Prefer concise tables for comparisons, controls, resources, risks, and ownership.
-- Use callouts only for material notes, warnings, blockers, or irreversible consequences.
-- Include inline Mermaid only for a supported diagram slot and only from accepted nodes and relationships.
-- Keep links relative or from accepted source URLs; do not invent repository paths or portal links.
-
-### Receipt
-
-When available, include renderer-provided artifact and template identifiers, evidence identifiers, and render status.
-
-### Validation Loop
-
-1. Check required slots and accepted source mappings before rendering.
-2. Render through the kernel capability.
-3. Check unresolved placeholders, heading order, status wording, disclosure, links, and receipt identifiers.
-4. Correct the request and re-render. If the renderer still cannot satisfy a required slot, return the blocker.

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/references/reference-only-outlines.md

@@ -1,78 +0,0 @@
-## Reference-Only Document Outlines
-
-These outlines preserve useful document semantics from the source skill. They do not declare artifact kinds, renderer
-bindings, workflow phases, file names, or authority to read repositories or query Azure. Use one only when a supported
-custom-document capability supplies accepted values for every required slot.
-
-### Preflight Evidence
-
-- Purpose and validation scope
-- Module or provider schema checks
-- Parameter type and interface checks
-- Region or service availability constraints
-- Known pitfalls, pass/fail evidence, and unresolved blockers
-
-Never infer a pass from planned configuration. Without accepted validation evidence, report the capability as absent.
-
-### Implementation Reference
-
-- Accepted implementation location or identifier
-- File or module structure from accepted inventory
-- Validation status with evidence references
-- Resources represented by the implementation
-- Key interfaces, decisions, limitations, and follow-up
-
-Do not add deployment commands or claim files exist unless accepted evidence provides them.
-
-### Documentation Package Index
-
-- Package contents and status
-- Accepted source artifacts and provenance
-- Workload summary
-- Related accepted resources and bounded links
-- Missing package items and deferrals
-
-### Design Document
-
-- Purpose, audience, objectives, constraints, assumptions, and stakeholders
-- Architecture overview and accepted relationships
-- Networking, storage, compute, identity, security, compliance, backup, and monitoring
-- Design decisions, operational implications, evidence, risks, and appendices
-
-Only include domains represented by accepted inputs. Keep planned and observed state distinct.
-
-### Backup And Recovery Plan
-
-- Recovery objectives by service tier
-- Backup scope, retention, restore approach, and ownership
-- Failover and failback decision points
-- Test schedule and accepted test evidence
-- Communications, dependencies, recovery procedures, and blockers
-
-Do not invent executable recovery commands. A missing tested procedure or owner is a blocker, not a placeholder success.
-
-### Compliance Matrix
-
-- Framework and scope
-- Requirement-to-control-to-evidence mapping
-- Gaps with severity, risk, owner, and remediation state
-- Evidence collection metadata and audit trail
-- Exceptions, expirations, deferrals, and residual risk
-
-Compliance percentages require accepted numerator, denominator, and scope. Otherwise present coverage as unknown.
-
-### Project Index
-
-- Workload summary and status
-- Accepted artifact catalog with provenance
-- Architecture preview only when a supported media slot exists
-- Resource summary, unresolved blockers, and related bounded links
-
-### Lessons And Improvement View
-
-- Accepted observations grouped by severity and workflow area
-- What happened, impact, corrective action, and evidence
-- Recommendations with owners and affected capability or contract
-- Deferred improvements and rationale
-
-Do not create improvement state or claim a correction was applied; project only kernel-accepted decisions.

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/templates/architecture-assessment.md

@@ -1,35 +0,0 @@
-## {artifact-title}
-
-> Presentation receipt: artifact `{artifact-identifier}`; template `{template-identifier}`.
-
-## Requirements Validation
-
-{requirements-validation}
-
-## Executive Summary
-
-{executive-summary}
-
-## Well-Architected Assessment
-
-{waf-assessment}
-
-## Resource And SKU Recommendations
-
-{resource-recommendations}
-
-## Architecture Decisions
-
-{architecture-decisions}
-
-## Implementation Handoff
-
-{implementation-handoff}
-
-## Risks And Deferrals
-
-{risks-and-deferrals}
-
-## References
-
-{references}

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/templates/cost-estimate.md

@@ -1,47 +0,0 @@
-## {artifact-title}
-
-> Presentation receipt: artifact `{artifact-identifier}`; template `{template-identifier}`.
-
-## Cost At A Glance
-
-{cost-at-a-glance}
-
-## Decision Summary
-
-{decision-summary}
-
-## Requirements To Cost Mapping
-
-{requirements-cost-mapping}
-
-## Cost Drivers And Sensitivities
-
-{cost-drivers-and-sensitivities}
-
-## Assumptions
-
-{assumptions}
-
-## Cost Breakdown
-
-{cost-breakdown}
-
-## Savings Opportunities
-
-{savings-state-and-opportunities}
-
-## Guardrails And Change Triggers
-
-{guardrails-and-change-triggers}
-
-## Risks And Deferrals
-
-{risks-and-deferrals}
-
-## Pricing Evidence
-
-{pricing-evidence}
-
-## References
-
-{references}

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/templates/deployment-summary.md

@@ -1,35 +0,0 @@
-## {artifact-title}
-
-> Presentation receipt: artifact `{artifact-identifier}`; template `{template-identifier}`.
-
-## Preflight Evidence
-
-{preflight-evidence}
-
-## Execution Context
-
-{execution-context}
-
-## Change Summary
-
-{change-summary}
-
-## Resource Results
-
-{resource-results}
-
-## Outputs
-
-{outputs}
-
-## Outputs And Follow-Up
-
-{outputs-and-follow-up}
-
-## Exceptions And Deferrals
-
-{exceptions-and-deferrals}
-
-## References
-
-{references}

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/templates/governance-constraints.md

@@ -1,35 +0,0 @@
-## {artifact-title}
-
-> Presentation receipt: artifact `{artifact-identifier}`; template `{template-identifier}`.
-
-## Discovery And Attestation
-
-{discovery-and-attestation}
-
-## Constraint Summary
-
-{constraint-summary}
-
-## Policy And Control Mapping
-
-{policy-and-control-mapping}
-
-## Adaptations And Exceptions
-
-{adaptations-and-exceptions}
-
-## Required Tags And Security Controls
-
-{tags-and-security-controls}
-
-## Cost And Network Constraints
-
-{cost-and-network-constraints}
-
-## Blockers And Deferrals
-
-{blockers-and-deferrals}
-
-## References
-
-{references}

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/templates/implementation-plan.md

@@ -1,43 +0,0 @@
-## {artifact-title}
-
-> Presentation receipt: artifact `{artifact-identifier}`; template `{template-identifier}`.
-
-## Plan Summary
-
-{plan-summary}
-
-## Resource Inventory
-
-{resource-inventory}
-
-## Governance Coverage
-
-{governance-coverage}
-
-## Module And Interface Structure
-
-{module-and-interface-structure}
-
-## Planned Work
-
-{planned-work}
-
-## Code Generation Contract
-
-{code-generation-contract}
-
-## Dependencies And Delivery Sequence
-
-{dependencies-and-delivery-sequence}
-
-## Naming And Security Decisions
-
-{naming-and-security-decisions}
-
-## Risks And Deferrals
-
-{risks-and-deferrals}
-
-## References
-
-{references}

package/assets/client-projections/github-copilot-vscode/.github/skills/apex-artifacts/templates/operations-runbook.md

@@ -1,35 +0,0 @@
-## {artifact-title}
-
-> Presentation receipt: artifact `{artifact-identifier}`; template `{template-identifier}`.
-
-## Quick Reference
-
-{quick-reference}
-
-## Health And Routine Operations
-
-{health-and-routine-operations}
-
-## Monitoring And Incident Response
-
-{monitoring-and-incident-response}
-
-## Common Procedures
-
-{common-procedures}
-
-## Maintenance And Recovery
-
-{maintenance-and-recovery}
-
-## Escalation And Ownership
-
-{escalation-and-ownership}
-
-## Change Evidence
-
-{change-evidence}
-
-## References
-
-{references}