Prompt file imported from refahigroup/refahiplus-api (.codex/prompts/10-Phase-25b-shopproductvariant-backfill-execution-qa.md). Copyright stays with the author.

Codex Operational QA Prompt — Phase 25B: Controlled ShopProductVariant Backfill Execution and Fixture QA

Name: 10-Phase-25b-shopproductvariant-backfill-execution-qa
Author: refahigroup

Read .codex/prompts/_session-bootstrap.md first. Then read AGENTS.md. Load only the relevant backend/module/store/order architecture skills from .codex/skills/.

This is an operational QA and controlled data-readiness task.

Run this prompt from:

C:\Workspace\repo\refahiplus-api

Do not modify source code unless a tiny report-only/doc-only change is required. Do not modify Admin Web. Do not modify Customer WebApp. Do not modify database migrations. Do not modify Docker/GitHub Actions. Do not remove runtime fallback behavior. Do not run write-mode backfill on production. Do not make release decisions.

Mandatory Report Output

At the end of this task, save the final report as:

.codex/reports/phase-25b-shopproductvariant-backfill-execution-qa.md

If .codex/reports/ does not exist, create it.

Also print the same report in the Codex final response.

Context

Phase 25A added backend-only controlled audit and backfill tooling for ShopProductVariant.

Available admin endpoints:

GET  /admin/shop-product-variants/backfill/audit
POST /admin/shop-product-variants/backfill

Phase 25A behavior:

- DryRun defaults to true.
- Backfill writes only missing non-deleted ShopProductVariant offerings.
- Existing configured offerings are never overwritten.
- Inactive non-deleted offerings are treated as existing and are not overwritten.
- Soft-deleted offerings do not block creating a new non-deleted offering.
- Backfill uses ProductVariant.PriceMinor and ProductVariant.DiscountedPriceMinor.
- Runtime fallback to ProductVariant pricing remains active.
- No actual database backfill was executed in Phase 25A.

Current goal:

Use the Phase 25A tooling in a controlled environment to verify audit, dry-run, write-mode backfill, idempotency, and end-to-end pricing behavior for products with variants.

Critical Safety Rules

Production Safety

Do not run write-mode backfill against production.

Write-mode is allowed only if all of these are true:

1. The environment is explicitly local, development, or stage.
2. The API base URL clearly indicates local/dev/stage.
3. A valid admin token is available.
4. A narrow ShopId or ProductId scope is used for the first write run.
5. The prompt/session explicitly has PHASE25B_ALLOW_WRITE=true or equivalent explicit local/stage approval.

If any condition is missing:

- Run audit and dry-run only.
- Do not run write-mode.
- Report what was skipped and why.

Data Safety

Do not:

- overwrite existing ShopProductVariant rows;
- change ProductVariant prices;
- change ShopProduct prices;
- change stock/capacity;
- change orders/cart data;
- remove fallback;
- delete data;
- apply migrations to a real database.

Required Pre-Check

Run:

git status --short

Report dirty state clearly.

Do not modify source files unless necessary for the report.

Required Environment Discovery

Check whether local/stage API execution is possible.

Look for existing environment/run instructions:

README
docs
.env examples
docker-compose files
launchSettings.json
appsettings.Development.json
AGENTS.md
.codex reports

Find or infer:

API_BASE_URL
admin auth/token mechanism
Store module route prefix
whether local API is running
whether database is reachable

Do not expose secrets in the report.

If an admin token is present only as an environment variable, reference it as:

ADMIN_TOKEN: present/not present

Do not print the token.

Required Operational Flow

1. Build/Test Baseline

Run backend validation first:

dotnet restore .\Refahi.Backend.slnx
dotnet build .\Refahi.Backend.slnx --configuration Release --no-restore
dotnet test .\Refahi.Backend.slnx --configuration Release --no-build

Do not proceed to API write-mode if build/test fails.

2. Audit All or Scoped Data

If API and admin auth are available, call audit endpoint.

Preferred first call:

GET /admin/shop-product-variants/backfill/audit

If dataset may be large, use filters:

GET /admin/shop-product-variants/backfill/audit?shopId={shopId}
GET /admin/shop-product-variants/backfill/audit?productId={productId}
GET /admin/shop-product-variants/backfill/audit?shopId={shopId}&productId={productId}

Capture:

ShopProductsChecked
ProductsWithVariants
ExistingOfferings
MissingOfferings
first-N detail rows
warnings/errors

