@quantile-co/factory-pi 0.1.0 → 0.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quantile-co/factory-pi",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "license": "MIT",
   "description": "Factory Pi extension and shared skill selections.",
   "type": "module",

package/skills/day-zero-deploy/references/local-state.md

@@ -151,7 +151,7 @@ cp "$TF_DIR/terraform.tfstate" "$TF_DIR/terraform.tfstate.pre-gcs"
 rm "$TF_DIR/backend_override.tf"
 tofu -chdir="$TF_DIR" init -migrate-state -lockfile=readonly \
   -backend-config="bucket=$GCP_TF_STATE_BUCKET" \
-  -backend-config="prefix=repository/prod"
+  -backend-config="prefix=${GH_REPO#*/}/prod/infrastructure"
 tofu -chdir="$TF_DIR" state list
 tofu -chdir="$TF_DIR" plan # expect no changes; keep the ignored backup securely until verified
 unset GITHUB_TOKEN # gh run watch cannot use the Terraform fine-grained PAT

package/skills/deploy/references/configuration.md

@@ -30,8 +30,12 @@ is passed as `--tf-layer` to the repository's pnpm task/app. That repository map
 the layer internally to its directory and existing backend prefix. Shared YAML
 contains neither directory nor backend-prefix arguments. Set
 `github.workflows.layers` to the supported subset. Factory selects Infrastructure
-only, mapped by its app to `tf/infrastructure` and `repository/prod`. Retain each
-consumer's existing state identity. Plan and Apply must select the same layer.
+only, mapped by its app to `tf/infrastructure`, with the source target
+`factory/prod/infrastructure`. Backend prefixes follow
+`<repository-name>/<environment>/<tf-layer>`, preserving dots in repository names.
+Changing an existing prefix requires a separately approved same-lineage state
+migration before activating its new source mapping; never initialize an empty
+backend as a replacement. Plan and Apply must select the same layer.
 
 A synthetic owner-roster example, not identities to deploy:
 

package/skills/deploy/references/plan-apply.md

@@ -101,9 +101,12 @@ Check may have run on the source branch before fast-forwarding main. Confirm its
 exact SHA, not just the branch label. Inspect current production activity; never
 cancel another operator's job. Verify main/prod restrictions, WIF and IAM,
 the effective state bucket and backend prefix, including caller inputs and runtime
-environment overrides. Factory defaults to `repository/prod`; consumers may retain
-another existing prefix. Check the called workflow's `factory-production`
-concurrency and any caller guard.
+environment overrides. New prefixes use
+`<repository-name>/<environment>/<tf-layer>`; Factory's source target is
+`factory/prod/infrastructure`. Verify that the existing lineage has been migrated
+before activating a changed prefix. A source edit, empty-backend initialization
+or `init -reconfigure` is not a state migration. Check the called workflow's
+`factory-production` concurrency and any caller guard.
 The Terraform root's reviewed paired records are the source of truth for platform
 permissions, including plan-reader emails and immutable deployment actor IDs.
 Neither YAML nor the CLI reads an Actions owner roster. The YAML owner and