[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASMC10VA4PFB2D2KMN80AA":3,"skill-same:01M7ASMC10VA4PFB2D2KMN80AA":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASMC10VA4PFB2D2KMN80AA","vibey-bootstrap-core",null,"Use when installing or consuming the vibey-bootstrap Python library (v4.0.0) and its v1 core. Covers pip install and the optional-extras matrix (fastapi, servicebus, sumologic, logging-all, db, email, http, documentdb, governance, aks, vibey-bootstrap scaffold, all, etc.), the 4-phase bootstrap that breaks the logging↔configuration circular dependency, initialize_application \u002F get_bootstrap_logger, configuration precedence and the local-override rule, EnhancedConfigRepository, SecretsRepository, Key Vault references, DI interfaces, RepositoryError\u002FConfigurationError\u002FKeyVaultError, and v1 environment variables (APPLICATIONINSIGHTS_CONNECTION_STRING, AZURE_APP_CONFIGURATION_CONNECTION_STRING, AZURE_KEY_VAULT_URL, LOG_LEVEL). Triggers on vibey-bootstrap, vibey_bootstrap, Azure Functions\u002Fcontainer app startup config, App Configuration + Key Vault loading, load_to_environ, or installing the bootstrap extras from the vibey distribution.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fvibey-bootstrap\u002Fskills\u002Fvibey-bootstrap-core\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vibey-bootstrap-core\ndescription: \"Use when installing or consuming the vibey-bootstrap Python library (v4.0.0) and its v1 core. Covers pip install and the optional-extras matrix (fastapi, servicebus, sumologic, logging-all, db, email, http, documentdb, governance, aks, vibey-bootstrap scaffold, all, etc.), the 4-phase bootstrap that breaks the logging↔configuration circular dependency, initialize_application \u002F get_bootstrap_logger, configuration precedence and the local-override rule, EnhancedConfigRepository, SecretsRepository, Key Vault references, DI interfaces, RepositoryError\u002FConfigurationError\u002FKeyVaultError, and v1 environment variables (APPLICATIONINSIGHTS_CONNECTION_STRING, AZURE_APP_CONFIGURATION_CONNECTION_STRING, AZURE_KEY_VAULT_URL, LOG_LEVEL). Triggers on vibey-bootstrap, vibey_bootstrap, Azure Functions\u002Fcontainer app startup config, App Configuration + Key Vault loading, load_to_environ, or installing the bootstrap extras from the vibey distribution.\"\n---\n\n> **vibey-bootstrap** is the library formerly published as `azure-bootstrap` (renamed in 4.0.0: package `vibey-bootstrap`, import `vibey_bootstrap`, CLI `vibey-bootstrap`; `azbootstrap` remains as a deprecated alias). Feature-tier labels below (v2 primitives, v3 modules) are historical and unchanged.\n\n# Azure Bootstrap — Installation & v1 Core (4-phase bootstrap)\n\n`vibey-bootstrap` solves the **logging ↔ configuration circular dependency** every\nAzure Functions \u002F container app hits at startup (you need logging to report config\nloading, but App Insights logging needs config to initialize). On top of that v1\ncore, v2 adds a large, opt-in, framework-agnostic \"cross-cutting layer\": structured\nlogging, correlation, tracing, counters, tiered alerts, an error vocabulary, ingress\nhardening, Service Bus plumbing, webhook auth, AI usage tracking, health probes, a\nv2.1 logging-transport layer (console \u002F App Insights \u002F Sumo Logic), and v4.0.0 adds\nseven more logging transports plus DB\u002Foutbox, email, hardened HTTP, AKS runtime,\ngovernance, and an `vibey-bootstrap` scaffold CLI — all opt-in behind pip extras.\n\n> **`vibey-bootstrap` is a pure Python package.** It ships inside the `vibey`\n> distribution on PyPI (vibey ADR-0037) and has\n> **no JavaScript\u002FTypeScript distribution** — you cannot `npm install` or `import` it\n> from a Next.js app. (For TS, see the `vibey-bootstrap-typescript` skill: HTTP client\n> integration with a Python backend, and porting the patterns to TypeScript.)\n\n**Compatibility:** the source and the distribution that ships it support Python **≥ 3.12**.\nDistribution: `pip install vibey-engine` (PyPI, MIT) — there is no separate\n`vibey-bootstrap` project (vibey ADR-0037). v4.0.0 is **additive** — every v1\u002Fv2 import path, symbol, signature, and\ndefault is unchanged; opt into new extras and env flags. See `MIGRATING-TO-V3.md`.\n\n## 1. Installation & extras\n\n```bash\npip install vibey-engine                     # the whole family; vibey_bootstrap importable\npip install 'vibey-engine[azure]'            # App Configuration + Key Vault + App Insights\npip install 'vibey-engine[bootstrap-all]'    # every optional dependency any extra below needs\n```\n\n**Extra names.** The matrix below lists the extras as `vibey-bootstrap`'s own\n`pyproject.toml` declares them, and they still select what each feature needs when the\npackage is installed from the tree. On the `vibey-engine` package there is no per-feature\nsuccessor spelling: the replacements are the two aggregates above (vibey ADR-0037).\n\n### Core dependencies (always installed)\n\n```text\nazure-appconfiguration-provider>=1.0.0\nazure-keyvault-secrets>=4.7.0\nazure-identity>=1.15.0\nazure-monitor-opentelemetry>=1.2.0\nopentelemetry-api>=1.22.0\n# Pinned minimums for CVE remediation:\nazure-core>=1.38.0     # CVE-2026-21226\nfilelock>=3.20.3       # CVE-2025-68146, CVE-2026-22701\nurllib3>=2.7.0         # CVE-2026-21441 + CVE-2026-44431\u002F44432\ncryptography>=48.0.1,\u003C49  # GHSA-537c-gmf6-5ccf (via azure-identity\u002Fmsal)\npyjwt>=2.13.0          # PYSEC-2026-175..179 (via msal)\n```\n\n### Optional extras matrix\n\nSource of truth: `pyproject.toml`. Many extras are empty markers (`[]`): the code is\n**stdlib-only** and already importable without the extra — the extra exists for\ndiscoverability \u002F intent, and only pulls real dependencies where a third-party package\nis genuinely required.\n\n| Extra | Installs | What it unlocks |\n|---|---|---|\n| `fastapi` | `fastapi>=0.110` | `fastapi_middleware`, webhook route, API-key dep, `fastapi_rate_limit` |\n| `servicebus` | `azure-servicebus>=7.11` | `servicebus.*` consumer\u002FDLQ helpers |\n| `sb-lock` | — (uses `servicebus`) | `sb_lock` message-lock renewal |\n| `scheduler` | `apscheduler>=3.10` | `scheduler.parse_cron_trigger` |\n| `retry` | `tenacity>=8.0` | `retry.build_retry` + Azure\u002FAI presets |\n| `pdf-safety` | `pypdf>=6.13.3` | `pdf_safety.sanitize_pdf_for_passthrough` |\n| `sumologic` | `requests>=2.32.0` | `SumoLogicHandler` transport |\n| `panther` | `requests>=2.32.0` | Panther SIEM transport |\n| `bloblog` | `azure-storage-blob>=12.19` | Blob Storage log transport |\n| `sqllog` | `sqlalchemy>=2.0` | SQL table log transport |\n| `nosqllog` | `pymongo>=4.6` | Mongo\u002FCosmos log transport |\n| `nosqllog-cosmos` | `azure-cosmos>=4.5` | Cosmos-native log transport |\n| `adxlog` | `azure-kusto-ingest`, `azure-kusto-data` | ADX log transport |\n| `eventhubslog` | `azure-eventhub>=5.11` | Event Hubs log transport |\n| `logging-all` | all transport deps above | every logging transport |\n| `transports` | — (stdlib) | transport registry + console\u002Fapp-insights |\n| `alerts` | — (stdlib) | tiered alert dispatcher |\n| `health` | — (stdlib) | readiness probes |\n| `heartbeat` | — (stdlib) | heartbeat + consumer watchdog |\n| `config-refresh` | — (stdlib) | `refresh_log_flags` |\n| `ingress` | — (stdlib) | 4-gate attachment classifier |\n| `ratelimit` | — (stdlib) | `TokenBucket` + presets |\n| `notify` | — (stdlib) | two-tier notification builders |\n| `subscription` | — (stdlib) | resource renewal loop |\n| `auth` | — (uses `fastapi`) | webhook + API-key guards |\n| `identity` | — (`azure-identity` in core) | `build_credential` |\n| `audit` | — (stdlib) | `build_audit_extra` |\n| `failclose` | — (stdlib) | `require_env` \u002F `optional_env` \u002F `fail_open_env` |\n| `openai` | — (stdlib) | AI usage tracker |\n| `tokens` | — (stdlib) | HMAC action tokens |\n| `metrics` | — (stdlib) | `build_metrics_snapshot` |\n| `db` | `sqlalchemy>=2.0`, `alembic>=1.13` | `get_db`, outbox, Alembic helpers |\n| `email` | `azure-communication-email>=1.0` | `AcsEmailSender` |\n| `http` | `requests>=2.32.0` | `build_session()`, `request_with_retry()` |\n| `http-async` | `httpx>=0.27` | `build_async_client()`, `async_request_with_retry()` |\n| `documentdb` | `pymongo>=4.6` | `mongo_client_from_env()` |\n| `governance` | — (stdlib) | `budget_guard()`, `track_usage()` |\n| `aks` | — (stdlib) | `build_info()`, `install_sigterm_handler()`, leader election |\n| `all` | fastapi, servicebus, apscheduler, requests, blob, sqlalchemy, alembic, pymongo, ACS email, kusto, eventhub, httpx | aggregate of all third-party deps |\n| `dev` \u002F `test` | tooling \u002F test deps | development & CI |\n\nThe `vibey-bootstrap` console script (`vibey-bootstrap list`, `vibey-bootstrap scaffold`) ships with\nthe core install — no extra required. Templates live under `vibey_bootstrap.contrib`.\n\n## 2. Python: the v1 core (4-phase bootstrap)\n\n### The problem and the solution\n\nConfiguration loading wants logging to report progress; App Insights logging wants\nconfiguration to initialize. The library breaks the cycle in four phases:\n\n1. **Console logging** — works immediately (always).\n2. **Telemetry from env** — try App Insights from `APPLICATIONINSIGHTS_CONNECTION_STRING`.\n3. **Configuration load** — Azure App Configuration + Key Vault → `os.environ`.\n4. **Telemetry upgrade** — if the connection string only arrived via config, upgrade to App Insights now.\n\n### Quick start (the canonical pattern)\n\n```python\nimport os\nfrom vibey_bootstrap import initialize_application, get_bootstrap_logger\n\nlogger = get_bootstrap_logger(__name__)     # works before bootstrap completes\nconfig_repo = initialize_application()       # runs all four phases\n# Every App Config + Key Vault value is now in os.environ:\ndb_host = os.getenv(\"DATABASE_HOST\")\n```\n\n### Configuration precedence & the local-override rule\n\nLookup order, highest priority first:\n\n1. **Environment variables** (`os.environ`) — local overrides always win\n2. **In-process cache** (prior `get_value()` results)\n3. **Azure App Configuration** (Key Vault references auto-resolved)\n4. **Key Vault** (direct, via the secrets repository)\n5. **Default values**\n\n`load_to_environ()` **never overwrites an existing `os.environ` key** — so anything\nset by `local.settings.json` (or your shell) survives, and only *new* remote keys are\nadded. App Config can store Key Vault *references* (a JSON `{\"uri\": \"...vault...\u002Fsecrets\u002F...\"}`);\nthe provider resolves them transparently, so `os.getenv(\"DATABASE_PASSWORD\")` returns\nthe actual secret, not the URI.\n\n### API reference — entry points\n\n```python\nfrom vibey_bootstrap import (\n    initialize_application, get_bootstrap_logger,\n    ensure_bootstrap_logging, create_enhanced_config_repository,\n)\n```\n\n| Symbol | Signature | Behavior |\n|---|---|---|\n| `initialize_application` | `(secrets_repository: SecretsRepositoryInterface \\| None = None) -> EnhancedConfigRepositoryInterface` | Runs the 4-phase bootstrap; loads all config to `os.environ`; caches the repo for `refresh_setting()`. Raises `RuntimeError` on unrecoverable failure. |\n| `get_bootstrap_logger` | `(name: str) -> logging.Logger` | A logger usable immediately; auto-configures bootstrap logging on first call. |\n| `ensure_bootstrap_logging` | `() -> None` | Idempotent bootstrap-logging setup. |\n| `create_enhanced_config_repository` | `(app_config_connection_string=None, secrets_repository=None, auto_load_to_environ=False) -> EnhancedConfigRepositoryInterface` | Factory for the config repository. |\n\n### API reference — classes\n\n```python\nfrom vibey_bootstrap import (\n    ApplicationBootstrap, BootstrapLogger, ExtraFieldsFormatter,\n    TelemetryManager, telemetry_manager,\n    EnhancedConfigRepository, SecretsRepository,\n)\n```\n\n- **`ApplicationBootstrap(secrets_repository=None)`** — orchestrator. `.initialize()`\n  runs the four phases and returns the repo; `.get_config_repository()`,\n  `.is_bootstrap_completed()`.\n- **`BootstrapLogger`** — `.configure_bootstrap_logging(level=None)` (class method;\n  level falls back to `LOG_LEVEL` env, then `INFO`).\n- **`ExtraFieldsFormatter`** — `logging.Formatter` that appends `extra={}` fields to\n  each line. (v1 lives in `services.bootstrap_logging`; a v2 variant lives in\n  `vibey_bootstrap.logging` — see the `vibey-bootstrap-primitives` skill.)\n- **`TelemetryManager` \u002F `telemetry_manager`** (singleton) —\n  `.configure(connection_string=None, allow_reconfigure=False) -> bool` and\n  `.try_upgrade_from_config(config_repository) -> bool`. Best-effort: always falls\n  back to console logging rather than raising.\n- **`EnhancedConfigRepository`** — key methods:\n\n  | Method | Purpose |\n  |---|---|\n  | `get_value(key, default=None) -> str \\| None` | env → cache → App Config → Key Vault → default |\n  | `get_secret_value(key, default=None) -> str \\| None` | direct Key Vault lookup |\n  | `get_all_values() -> dict[str, str]` | merged view (env wins) |\n  | `load_to_environ() -> int` | populate `os.environ`; returns count of **new** keys |\n  | `refresh() -> None` | clear cache + reload (used by `refresh_setting`) |\n  | `get_repository_metrics() -> dict` | availability + counts |\n  | `is_app_config_available()` \u002F `is_key_vault_available()` | feature probes |\n\n- **`SecretsRepository(vault_url=None)`** — `get_secret`, `set_secret`,\n  `delete_secret`, `list_secrets`, `is_available` (reads `AZURE_KEY_VAULT_URL`).\n\n### Interfaces (DI \u002F type hints) and exceptions\n\n```python\nfrom vibey_bootstrap import (\n    ApplicationBootstrapInterface, BootstrapLoggerInterface,\n    TelemetryManagerInterface, EnhancedConfigRepositoryInterface,\n    SecretsRepositoryInterface,\n    RepositoryError, ConfigurationError, KeyVaultError,   # ConfigurationError, KeyVaultError subclass RepositoryError\n)\n```\n\n### v1 environment variables\n\n| Variable | Used by | Purpose |\n|---|---|---|\n| `APPLICATIONINSIGHTS_CONNECTION_STRING` | `TelemetryManager` | App Insights telemetry |\n| `AZURE_APP_CONFIGURATION_CONNECTION_STRING` | `EnhancedConfigRepository` | App Configuration endpoint |\n| `AZURE_APPCONFIG_ENDPOINT` | health probe \u002F AAD auth | App Config endpoint (credential-based) |\n| `AZURE_KEY_VAULT_URL` | `SecretsRepository` | Key Vault endpoint |\n| `LOG_LEVEL` | bootstrap + telemetry logging | `DEBUG`\u002F`INFO`\u002F`WARNING`\u002F`ERROR` (default `INFO`) |\n| `FUNCTIONS_WORKER_RUNTIME` | bootstrap logging | presence triggers Azure-Functions log setup |\n","> **vibey-bootstrap** is the library formerly published as `azure-bootstrap` (renamed in 4.0.0: package `vibey-bootstrap`, import `vibey_bootstrap`, CLI `vibey-bootstrap`; `azbootstrap` remains as a deprecated alias). Feature-tier labels below (v2 primitives, v3 modules) are historical and unchanged.\n\n# Azure Bootstrap — Installation & v1 Core (4-phase bootstrap)\n\n`vibey-bootstrap` solves the **logging ↔ configuration circular dependency** every\nAzure Functions \u002F container app hits at startup (you need logging to report config\nloading, but App Insights logging needs config to initialize). On top of that v1\ncore, v2 adds a large, opt-in, framework-agnostic \"cross-cutting layer\": structured\nlogging, correlation, tracing, counters, tiered alerts, an error vocabulary, ingress\nhardening, Service Bus plumbing, webhook auth, AI usage tracking, health probes, a\nv2.1 logging-transport layer (console \u002F App Insights \u002F Sumo Logic), and v4.0.0 adds\nseven more logging transports plus DB\u002Foutbox, email, hardened HTTP, AKS runtime,\ngovernance, and an `vibey-bootstrap` scaffold CLI — all opt-in behind pip extras.\n\n> **`vibey-bootstrap` is a pure Python package.** It ships inside the `vibey`\n> distribution on PyPI (vibey ADR-0037) and has\n> **no JavaScript\u002FTypeScript distribution** — you cannot `npm install` or `import` it\n> from a Next.js app. (For TS, see the `vibey-bootstrap-typescript` skill: HTTP client\n> integration with a Python backend, and porting the patterns to TypeScript.)\n\n**Compatibility:** the source and the distribution that ships it support Python **≥ 3.12**.\nDistribution: `pip install vibey-engine` (PyPI, MIT) — there is no separate\n`vibey-bootstrap` project (vibey ADR-0037). v4.0.0 is **additive** — every v1\u002Fv2 import path, symbol, signature, and\ndefault is unchanged; opt into new extras and env flags. See `MIGRATING-TO-V3.md`.\n\n## 1. Installation & extras\n\n```bash\npip install vibey-engine                     # the whole family; vibey_bootstrap importable\npip install 'vibey-engine[azure]'            # App Configuration + Key Vault + App Insights\npip install 'vibey-engine[bootstrap-all]'    # every optional dependency any extra below needs\n```\n\n**Extra names.** The matrix below lists the extras as `vibey-bootstrap`'s own\n`pyproject.toml` declares them, and they still select what each feature needs when the\npackage is installed from the tree. On the `vibey-engine` package there is no per-feature\nsuccessor spelling: the replacements are the two aggregates above (vibey ADR-0037).\n\n### Core dependencies (always installed)\n\n```text\nazure-appconfiguration-provider>=1.0.0\nazure-keyvault-secrets>=4.7.0\nazure-identity>=1.15.0\nazure-monitor-opentelemetry>=1.2.0\nopentelemetry-api>=1.22.0\n# Pinned minimums for CVE remediation:\nazure-core>=1.38.0     # CVE-2026-21226\nfilelock>=3.20.3       # CVE-2025-68146, CVE-2026-22701\nurllib3>=2.7.0         # CVE-2026-21441 + CVE-2026-44431\u002F44432\ncryptography>=48.0.1,\u003C49  # GHSA-537c-gmf6-5ccf (via azure-identity\u002Fmsal)\npyjwt>=2.13.0          # PYSEC-2026-175..179 (via msal)\n```\n\n### Optional extras matrix\n\nSource of truth: `pyproject.toml`. Many extras are empty markers (`[]`): the code is\n**stdlib-only** and already importable without the extra — the extra exists for\ndiscoverability \u002F intent, and only pulls real dependencies where a third-party package\nis genuinely required.\n\n| Extra | Installs | What it unlocks |\n|---|---|---|\n| `fastapi` | `fastapi>=0.110` | `fastapi_middleware`, webhook route, API-key dep, `fastapi_rate_limit` |\n| `servicebus` | `azure-servicebus>=7.11` | `servicebus.*` consumer\u002FDLQ helpers |\n| `sb-lock` | — (uses `servicebus`) | `sb_lock` message-lock renewal |\n| `scheduler` | `apscheduler>=3.10` | `scheduler.parse_cron_trigger` |\n| `retry` | `tenacity>=8.0` | `retry.build_retry` + Azure\u002FAI presets |\n| `pdf-safety` | `pypdf>=6.13.3` | `pdf_safety.sanitize_pdf_for_passthrough` |\n| `sumologic` | `requests>=2.32.0` | `SumoLogicHandler` transport |\n| `panther` | `requests>=2.32.0` | Panther SIEM transport |\n| `bloblog` | `azure-storage-blob>=12.19` | Blob Storage log transport |\n| `sqllog` | `sqlalchemy>=2.0` | SQL table log transport |\n| `nosqllog` | `pymongo>=4.6` | Mongo\u002FCosmos log transport |\n| `nosqllog-cosmos` | `azure-cosmos>=4.5` | Cosmos-native log transport |\n| `adxlog` | `azure-kusto-ingest`, `azure-kusto-data` | ADX log transport |\n| `eventhubslog` | `azure-eventhub>=5.11` | Event Hubs log transport |\n| `logging-all` | all transport deps above | every logging transport |\n| `transports` | — (stdlib) | transport registry + console\u002Fapp-insights |\n| `alerts` | — (stdlib) | tiered alert dispatcher |\n| `health` | — (stdlib) | readiness probes |\n| `heartbeat` | — (stdlib) | heartbeat + consumer watchdog |\n| `config-refresh` | — (stdlib) | `refresh_log_flags` |\n| `ingress` | — (stdlib) | 4-gate attachment classifier |\n| `ratelimit` | — (stdlib) | `TokenBucket` + presets |\n| `notify` | — (stdlib) | two-tier notification builders |\n| `subscription` | — (stdlib) | resource renewal loop |\n| `auth` | — (uses `fastapi`) | webhook + API-key guards |\n| `identity` | — (`azure-identity` in core) | `build_credential` |\n| `audit` | — (stdlib) | `build_audit_extra` |\n| `failclose` | — (stdlib) | `require_env` \u002F `optional_env` \u002F `fail_open_env` |\n| `openai` | — (stdlib) | AI usage tracker |\n| `tokens` | — (stdlib) | HMAC action tokens |\n| `metrics` | — (stdlib) | `build_metrics_snapshot` |\n| `db` | `sqlalchemy>=2.0`, `alembic>=1.13` | `get_db`, outbox, Alembic helpers |\n| `email` | `azure-communication-email>=1.0` | `AcsEmailSender` |\n| `http` | `requests>=2.32.0` | `build_session()`, `request_with_retry()` |\n| `http-async` | `httpx>=0.27` | `build_async_client()`, `async_request_with_retry()` |\n| `documentdb` | `pymongo>=4.6` | `mongo_client_from_env()` |\n| `governance` | — (stdlib) | `budget_guard()`, `track_usage()` |\n| `aks` | — (stdlib) | `build_info()`, `install_sigterm_handler()`, leader election |\n| `all` | fastapi, servicebus, apscheduler, requests, blob, sqlalchemy, alembic, pymongo, ACS email, kusto, eventhub, httpx | aggregate of all third-party deps |\n| `dev` \u002F `test` | tooling \u002F test deps | development & CI |\n\nThe `vibey-bootstrap` console script (`vibey-bootstrap list`, `vibey-bootstrap scaffold`) ships with\nthe core install — no extra required. Templates live under `vibey_bootstrap.contrib`.\n\n## 2. Python: the v1 core (4-phase bootstrap)\n\n### The problem and the solution\n\nConfiguration loading wants logging to report progress; App Insights logging wants\nconfiguration to initialize. The library breaks the cycle in four phases:\n\n1. **Console logging** — works immediately (always).\n2. **Telemetry from env** — try App Insights from `APPLICATIONINSIGHTS_CONNECTION_STRING`.\n3. **Configuration load** — Azure App Configuration + Key Vault → `os.environ`.\n4. **Telemetry upgrade** — if the connection string only arrived via config, upgrade to App Insights now.\n\n### Quick start (the canonical pattern)\n\n```python\nimport os\nfrom vibey_bootstrap import initialize_application, get_bootstrap_logger\n\nlogger = get_bootstrap_logger(__name__)     # works before bootstrap completes\nconfig_repo = initialize_application()       # runs all four phases\n# Every App Config + Key Vault value is now in os.environ:\ndb_host = os.getenv(\"DATABASE_HOST\")\n```\n\n### Configuration precedence & the local-override rule\n\nLookup order, highest priority first:\n\n1. **Environment variables** (`os.environ`) — local overrides always win\n2. **In-process cache** (prior `get_value()` results)\n3. **Azure App Configuration** (Key Vault references auto-resolved)\n4. **Key Vault** (direct, via the secrets repository)\n5. **Default values**\n\n`load_to_environ()` **never overwrites an existing `os.environ` key** — so anything\nset by `local.settings.json` (or your shell) survives, and only *new* remote keys are\nadded. App Config can store Key Vault *references* (a JSON `{\"uri\": \"...vault...\u002Fsecrets\u002F...\"}`);\nthe provider resolves them transparently, so `os.getenv(\"DATABASE_PASSWORD\")` returns\nthe actual secret, not the URI.\n\n### API reference — entry points\n\n```python\nfrom vibey_bootstrap import (\n    initialize_application, get_bootstrap_logger,\n    ensure_bootstrap_logging, create_enhanced_config_repository,\n)\n```\n\n| Symbol | Signature | Behavior |\n|---|---|---|\n| `initialize_application` | `(secrets_repository: SecretsRepositoryInterface \\| None = None) -> EnhancedConfigRepositoryInterface` | Runs the 4-phase bootstrap; loads all config to `os.environ`; caches the repo for `refresh_setting()`. Raises `RuntimeError` on unrecoverable failure. |\n| `get_bootstrap_logger` | `(name: str) -> logging.Logger` | A logger usable immediately; auto-configures bootstrap logging on first call. |\n| `ensure_bootstrap_logging` | `() -> None` | Idempotent bootstrap-logging setup. |\n| `create_enhanced_config_repository` | `(app_config_connection_string=None, secrets_repository=None, auto_load_to_environ=False) -> EnhancedConfigRepositoryInterface` | Factory for the config repository. |\n\n### API reference — classes\n\n```python\nfrom vibey_bootstrap import (\n    ApplicationBootstrap, BootstrapLogger, ExtraFieldsFormatter,\n    TelemetryManager, telemetry_manager,\n    EnhancedConfigRepository, SecretsRepository,\n)\n```\n\n- **`ApplicationBootstrap(secrets_repository=None)`** — orchestrator. `.initialize()`\n  runs the four phases and returns the repo; `.get_config_repository()`,\n  `.is_bootstrap_completed()`.\n- **`BootstrapLogger`** — `.configure_bootstrap_logging(level=None)` (class method;\n  level falls back to `LOG_LEVEL` env, then `INFO`).\n- **`ExtraFieldsFormatter`** — `logging.Formatter` that appends `extra={}` fields to\n  each line. (v1 lives in `services.bootstrap_logging`; a v2 variant lives in\n  `vibey_bootstrap.logging` — see the `vibey-bootstrap-primitives` skill.)\n- **`TelemetryManager` \u002F `telemetry_manager`** (singleton) —\n  `.configure(connection_string=None, allow_reconfigure=False) -> bool` and\n  `.try_upgrade_from_config(config_repository) -> bool`. Best-effort: always falls\n  back to console logging rather than raising.\n- **`EnhancedConfigRepository`** — key methods:\n\n  | Method | Purpose |\n  |---|---|\n  | `get_value(key, default=None) -> str \\| None` | env → cache → App Config → Key Vault → default |\n  | `get_secret_value(key, default=None) -> str \\| None` | direct Key Vault lookup |\n  | `get_all_values() -> dict[str, str]` | merged view (env wins) |\n  | `load_to_environ() -> int` | populate `os.environ`; returns count of **new** keys |\n  | `refresh() -> None` | clear cache + reload (used by `refresh_setting`) |\n  | `get_repository_metrics() -> dict` | availability + counts |\n  | `is_app_config_available()` \u002F `is_key_vault_available()` | feature probes |\n\n- **`SecretsRepository(vault_url=None)`** — `get_secret`, `set_secret`,\n  `delete_secret`, `list_secrets`, `is_available` (reads `AZURE_KEY_VAULT_URL`).\n\n### Interfaces (DI \u002F type hints) and exceptions\n\n```python\nfrom vibey_bootstrap import (\n    ApplicationBootstrapInterface, BootstrapLoggerInterface,\n    TelemetryManagerInterface, EnhancedConfigRepositoryInterface,\n    SecretsRepositoryInterface,\n    RepositoryError, ConfigurationError, KeyVaultError,   # ConfigurationError, KeyVaultError subclass RepositoryError\n)\n```\n\n### v1 environment variables\n\n| Variable | Used by | Purpose |\n|---|---|---|\n| `APPLICATIONINSIGHTS_CONNECTION_STRING` | `TelemetryManager` | App Insights telemetry |\n| `AZURE_APP_CONFIGURATION_CONNECTION_STRING` | `EnhancedConfigRepository` | App Configuration endpoint |\n| `AZURE_APPCONFIG_ENDPOINT` | health probe \u002F AAD auth | App Config endpoint (credential-based) |\n| `AZURE_KEY_VAULT_URL` | `SecretsRepository` | Key Vault endpoint |\n| `LOG_LEVEL` | bootstrap + telemetry logging | `DEBUG`\u002F`INFO`\u002F`WARNING`\u002F`ERROR` (default `INFO`) |\n| `FUNCTIONS_WORKER_RUNTIME` | bootstrap logging | presence triggers Azure-Functions log setup |\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fvibey-bootstrap\u002Fskills\u002Fvibey-bootstrap-core",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill vibey-bootstrap-core",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill vibey-bootstrap-core",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill vibey-bootstrap-core","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fvibey-bootstrap\u002Fskills\u002Fvibey-bootstrap-core\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]