If API/auth is not available, report audit as not run and explain exactly what is missing.

3. Dry-Run Backfill

Run dry-run before any write.

Example payload:

{
  "shopId": null,
  "productId": null,
  "dryRun": true,
  "detailLimit": 50
}

Prefer scoped dry-run first if sample ShopId/ProductId is available.

Capture:

CreatedOfferings preview count
SkippedExistingOfferings
SkippedInvalidVariants
Warnings
CreatedItems preview

Do not run write-mode if dry-run returns invalid price warnings that look unsafe.

4. Controlled Write-Mode Backfill

Only if safety conditions are met.

Start with a narrow scope:

{
  "shopId": "{sampleShopId}",
  "productId": "{sampleProductId}",
  "dryRun": false,
  "detailLimit": 50
}

After write-mode, immediately run:

- audit for the same scope;
- write-mode again for the same scope to confirm idempotency.

Expected result:

- First write creates missing rows.
- Second write creates zero rows.
- Existing configured rows are not overwritten.
- Audit missing count decreases.

If write-mode is not allowed/possible, document the exact API calls that should be run manually later.

5. Two-Shop Fixture QA

If data exists or can be safely identified:

Find or use a product that exists in two shops and has variants.

Verify:

- Shop A has ShopProductVariant row for Variant X.
- Shop B has ShopProductVariant row for Variant X.
- Prices can differ between Shop A and Shop B.
- Product detail with shopSlug A returns price A.
- Product detail with shopSlug B returns price B.

Use API calls if browser QA is not available:

GET /api/store/{moduleSlug}/products/{productSlug}?shopSlug={shopSlugA}
GET /api/store/{moduleSlug}/products/{productSlug}?shopSlug={shopSlugB}

Check returned variant fields:

ShopProductVariantId
ShopPriceMinor
ShopDiscountedPriceMinor
PriceSource
IsActiveInShop
UsesShopSpecificPrice
PriceMinor / DiscountedPriceMinor as currently returned

6. Cart/Checkout API QA

If local/stage API, auth, and test data are available:

Test at least one variant item with active ShopProductVariant.

Verify:

- AddToCart uses ShopProductVariant price.
- GetCart returns ShopProductVariantId and PriceSource.
- PlaceStoreOrder succeeds when cart price is current.
- If price changes after item is in cart, checkout rejects stale price or cart shows HasPriceChanged according to Phase 21 behavior.

Do not use real payment rails unless local/stage mocks are explicitly configured.

Do not run wallet/payment flows against production.

7. WebApp Browser QA

If local/stage WebApp and API are available:

Verify:

Same product under Shop A and Shop B:
- shop-specific route passes ShopSlug;
- variant selector shows Shop A price on Shop A route;
- variant selector shows Shop B price on Shop B route;
- inactive shop variant is disabled;
- missing shop variant fallback still works if expected;
- cart row displays correct price;
- price-change warning blocks checkout when backend says HasPriceChanged.

If browser QA is unavailable, report not run.

Optional: Manual Command Templates

If executing API calls is not possible, provide exact curl/httpie templates using placeholders.

Do not invent real IDs.

Template examples:

curl -H "Authorization: Bearer $ADMIN_TOKEN" \
  "$API_BASE_URL/admin/shop-product-variants/backfill/audit?shopId={SHOP_ID}&productId={PRODUCT_ID}"

curl -X POST \
  -H "Authorization: Bearer $ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"shopId":"{SHOP_ID}","productId":"{PRODUCT_ID}","dryRun":true,"detailLimit":50}' \
  "$API_BASE_URL/admin/shop-product-variants/backfill"

curl -X POST \
  -H "Authorization: Bearer $ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"shopId":"{SHOP_ID}","productId":"{PRODUCT_ID}","dryRun":false,"detailLimit":50}' \
  "$API_BASE_URL/admin/shop-product-variants/backfill"

Strict Out of Scope

Do not:

- modify Backend source behavior;
- modify Admin Web;
- modify Customer WebApp;
- remove ProductVariant fallback;
- enforce missing ShopProductVariant rejection;
- apply DB migrations;
- run write-mode on production;
- run unscoped write-mode as the first write;
- change cart/checkout code;
- change product detail code;
- change Orders/Wallet;
- change Docker/GitHub Actions;
- change package versions or target frameworks;
- mark production-ready.

