10. Starter Kit Behavior

Full Starter Kit mechanics are documented in Tenant Starter Kit & Product Catalog. The Starter Kit remains root-admin-only by design — see the Tenant Signup guide, Chapter 11 — and this task did not expose it to any tenant's own first-login flow. This chapter records the live-verified Preview (read-only, never writes) result for each of the four packages, run with a root-tenant admin token, exactly as the task instructed ("run root-admin StarterKit Preview only").

10.1 Live-verified Preview results

Package	Accounting chain (ChartAccounts/Mappings/InventoryAccountCategory)	CostCenters	Product chain (Prerequisites/Categories/Items)
Shumoul Starter	Blocked — no Features.AccountManagement entitlement	Skipped — onboarding answer said not needed	Failed — accounting/product apply bridges disabled (pre-existing, unrelated to entitlement)
Shumoul POS	Blocked — no Features.AccountManagement entitlement	Skipped — onboarding answer said not needed	Failed — apply bridge disabled (same as above)
Shumoul Finance Starter	Failed — apply bridge disabled (not Blocked — confirms Features.AccountManagement is entitled)	Skipped — downstream of the failed accounts step	Skipped — no Features.ProductsManagement entitlement
Shumoul Finance Advanced	Failed — apply bridge disabled (confirms entitlement present)	Skipped — downstream of the failed accounts step	Skipped — no Features.ProductsManagement entitlement

10.2 Reading Blocked vs. Failed correctly

This distinction is the actual proof the package design works as intended:

• Blocked means the tenant's subscription does not entitle the step at all — Starter/POS show Blocked on every accounting step, confirming Features.AccountManagement is correctly excluded from both.
• Failed means the step would have been attempted (entitlement present) but a downstream apply-bridge dependency is disabled — Finance Starter/Advanced show Failed (not Blocked) on AccountingChartAccounts, confirming Features.AccountManagement is correctly included. The bridge-disabled condition itself is a pre-existing, already-documented dev-safety default (see the Tenant Starter Kit guide's own staging verification chapter) — not a defect introduced by this task.

The Product chain shows the exact mirror image: Failed (bridge-only) for Starter/POS (which do carry Features.ProductsManagement), and Skipped — explicitly citing the missing entitlement — for both Finance packages (which correctly do not).

Update: the accounting chain gained a fifth step, CashBankAccountingLink, between AccountingChartMappings and InventoryAccountCategory — see Cash/Bank GL-Currency Linking. It is gated by the same Features.AccountManagement entitlement as the rest of this chain, so it reads Blocked/Failed identically to AccountingChartMappings in the table above for every package.

10.3 Cost centers and needsCostCenters

CostCenters inclusion depends on the onboarding needsCostCenters answer and the Features.AccountManagement entitlement and the CostCenterSettings settings-group entitlement (see the Starter Kit guide's own architecture chapter). In this task's live run, the CostCenters step for both finance packages was Skipped as a downstream consequence of the (bridge-disabled) accounts step failing, not because of the needsCostCenters answer itself — so the Simple vs. Mandatory answer differentiation between Finance Starter and Finance Advanced was not independently observable in this dev session. The underlying CostCenterSettings entitlement difference (both finance packages have it, Starter/POS do not) was already confirmed directly via the onboarding recommendation step (Chapter 9).

10.4 Apply was not run

Consistent with the task's instruction, only Preview was called for all four packages — no tenant database was written by this task's live verification.