ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/355-platform-sellable-smoke-matrix/artifacts/blocked-fixtures.md
ahmido f35782a163 feat: platform sellable smoke matrix (spec 355) (#426) 
Added artifacts, screenshots, and documentation for the platform sellable smoke matrix. Fixed a bug in FindingRiskGovernanceResolver and updated related tests.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #426
2026-06-05 10:42:31 +00:00

2.7 KiB
Raw Permalink Blame History

Blocked Fixtures

Status: inventoried
Spec: specs/355-platform-sellable-smoke-matrix/spec.md

Use this file only when a required smoke state cannot be exercised honestly with current local/testing data.

Available States

  • Provider blocker: workspace=spec-352-guidance-browser-audit, environment=spec-352-audit-provider-blocker, user smoke-requester+352@tenantpilot.local
  • Review-output blocker with existing draft: workspace=spec-352-guidance-browser-audit, environment=spec-352-audit-review-output, review #31
  • Review-output owner surface with reusable open-draft path: workspace=spec-352-guidance-browser-audit, environment=spec-352-audit-review-output, user smoke-requester+352@tenantpilot.local
  • Calm no-urgent-action dashboard: workspace=spec-352-guidance-browser-audit, environment=spec-352-audit-no-urgent
  • Evidence incomplete with customer-safe boundary and operation proof: workspace wp, environment=spec342-demo-evidence-incomplete, operation #24
  • Governance Inbox queue item: workspace wp, environment=spec342-demo-accepted-risks
  • Accepted-risk focused review lane: workspace wp, environment=spec342-demo-accepted-risks
  • Accepted-risk expiring, expired, and incomplete states used for the browser matrix: workspace wp, environment=spec342-demo-accepted-risks, exceptions #7, #8, #9

Missing States

  • Clean provider verification-failed demo record was not persisted in the local DB during the Spec 355 run. Provider verification guidance was therefore verified through the provider-blocked permissions path and the Provider Connections owner surface instead.
  • Pending-renewal non-lapsed and lapsed accepted-risk cases were not re-run in the Spec 355 browser matrix, even though Spec 354 already has dedicated browser and feature coverage for them.

Blockers

  • The dedicated Spec 354 browser fixture user (spec354-browser-wj5ugjux@example.test) did not remain reusable through the Playwright smoke-login flow in this local browser session, even though the route itself responded correctly. To avoid a false negative, the accepted-risk queue proof was run against the stable workspace wp operator fixture instead.
  • Clean expiring and expired accepted-risk states in workspace wp needed small local-only fixture augmentation via tinker because the persisted demo records mixed expiring and incomplete governance semantics.

Next Actions

  • Keep the smoke matrix conservative.
  • Do not invent repo code or broaden runtime scope just to clear a blocked flow.
  • If Spec 355 needs a future repeatable fixture pack, add a dedicated local seeder in a follow-up slice rather than widening this verification gate.