feat(infra): pull artifacts pinned by package release

docs/prds/prd-new-packaged-infra-artifacts.md

@@ -110,10 +110,11 @@ non-empty Firecracker versions, 64-character lowercase SHA-256 values, and a
 full source commit. It returns immutable value objects rather than passing raw
 dictionaries through backend code.
 
-The repository carries no pretend production pins. A source checkout without a
-generated manifest is a development tree and must explicitly select local
-infrastructure builds. A built distribution without valid generated metadata
-is invalid and fails during infrastructure preparation.
+The repository carries no pretend production pins. A source checkout or ad-hoc
+Git wheel carries a `development: true` marker and selects local infrastructure
+builds, preserving the contributor and current `install.sh` paths. The release
+packaging workflow must replace that marker with the validated schema above;
+it refuses mutable or incomplete release inputs.
 
 ### Packaging order
 
@@ -145,10 +146,11 @@ before starting either plane.
 The gateway receives the same contract so startup does not continue to rebuild
 the adjacent half of the fixed infrastructure pair.
 
-An explicit `BOT_BOTTLE_INFRA_BUILD=local` development mode selects the existing
-builders. Local mode is allowed from a checkout and deliberately bypasses
-release metadata. Packaged production startup never silently falls back from a
-failed pull to a local build.
+A source checkout is itself a development boundary and selects the existing
+builders. `BOT_BOTTLE_INFRA_BUILD=local` provides the same explicit override
+for release debugging. Both paths deliberately bypass release metadata.
+Packaged production startup never silently falls back from a failed pull to a
+local build.
 
 ### Docker