Final Report Format

Save the report to:

.codex/reports/phase-25b-shopproductvariant-backfill-execution-qa.md

Use exactly this structure:

Summary:
- ...

Skills used:
- ...

Repository checked:
- ...

Git state:
- Pre-check:
- Final:

Environment/runtime availability:
- API base URL:
- Admin token:
- Environment classification:
- Write-mode allowed:
- Reason:

Build/test validation:
- Command: ...
  Result: ...

Audit execution:
- Endpoint:
- Scope:
- Result:
- Missing offerings:
- Warnings:

Dry-run execution:
- Endpoint:
- Scope:
- Result:
- Would create:
- Skipped existing:
- Skipped invalid:
- Warnings:

Write-mode execution:
- Executed: yes/no
- Scope:
- Result:
- Created:
- Idempotency re-run:
- Reason if not executed:

Two-shop product-detail QA:
- Executed: yes/no
- Result:
- Evidence:

Cart/checkout QA:
- Executed: yes/no
- Result:
- Evidence:

WebApp/browser QA:
- Executed: yes/no
- Result:
- Evidence:

Data safety findings:
- ...

Fallback behavior:
- ...

Deferred items:
- ...

Risks / assumptions:
- ...

Suggested next phase:
- ...

# Codex Operational QA Prompt — Phase 25B: Controlled ShopProductVariant Backfill Execution and Fixture QA Read `.codex/prompts/_session-bootstrap.md` first. Then read `AGENTS.md`. Load only the relevant backend/module/store/order architecture skills from `.codex/skills/`. This is an **operational QA and controlled data-readiness task**. Run this prompt from: ```text id="n4u9xw" C:\Workspace\repo\refahiplus-api ``` Do not modify source code unless a tiny report-only/doc-only change is required. Do not modify Admin Web. Do not modify Customer WebApp. Do not modify database migrations. Do not modify Docker/GitHub Actions. Do not remove runtime fallback behavior. Do not run write-mode backfill on production. Do not make release decisions. ## Mandatory Report Output At the end of this task, save the final report as: ```text id="w5zzql" .codex/reports/phase-25b-shopproductvariant-backfill-execution-qa.md ``` If `.codex/reports/` does not exist, create it. Also print the same report in the Codex final response. ## Context Phase 25A added backend-only controlled audit and backfill tooling for `ShopProductVariant`. Available admin endpoints: ```text id="s5gktw" GET /admin/shop-product-variants/backfill/audit POST /admin/shop-product-variants/backfill ``` Phase 25A behavior: ```text id="fw9p8l" - DryRun defaults to true. - Backfill writes only missing non-deleted ShopProductVariant offerings. - Existing configured offerings are never overwritten. - Inactive non-deleted offerings are treated as existing and are not overwritten. - Soft-deleted offerings do not block creating a new non-deleted offering. - Backfill uses ProductVariant.PriceMinor and ProductVariant.DiscountedPriceMinor. - Runtime fallback to ProductVariant pricing remains active. - No actual database backfill was executed in Phase 25A. ``` Current goal: ```text id="e7711l" Use the Phase 25A tooling in a controlled environment to verify audit, dry-run, write-mode backfill, idempotency, and end-to-end pricing behavior for products with variants. ``` ## Critical Safety Rules ### Production Safety Do not run write-mode backfill against production. Write-mode is allowed only if all of these are true: ```text id="8xds4r" 1. The environment is explicitly local, development, or stage. 2. The API base URL clearly indicates local/dev/stage. 3. A valid admin token is available. 4. A narrow ShopId or ProductId scope is used for the first write run. 5. The prompt/session explicitly has PHASE25B_ALLOW_WRITE=true or equivalent explicit local/stage approval. ``` If any condition is missing: ```text id="m3gnv4" - Run audit and dry-run only. - Do not run write-mode. - Report what was skipped and why. ``` ### Data Safety Do not: ```text id="sfh6zx" - overwrite existing ShopProductVariant rows; - change ProductVariant prices; - change ShopProduct prices; - change stock/capacity; - change orders/cart data; - remove fallback; - delete data; - apply migrations to a real database. ``` ## Required Pre-Check Run: ```bash id="cr5tnf" git status --short ``` Report dirty state clearly. Do not modify source files unless necessary for the report. ## Required Environment Discovery Check whether local/stage API execution is possible. Look for existing environment/run instructions: ```text id="ke4j5h" README docs .env examples docker-compose files launchSettings.json appsettings.Development.json AGENTS.md .codex reports ``` Find or infer: ```text id="fvt51n" API_BASE_URL admin auth/token mechanism Store module route prefix whether local API is running whether database is reachable ``` Do not expose secrets in the report. If an admin token is present only as an environment variable, reference it as: ```text id="dhs03d" ADMIN_TOKEN: present/not present ``` Do not print the token. ## Required Operational Flow ### 1. Build/Test Baseline Run backend validation first: ```bash id="uopvpi" dotnet restore .\Refahi.Backend.slnx dotnet build .\Refahi.Backend.slnx --configuration Release --no-restore dotnet test .\Refahi.Backend.slnx --configuration Release --no-build ``` Do not proceed to API write-mode if build/test fails. ### 2. Audit All or Scoped Data If API and admin auth are available, call audit endpoint. Preferred first call: ```http id="juhsth" GET /admin/shop-product-variants/backfill/audit ``` If dataset may be large, use filters: ```http id="0enbfx" GET /admin/shop-product-variants/backfill/audit?shopId={shopId} GET /admin/shop-product-variants/backfill/audit?productId={productId} GET /admin/shop-product-variants/backfill/audit?shopId={shopId}&productId={productId} ``` Capture: ```text id="mhhygg" ShopProductsChecked ProductsWithVariants ExistingOfferings MissingOfferings first-N detail rows warnings/errors ``` If API/auth is not available, report audit as not run and explain exactly what is missing. ### 3. Dry-Run Backfill Run dry-run before any write. Example payload: ```json id="k59jgj" { "shopId": null, "productId": null, "dryRun": true, "detailLimit": 50 } ``` Prefer scoped dry-run first if sample ShopId/ProductId is available. Capture: ```text id="695w3d" CreatedOfferings preview count SkippedExistingOfferings SkippedInvalidVariants Warnings CreatedItems preview ``` Do not run write-mode if dry-run returns invalid price warnings that look unsafe. ### 4. Controlled Write-Mode Backfill Only if safety conditions are met. Start with a narrow scope: ```json id="nphh4y" { "shopId": "{sampleShopId}", "productId": "{sampleProductId}", "dryRun": false, "detailLimit": 50 } ``` After write-mode, immediately run: ```text id="cml1m6" - audit for the same scope; - write-mode again for the same scope to confirm idempotency. ``` Expected result: ```text id="9pp6xc" - First write creates missing rows. - Second write creates zero rows. - Existing configured rows are not overwritten. - Audit missing count decreases. ``` If write-mode is not allowed/possible, document the exact API calls that should be run manually later. ### 5. Two-Shop Fixture QA If data exists or can be safely identified: Find or use a product that exists in two shops and has variants. Verify: ```text id="7kegq9" - Shop A has ShopProductVariant row for Variant X. - Shop B has ShopProductVariant row for Variant X. - Prices can differ between Shop A and Shop B. - Product detail with shopSlug A returns price A. - Product detail with shopSlug B returns price B. ``` Use API calls if browser QA is not available: ```http id="6o1502" GET /api/store/{moduleSlug}/products/{productSlug}?shopSlug={shopSlugA} GET /api/store/{moduleSlug}/products/{productSlug}?shopSlug={shopSlugB} ``` Check returned variant fields: ```text id="6iwld3" ShopProductVariantId ShopPriceMinor ShopDiscountedPriceMinor PriceSource IsActiveInShop UsesShopSpecificPrice PriceMinor / DiscountedPriceMinor as currently returned ``` ### 6. Cart/Checkout API QA If local/stage API, auth, and test data are available: Test at least one variant item with active `ShopProductVariant`. Verify: ```text id="z2t6zt" - AddToCart uses ShopProductVariant price. - GetCart returns ShopProductVariantId and PriceSource. - PlaceStoreOrder succeeds when cart price is current. - If price changes after item is in cart, checkout rejects stale price or cart shows HasPriceChanged according to Phase 21 behavior. ``` Do not use real payment rails unless local/stage mocks are explicitly configured. Do not run wallet/payment flows against production. ### 7. WebApp Browser QA If local/stage WebApp and API are available: Verify: ```text id="ze98lz" Same product under Shop A and Shop B: - shop-specific route passes ShopSlug; - variant selector shows Shop A price on Shop A route; - variant selector shows Shop B price on Shop B route; - inactive shop variant is disabled; - missing shop variant fallback still works if expected; - cart row displays correct price; - price-change warning blocks checkout when backend says HasPriceChanged. ``` If browser QA is unavailable, report not run. ## Optional: Manual Command Templates If executing API calls is not possible, provide exact curl/httpie templates using placeholders. Do not invent real IDs. Template examples: ```bash id="lc4i39" curl -H "Authorization: Bearer $ADMIN_TOKEN" \ "$API_BASE_URL/admin/shop-product-variants/backfill/audit?shopId={SHOP_ID}&productId={PRODUCT_ID}" ``` ```bash id="j8m6gw" curl -X POST \ -H "Authorization: Bearer $ADMIN_TOKEN" \ -H "Content-Type: application/json" \ -d '{"shopId":"{SHOP_ID}","productId":"{PRODUCT_ID}","dryRun":true,"detailLimit":50}' \ "$API_BASE_URL/admin/shop-product-variants/backfill" ``` ```bash id="i39dgl" curl -X POST \ -H "Authorization: Bearer $ADMIN_TOKEN" \ -H "Content-Type: application/json" \ -d '{"shopId":"{SHOP_ID}","productId":"{PRODUCT_ID}","dryRun":false,"detailLimit":50}' \ "$API_BASE_URL/admin/shop-product-variants/backfill" ``` ## Strict Out of Scope Do not: ```text id="t17dvu" - modify Backend source behavior; - modify Admin Web; - modify Customer WebApp; - remove ProductVariant fallback; - enforce missing ShopProductVariant rejection; - apply DB migrations; - run write-mode on production; - run unscoped write-mode as the first write; - change cart/checkout code; - change product detail code; - change Orders/Wallet; - change Docker/GitHub Actions; - change package versions or target frameworks; - mark production-ready. ``` ## Final Report Format Save the report to: ```text id="f40rd1" .codex/reports/phase-25b-shopproductvariant-backfill-execution-qa.md ``` Use exactly this structure: ```text id="jv3u6s" Summary: - ... Skills used: - ... Repository checked: - ... Git state: - Pre-check: - Final: Environment/runtime availability: - API base URL: - Admin token: - Environment classification: - Write-mode allowed: - Reason: Build/test validation: - Command: ... Result: ... Audit execution: - Endpoint: - Scope: - Result: - Missing offerings: - Warnings: Dry-run execution: - Endpoint: - Scope: - Result: - Would create: - Skipped existing: - Skipped invalid: - Warnings: Write-mode execution: - Executed: yes/no - Scope: - Result: - Created: - Idempotency re-run: - Reason if not executed: Two-shop product-detail QA: - Executed: yes/no - Result: - Evidence: Cart/checkout QA: - Executed: yes/no - Result: - Evidence: WebApp/browser QA: - Executed: yes/no - Result: - Evidence: Data safety findings: - ... Fallback behavior: - ... Deferred items: - ... Risks / assumptions: - ... Suggested next phase: - ... ```

