vault-release

Nodig

• product_configs — Product folders scanned to assemble a release.
• bob_user_manual — Assembled print source packaged into the release; generated by branded-pdf.
• partner_product — Partner product note read when building the partner release.
• playbooks — Playbook content copied into the release.
• upgrade_playbooks — Upgrade playbooks, held back by pricing-tier.
• wiki_manual — User-manual chapters — the only place manual content is edited; copied verbatim.
• release_config — RELEASE-CONFIG.md defining what the package includes
• release_config — Release config to build from
• output_path — Destination; defaults to the config's own output block
• release_config — Config that produced a wrong or empty package
• release_config — Product config carrying an mcp block: output_name, skill_tiers, namespace.
• playbooks — Active playbooks of the shipped tiers, shipped with the files they embed.
• value_chain_definitions — Canonical chain definitions VALUE-CHAINS.md is regenerated from; not shipped.
• release_directory — Built release directory containing MANIFEST.md and the package files.
• release_repository — Local release-history repository used by publish_release.py; its path and GitHub name come from the workspace's release-ops settings.
• release_ops — Owner release settings (repository, Drive account, product aliases, partner/retired lists); publish and build_packages read it, and refuse with the reason when a value they need is missing.