{ "prompt": "# Codex Operational QA Prompt — Phase 25B: Controlled ShopProductVariant Backfill Execution and Fixture QA\n\nRead `.codex/prompts/_session-bootstrap.md` first.\nThen read `AGENTS.md`.\nLoad only the relevant backend/module/store/order architecture skills from `.codex/skills/`.\n\nThis is an **operational QA and controlled data-readiness task**.\n\nRun this prompt from:\n\n```text id=\"n4u9xw\"\nC:\\Workspace\\repo\\refahiplus-api\n```\n\nDo not modify source code unless a tiny report-only/doc-only change is required.\nDo not modify Admin Web.\nDo not modify Customer WebApp.\nDo not modify database migrations.\nDo not modify Docker/GitHub Actions.\nDo not remove runtime fallback behavior.\nDo not run write-mode backfill on production.\nDo not make release decisions.\n\n## Mandatory Report Output\n\nAt the end of this task, save the final report as:\n\n```text id=\"w5zzql\"\n.codex/reports/phase-25b-shopproductvariant-backfill-execution-qa.md\n```\n\nIf `.codex/reports/` does not exist, create it.\n\nAlso print the same report in the Codex final response.\n\n## Context\n\nPhase 25A added backend-only controlled audit and backfill tooling for `ShopProductVariant`.\n\nAvailable admin endpoints:\n\n```text id=\"s5gktw\"\nGET /admin/shop-product-variants/backfill/audit\nPOST /admin/shop-product-variants/backfill\n```\n\nPhase 25A behavior:\n\n```text id=\"fw9p8l\"\n- DryRun defaults to true.\n- Backfill writes only missing non-deleted ShopProductVariant offerings.\n- Existing configured offerings are never overwritten.\n- Inactive non-deleted offerings are treated as existing and are not overwritten.\n- Soft-deleted offerings do not block creating a new non-deleted offering.\n- Backfill uses ProductVariant.PriceMinor and ProductVariant.DiscountedPriceMinor.\n- Runtime fallback to ProductVariant pricing remains active.\n- No actual database backfill was executed in Phase 25A.\n```\n\nCurrent goal:\n\n```text id=\"e7711l\"\nUse the Phase 25A tooling in a controlled environment to verify audit, dry-run, write-mode backfill, idempotency, and end-to-end pricing behavior for products with variants.\n```\n\n## Critical Safety Rules\n\n### Production Safety\n\nDo not run write-mode backfill against production.\n\nWrite-mode is allowed only if all of these are true:\n\n```text id=\"8xds4r\"\n1. The environment is explicitly local, development, or stage.\n2. The API base URL clearly indicates local/dev/stage.\n3. A valid admin token is available.\n4. A narrow ShopId or ProductId scope is used for the first write run.\n5. The prompt/session explicitly has PHASE25B_ALLOW_WRITE=true or equivalent explicit local/stage approval.\n```\n\nIf any condition is missing:\n\n```text id=\"m3gnv4\"\n- Run audit and dry-run only.\n- Do not run write-mode.\n- Report what was skipped and why.\n```\n\n### Data Safety\n\nDo not:\n\n```text id=\"sfh6zx\"\n- overwrite existing ShopProductVariant rows;\n- change ProductVariant prices;\n- change ShopProduct prices;\n- change stock/capacity;\n- change orders/cart data;\n- remove fallback;\n- delete data;\n- apply migrations to a real database.\n```\n\n## Required Pre-Check\n\nRun:\n\n```bash id=\"cr5tnf\"\ngit status --short\n```\n\nReport dirty state clearly.\n\nDo not modify source files unless necessary for the report.\n\n## Required Environment Discovery\n\nCheck whether local/stage API execution is possible.\n\nLook for existing environment/run instructions:\n\n```text id=\"ke4j5h\"\nREADME\ndocs\n.env examples\ndocker-compose files\nlaunchSettings.json\nappsettings.Development.json\nAGENTS.md\n.codex reports\n```\n\nFind or infer:\n\n```text id=\"fvt51n\"\nAPI_BASE_URL\nadmin auth/token mechanism\nStore module route prefix\nwhether local API is running\nwhether database is reachable\n```\n\nDo not expose secrets in the report.\n\nIf an admin token is present only as an environment variable, reference it as:\n\n```text id=\"dhs03d\"\nADMIN_TOKEN: present/not present\n```\n\nDo not print the token.\n\n## Required Operational Flow\n\n### 1. Build/Test Baseline\n\nRun backend validation first:\n\n```bash id=\"uopvpi\"\ndotnet restore .\\Refahi.Backend.slnx\ndotnet build .\\Refahi.Backend.slnx --configuration Release --no-restore\ndotnet test .\\Refahi.Backend.slnx --configuration Release --no-build\n```\n\nDo not proceed to API write-mode if build/test fails.\n\n### 2. Audit All or Scoped Data\n\nIf API and admin auth are available, call audit endpoint.\n\nPreferred first call:\n\n```http id=\"juhsth\"\nGET /admin/shop-product-variants/backfill/audit\n```\n\nIf dataset may be large, use filters:\n\n```http id=\"0enbfx\"\nGET /admin/shop-product-variants/backfill/audit?shopId={shopId}\nGET /admin/shop-product-variants/backfill/audit?productId={productId}\nGET /admin/shop-product-variants/backfill/audit?shopId={shopId}&productId={productId}\n```\n\nCapture:\n\n```text id=\"mhhygg\"\nShopProductsChecked\nProductsWithVariants\nExistingOfferings\nMissingOfferings\nfirst-N detail rows\nwarnings/errors\n```\n\nIf API/auth is not available, report audit as not run and explain exactly what is missing.\n\n### 3. Dry-Run Backfill\n\nRun dry-run before any write.\n\nExample payload:\n\n```json id=\"k59jgj\"\n{\n \"shopId\": null,\n \"productId\": null,\n \"dryRun\": true,\n \"detailLimit\": 50\n}\n```\n\nPrefer scoped dry-run first if sample ShopId/ProductId is available.\n\nCapture:\n\n```text id=\"695w3d\"\nCreatedOfferings preview count\nSkippedExistingOfferings\nSkippedInvalidVariants\nWarnings\nCreatedItems preview\n```\n\nDo not run write-mode if dry-run returns invalid price warnings that look unsafe.\n\n### 4. Controlled Write-Mode Backfill\n\nOnly if safety conditions are met.\n\nStart with a narrow scope:\n\n```json id=\"nphh4y\"\n{\n \"shopId\": \"{sampleShopId}\",\n \"productId\": \"{sampleProductId}\",\n \"dryRun\": false,\n \"detailLimit\": 50\n}\n```\n\nAfter write-mode, immediately run:\n\n```text id=\"cml1m6\"\n- audit for the same scope;\n- write-mode again for the same scope to confirm idempotency.\n```\n\nExpected result:\n\n```text id=\"9pp6xc\"\n- First write creates missing rows.\n- Second write creates zero rows.\n- Existing configured rows are not overwritten.\n- Audit missing count decreases.\n```\n\nIf write-mode is not allowed/possible, document the exact API calls that should be run manually later.\n\n### 5. Two-Shop Fixture QA\n\nIf data exists or can be safely identified:\n\nFind or use a product that exists in two shops and has variants.\n\nVerify:\n\n```text id=\"7kegq9\"\n- Shop A has ShopProductVariant row for Variant X.\n- Shop B has ShopProductVariant row for Variant X.\n- Prices can differ between Shop A and Shop B.\n- Product detail with shopSlug A returns price A.\n- Product detail with shopSlug B returns price B.\n```\n\nUse API calls if browser QA is not available:\n\n```http id=\"6o1502\"\nGET /api/store/{moduleSlug}/products/{productSlug}?shopSlug={shopSlugA}\nGET /api/store/{moduleSlug}/products/{productSlug}?shopSlug={shopSlugB}\n```\n\nCheck returned variant fields:\n\n```text id=\"6iwld3\"\nShopProductVariantId\nShopPriceMinor\nShopDiscountedPriceMinor\nPriceSource\nIsActiveInShop\nUsesShopSpecificPrice\nPriceMinor / DiscountedPriceMinor as currently returned\n```\n\n### 6. Cart/Checkout API QA\n\nIf local/stage API, auth, and test data are available:\n\nTest at least one variant item with active `ShopProductVariant`.\n\nVerify:\n\n```text id=\"z2t6zt\"\n- AddToCart uses ShopProductVariant price.\n- GetCart returns ShopProductVariantId and PriceSource.\n- PlaceStoreOrder succeeds when cart price is current.\n- If price changes after item is in cart, checkout rejects stale price or cart shows HasPriceChanged according to Phase 21 behavior.\n```\n\nDo not use real payment rails unless local/stage mocks are explicitly configured.\n\nDo not run wallet/payment flows against production.\n\n### 7. WebApp Browser QA\n\nIf local/stage WebApp and API are available:\n\nVerify:\n\n```text id=\"ze98lz\"\nSame product under Shop A and Shop B:\n- shop-specific route passes ShopSlug;\n- variant selector shows Shop A price on Shop A route;\n- variant selector shows Shop B price on Shop B route;\n- inactive shop variant is disabled;\n- missing shop variant fallback still works if expected;\n- cart row displays correct price;\n- price-change warning blocks checkout when backend says HasPriceChanged.\n```\n\nIf browser QA is unavailable, report not run.\n\n## Optional: Manual Command Templates\n\nIf executing API calls is not possible, provide exact curl/httpie templates using placeholders.\n\nDo not invent real IDs.\n\nTemplate examples:\n\n```bash id=\"lc4i39\"\ncurl -H \"Authorization: Bearer $ADMIN_TOKEN\" \\\n \"$API_BASE_URL/admin/shop-product-variants/backfill/audit?shopId={SHOP_ID}&productId={PRODUCT_ID}\"\n```\n\n```bash id=\"j8m6gw\"\ncurl -X POST \\\n -H \"Authorization: Bearer $ADMIN_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"shopId\":\"{SHOP_ID}\",\"productId\":\"{PRODUCT_ID}\",\"dryRun\":true,\"detailLimit\":50}' \\\n \"$API_BASE_URL/admin/shop-product-variants/backfill\"\n```\n\n```bash id=\"i39dgl\"\ncurl -X POST \\\n -H \"Authorization: Bearer $ADMIN_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"shopId\":\"{SHOP_ID}\",\"productId\":\"{PRODUCT_ID}\",\"dryRun\":false,\"detailLimit\":50}' \\\n \"$API_BASE_URL/admin/shop-product-variants/backfill\"\n```\n\n## Strict Out of Scope\n\nDo not:\n\n```text id=\"t17dvu\"\n- modify Backend source behavior;\n- modify Admin Web;\n- modify Customer WebApp;\n- remove ProductVariant fallback;\n- enforce missing ShopProductVariant rejection;\n- apply DB migrations;\n- run write-mode on production;\n- run unscoped write-mode as the first write;\n- change cart/checkout code;\n- change product detail code;\n- change Orders/Wallet;\n- change Docker/GitHub Actions;\n- change package versions or target frameworks;\n- mark production-ready.\n```\n\n## Final Report Format\n\nSave the report to:\n\n```text id=\"f40rd1\"\n.codex/reports/phase-25b-shopproductvariant-backfill-execution-qa.md\n```\n\nUse exactly this structure:\n\n```text id=\"jv3u6s\"\nSummary:\n- ...\n\nSkills used:\n- ...\n\nRepository checked:\n- ...\n\nGit state:\n- Pre-check:\n- Final:\n\nEnvironment/runtime availability:\n- API base URL:\n- Admin token:\n- Environment classification:\n- Write-mode allowed:\n- Reason:\n\nBuild/test validation:\n- Command: ...\n Result: ...\n\nAudit execution:\n- Endpoint:\n- Scope:\n- Result:\n- Missing offerings:\n- Warnings:\n\nDry-run execution:\n- Endpoint:\n- Scope:\n- Result:\n- Would create:\n- Skipped existing:\n- Skipped invalid:\n- Warnings:\n\nWrite-mode execution:\n- Executed: yes/no\n- Scope:\n- Result:\n- Created:\n- Idempotency re-run:\n- Reason if not executed:\n\nTwo-shop product-detail QA:\n- Executed: yes/no\n- Result:\n- Evidence:\n\nCart/checkout QA:\n- Executed: yes/no\n- Result:\n- Evidence:\n\nWebApp/browser QA:\n- Executed: yes/no\n- Result:\n- Evidence:\n\nData safety findings:\n- ...\n\nFallback behavior:\n- ...\n\nDeferred items:\n- ...\n\nRisks / assumptions:\n- ...\n\nSuggested next phase:\n- ...\n```", "variables": [], "notes": "Read `.codex/prompts/_session-bootstrap.md` first. Then read `AGENTS.md`. Load only the relevant backend/module/store/order architecture skills from `.codex/skills/`.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/refahigroup/refahiplus-api", "path": ".codex/prompts/10-Phase-25b-shopproductvariant-backfill-execution-qa.md", "ref": "18003c6604b9e3d23b1d211e5ee0a2d42ee03cd4", "url": "https://github.com/refahigroup/refahiplus-api/blob/18003c6604b9e3d23b1d211e5ee0a2d42ee03cd4/.codex/prompts/10-Phase-25b-shopproductvariant-backfill-execution-qa.md", "key": "refahigroup/refahiplus-api/.codex/prompts/10-Phase-25b-shopproductvariant-backfill-execution-qa.md" } } }

10-Phase-25b-shopproductvariant-backfill-execution-qa

About

Codex Operational QA Prompt — Phase 25B: Controlled ShopProductVariant Backfill Execution and Fixture QA

Mandatory Report Output

Context

Critical Safety Rules

Production Safety

Data Safety

Required Pre-Check

Required Environment Discovery

Required Operational Flow

1. Build/Test Baseline

2. Audit All or Scoped Data

3. Dry-Run Backfill

4. Controlled Write-Mode Backfill

5. Two-Shop Fixture QA

6. Cart/Checkout API QA

7. WebApp Browser QA

Optional: Manual Command Templates

Strict Out of Scope

Final Report Format

Use it

Manifest

Reviews