@captain_z/zsk 1.6.1 → 1.8.1

package/templates/module/frontend-module/proposal.md

@@ -1,7 +1,32 @@
 # __MODULE_NAME__ Proposal
 
+## Problem
+
+- Target user / stakeholder:
+- Problem:
+- Why now:
+- Source evidence:
+
+## Scope
+
+- In scope:
+- Out of scope:
+- Assumptions:
+- Open questions / blockers:
+
+## Success Criteria
+
+| Criterion | Evidence Source | Owner / Next Stage |
+| --- | --- | --- |
+|  |  |  |
+
+## Risks And Rejected Alternatives
+
+| Item | Decision | Rationale / Evidence |
+| --- | --- | --- |
+|  |  |  |
+
 ## Documentation Feedback
 
 - No-update rationale:
   - Created from the ZSK module template; no proposal has been drafted yet.
-

package/templates/module/frontend-module/spec.md

@@ -1,5 +1,17 @@
 # __MODULE_NAME__ Spec
 
+## Behavior Contract
+
+| ID | Requirement | Type | Source / Decision | Priority | Observable Outcome |
+| --- | --- | --- | --- | --- | --- |
+| FR-001 |  | FR |  | P0 |  |
+
+## Acceptance Criteria
+
+| AC | Linked Requirement | Given / When / Then | Evidence Route |
+| --- | --- | --- | --- |
+| AC-001 | FR-001 | Given  / When  / Then  |  |
+
 ## Scenario Contracts
 
 | Scenario | User Goal | Entry | Preconditions | Observable Result | PRD/SRS / FR/AC | Automate |
@@ -13,6 +25,7 @@ Rules:
 - Mark unclear or conflicting facts as blockers instead of choosing behavior silently.
 - Do not write brittle selectors in spec.
 - Mark which P0/P1 scenarios must become Playwright cases.
+- Keep implementation choices out unless they are part of the product contract.
 
 ## Documentation Feedback
 

package/templates/module/frontend-module/tasks.md

@@ -1,17 +1,30 @@
 # __MODULE_NAME__ Tasks
 
+## Execution Plan
+
+| ID | Task | Depends On | Scope / Files | Linked FR/AC | Evidence Hook | Status |
+| --- | --- | --- | --- | --- | --- | --- |
+| T-001 |  |  |  | FR-001 / AC-001 |  | TODO |
+
+## Coverage Matrix
+
+| FR/AC | Implementation Task | Test / Scenario Task | Docs / Issue / Evidence Task |
+| --- | --- | --- | --- |
+| FR-001 / AC-001 | T-001 |  |  |
+
 ## Playwright Case Tasks
 
 | Task | Scenario Contract | Case File | Fixture/Auth | Reuse Target | Status |
 | --- | --- | --- | --- | --- | --- |
-| Create P0 happy path skeleton | P0 happy path | `scenarios/p0-happy-path.spec.ts` |  | demo, verify, regression | TODO |
+| Create P0 happy path skeleton | P0 happy path | `__PLAYWRIGHT_SPECS__/p0-happy-path.spec.ts` |  | demo, verify, regression | TODO |
 
 Rules:
 
-- Create Playwright skeletons before demo.
+- Create Playwright skeletons under `__PLAYWRIGHT_SPECS__` before demo.
 - Create or update source-aligned tests/scenarios before implementation for testable behavior changes.
 - Tag cases as smoke/demo/verify/regression.
 - Include tasks for labels/test ids required by stable locators.
+- Do not create vague tasks such as "implement feature"; each task needs scope, dependency, and evidence.
 
 ## Documentation Feedback
 

package/templates/project-init/.zsk/config.yaml

@@ -1,16 +1,22 @@
 # yaml-language-server: $schema=__ZSK_CONFIG_SCHEMA_URL__
 
+layoutVersion: 2
+
 project:
   name: "<project-name>"
 
 paths:
-  raws: .raws
-  docs: docs
-  issues: .issues
+  docs: .zsk/docs
+  modules: .zsk/modules
+  raws: .zsk/raws
+  issues: .zsk/issues
+  evidence: .zsk/evidence
+  playwright: .zsk/playwright
 
-# Resource origins. AI or zsk config setup should fill these with online URLs,
-# git repositories, Figma/Modao links, OpenAPI locations, or local files.
-# Optional snapshots should land under paths.raws, for example:
+# Raw source origins. AI or zsk config setup should fill these with online URLs,
+# git repositories, design-platform links/assets, OpenAPI locations, or local files.
+# Optional snapshots should land under paths.raws with stable role/provider paths.
+# Dates belong in manifest metadata such as syncedAt, not in path authority.
 #
 # sources:
 #   srs:
@@ -18,26 +24,27 @@ paths:
 #     origin:
 #       kind: url
 #       url: https://example.com/srs
-#     snapshot: .raws/requirements/srs.md
-#   figma_main:
+#     snapshot: .zsk/raws/product/srs.md
+#   design_main:
 #     type: design
 #     origin:
-#       kind: figma
+#       kind: design
+#       provider: figma
 #       url: https://www.figma.com/file/...
-#     snapshot: .raws/design-sources/figma-main.json
+#     snapshot: .zsk/raws/ue/design-main.json
 #   backend_api:
-#     type: backend_repo
+#     type: api_contract
 #     origin:
 #       kind: git
 #       repository: https://github.com/example/backend-api.git
 #       path: openapi.yaml
-#     snapshot: .raws/backend-repositories/backend-openapi.yaml
+#     snapshot: .zsk/raws/backend/api-contract.yaml
 #   acceptance_cases:
 #     type: test_case
 #     origin:
 #       kind: url
 #       url: https://example.com/qa-cases
-#     snapshot: .raws/testing/acceptance-cases.md
+#     snapshot: .zsk/raws/qa/testing/acceptance-cases.md
 sources: {}
 
 tools:
@@ -45,14 +52,15 @@ tools:
     - playwright_cli
     - playwright_mcp
     - playwright
-    - browser_use
     - computer_use
+    - browser_use
   design:
+    - manual
     - figma_mcp
 
 modules:
-  index: docs/_module-index.md
-  root: docs
+  index: .zsk/modules/index.md
+  root: .zsk/modules
 
 automation:
   smoke:
@@ -63,17 +71,20 @@ automation:
   deploy:
     command: pnpm deploy:staging
   demo:
-    # Default hybrid lane:
-    # - Playwright CLI/UI mode is preferred for visible demo performance, controlled stop/pause, screenshots, traces, reports, and repeatable runs.
-    # - Playwright MCP inspects structured accessibility snapshots and proposes operations when needed.
-    # - Browser Use identifies the human-intent target and preserves existing logged-in browser/profile state when auth cannot be reproduced cheaply.
-    # - Computer Use is reserved for visual/system-level context that browser automation cannot expose.
-    # - Playwright consumes the handoff to pre-write/rehearse scenarios, then performs the external demo with visible trace/report evidence.
-    defaultMode: hybrid
+    # Default optimized lane:
+    # - Formal test cases come from module tests.raw_cases or sources.testing, normally snapshots under .zsk/raws/qa/testing.
+    # - Playwright storageState is the preferred way to reuse login/session state without stopping on login pages.
+    # - Computer Use is the preferred visual/current-page observation lane when it is available and authorized.
+    # - Browser Use is optional and runtime-specific; use it only where the agent platform supports it and permissions are available.
+    # - If neither Computer Use nor Browser Use exists, use Playwright MCP/ARIA/CDP snapshots or documented manual evidence as the compatible handoff.
+    # - zsk/agent generation writes test-plan.json, then Playwright CLI/Skills generate executable .spec.ts cases.
+    # - Playwright Test executes/debugs and records evidence. No MCP or bridge fallback is used in optimized mode.
+    # - Use --hybrid explicitly for the legacy bridge lane.
+    defaultMode: optimized
     baseUrl: http://localhost:3000
     command: pnpm dev
-    evidenceDir: .issues/{module}/demo/_evidence
-    scenarioDir: docs/{module}/scenarios
+    evidenceDir: .zsk/modules/{module}/_evidence/demo
+    scenarioDir: .zsk/modules/{module}/_playwright/specs
     playwright:
       config: playwright.config.ts
       project: chromium
@@ -83,12 +94,13 @@ automation:
       role: understand-and-decide
     bridge:
       enabled: true
-      # decisionTool may be playwright_mcp for structured accessibility snapshots,
-      # browser_use for existing login/profile state, or computer_use for visual/system-level understanding.
+      # Legacy hybrid-only bridge. Not used by defaultMode: optimized.
+      # Prefer computer_use for visual/system-level understanding when available.
+      # Fall back to playwright_mcp for structured accessibility snapshots, or browser_use only on runtimes that support it.
       decisionTool: playwright_mcp
       executionTool: playwright
-      planFile: .zsk/demo-sessions/{module}/operation-plan.json
-      executionFile: .zsk/demo-sessions/{module}/playwright-execution.json
+      planFile: .zsk/modules/{module}/_playwright/execution/operation-plan.json
+      executionFile: .zsk/modules/{module}/_playwright/execution/playwright-execution.json
   verify:
     commands:
       - pnpm test:e2e

package/templates/project-init/.zsk/docs/PROJECT-CONFIG.md

@@ -0,0 +1,62 @@
+# Project Config
+
+This file is the human-readable companion to `.zsk/config.yaml`.
+
+## Halcyon Layer
+
+This `.zsk/` workspace is project-specific. It is the Halcyon operating layer for this project: the place where AI agents read raw facts, produce stage documents, route issues/evidence, and prove stage completion. It is not a generic docs folder and it is not a replacement for the application's source tree.
+
+Use this layer to answer three questions before execution:
+
+- What facts and decisions are authoritative for this project?
+- Which module/stage owns the next artifact?
+- What evidence or issue update proves the stage is complete?
+
+## Workspace Layout
+
+`zsk init` owns only the `.zsk/` workspace by default:
+
+| Path | Purpose |
+| --- | --- |
+| `.zsk/config.yaml` | Machine-readable project config and path authority |
+| `.zsk/docs/` | Project-level docs such as this file and `SYSTEM-SPEC.md` |
+| `.zsk/modules/{module}/` | Module `module.yaml`, `proposal.md`, `spec.md`, `design.md`, `tasks.md` |
+| `.zsk/raws/` | Immutable raw fact sources and manifest/index files |
+| `.zsk/modules/{module}/_issues/` | Module-private issue records, created on demand |
+| `.zsk/modules/{module}/_evidence/` | Module-private evidence, screenshots, traces, logs, and verification artifacts, created on demand |
+| `.zsk/modules/{module}/_playwright/` | Module-specific Playwright specs, plans, auth state, results, reports, and execution records, created on demand |
+| `.zsk/playwright/` | Shared Playwright config/auth/helpers only, created on demand |
+
+Root `docs/`, `.raws/`, `.issues/`, and `.playwright/` are not default write targets. Use explicit export or migration tooling when you need project-root copies.
+
+## Source Priorities
+
+1. `.zsk/config.yaml`
+2. `.zsk/docs/SYSTEM-SPEC.md`
+3. Project resource origins listed under `.zsk/config.yaml#sources`
+4. `.zsk/raws/manifest.json` and `.zsk/raws/index.md`
+5. `.zsk/modules/{module}/module.yaml`
+6. `.zsk/modules/{module}/spec.md`
+7. `.zsk/modules/{module}/design.md`
+8. Runtime evidence under module `_evidence` / `_playwright` or shared `.zsk/evidence` / `.zsk/playwright`
+
+When sources conflict, record the conflict under the module `_issues` directory, or shared `.zsk/issues` only for cross-module/global issues, and update the affected module docs with a Documentation Feedback note or an explicit no-update rationale.
+
+## Authoring Rule
+
+Every module stage document is a handoff contract:
+
+- `proposal.md` explains why the work exists, who it serves, what is in scope, what is out of scope, and how success will be recognized.
+- `spec.md` defines observable behavior, scenarios, acceptance criteria, edge cases, and source-linked assumptions.
+- `design.md` maps approved behavior to implementation surfaces, interfaces, state, data flow, risks, and verification strategy.
+- `tasks.md` breaks the design into ordered work with owners/scope, dependencies, FR/AC coverage, and evidence hooks.
+
+If a document cannot answer its stage questions, stop and record the missing source, decision, blocker, or issue instead of filling the template.
+
+## Maintenance Checklist
+
+- Update `.zsk/config.yaml` when paths, tools, or source origins change.
+- Keep project-wide reusable rules in `.zsk/docs/SYSTEM-SPEC.md`.
+- Keep module-specific decisions in `.zsk/modules/{module}/`.
+- Keep shared raw source facts under `.zsk/raws/`.
+- Keep runtime outputs out of docs and under module-private `_evidence` / `_playwright` unless they are deliberately shared under `.zsk/evidence` / `.zsk/playwright`.

package/templates/project-init/.zsk/docs/SYSTEM-SPEC.md

@@ -0,0 +1,59 @@
+# System Spec
+
+This document captures project-wide rules that should guide module work.
+
+## Operating Model
+
+The `.zsk/` workspace is this project's Halcyon layer. It keeps AI execution grounded by separating:
+
+- raw facts under `paths.raws`;
+- project-wide rules under `paths.docs`;
+- module-owned stage contracts under `paths.modules`;
+- runtime evidence under module `_evidence` or shared `paths.evidence`;
+- issue records under module `_issues` or shared/global `paths.issues`;
+- Playwright plans/specs/results under module `_playwright` or shared `paths.playwright`.
+
+Agents must use the smallest sufficient lane: read local sources first, run deterministic CLI checks when possible, delegate only when the work has independent expert lanes, and record blockers instead of filling missing facts from chat memory.
+
+## Path Boundaries
+
+- `paths.docs` stores project-level docs only.
+- `paths.modules` stores module source-of-truth docs.
+- `paths.raws` stores immutable shared source snapshots and manually provided fact sources.
+- Module `_issues` stores module-specific actionable issue records; `paths.issues` is created on demand only for shared/global indexes or cross-module issues.
+- Module `_evidence` stores module-specific runtime evidence and verification artifacts; `paths.evidence` is created on demand only for shared/global evidence.
+- Module `_playwright` stores module-specific Playwright specs, plans, auth state, results, reports, and execution records; `paths.playwright` is created on demand only for shared Playwright assets.
+
+Root `docs/`, `.raws/`, `.issues/`, and `.playwright/` are legacy or export surfaces, not default zsk write targets.
+
+## Testing Assets
+
+Original QA, acceptance, release, and manually supplied test cases belong in configured project sources and may be snapshotted under `paths.raws`, normally `.zsk/raws/qa/testing`. Module-derived test plans and Playwright specs belong under module `_playwright` unless they are intentionally shared under `paths.playwright`.
+
+## Completion Feedback
+
+Every stage document that changes durable behavior should include Documentation Feedback with either:
+
+- a concrete update to project/module docs, or
+- an explicit no-update rationale.
+
+Runtime evidence should be linked from docs, not embedded in docs.
+
+## Stage Document Standards
+
+ZSK stage documents are decision artifacts. They are complete only when the next stage can act without hidden chat context.
+
+| Stage | Document Mode | Must Prove |
+| --- | --- | --- |
+| `prepare` | Evidence report | Source origins, freshness, conflicts, and raw snapshot paths are known before planning. |
+| `proposal` | Decision brief | Problem, user/business outcome, scope, non-goals, risks, and success criteria are explicit. |
+| `spec` | Behavior contract | FR/NFR, scenarios, edge cases, and acceptance criteria are observable and source-linked. |
+| `design` | Implementation contract | Behavior maps to files/modules/interfaces/state/data flow, with risks and verification strategy. |
+| `task` | Execution plan | Work is ordered, owned, independently reviewable, and tied to FR/AC plus evidence hooks. |
+| `coding` | Implementation evidence | Changed files, behavior, tests, and residual risks are tied back to tasks. |
+| `smoke` | Evidence report | Local proof names the claim, command/scenario, result, artifacts, and failures. |
+| `review` | Evidence report | Findings are severity-ranked, traceable, and cover scope, correctness, tests, risk, and harness compliance. |
+| `ready` | Verification handoff | Fixed issues, AC, evidence, replay steps, version, and residual risks are mapped. |
+| `verify` | Independent evidence | The ready claim is replayed with fresh evidence and pass/fail issue status updates. |
+
+Each stage document must separate facts, decisions, assumptions, open questions, evidence, and next action. Do not leave template filler, untraceable "best practice" claims, vague tasks, or unresolved contradictions in a stage artifact.

package/templates/project-init/.zsk/modules/index.md

@@ -0,0 +1,7 @@
+# Module Index
+
+Generated and refreshed as modules are added.
+
+| Module | Status | Notes |
+| --- | --- | --- |
+|  |  |  |

package/templates/project-init/.zsk/raws/backend/index.md

@@ -0,0 +1,3 @@
+# Backend Sources
+
+Backend repositories, API contracts, OpenAPI files, and integration notes.

package/templates/project-init/.zsk/raws/index.md

@@ -0,0 +1,7 @@
+# Raw Source Index
+
+Immutable fact sources for this project. Generated and refreshed by `zsk prep`.
+
+| Provider | Type | Status | Snapshot / Origin |
+| --- | --- | --- | --- |
+|  |  |  |  |

package/templates/project-init/.zsk/raws/jira/index.md

@@ -0,0 +1,3 @@
+# Jira Sources
+
+Jira exports, linked issue references, and ticket snapshots.

package/templates/project-init/.zsk/raws/manual/index.md

@@ -0,0 +1,3 @@
+# Manual Sources
+
+Manually supplied notes, local files, and ad hoc source material.

package/templates/project-init/.zsk/raws/product/index.md

@@ -0,0 +1,3 @@
+# Product Sources
+
+SRS, PRD, requirements, release notes, and customer/product feedback.

package/templates/project-init/.zsk/raws/qa/index.md

@@ -0,0 +1,3 @@
+# QA Sources
+
+QA cases, acceptance cases, test data, and verification source material.

package/templates/project-init/.zsk/raws/ue/index.md

@@ -0,0 +1,3 @@
+# UE Sources
+
+Design handoff, Figma/Modao references, UX notes, and interaction assets.

package/templates/module/frontend-module/acceptance.md

@@ -1,18 +0,0 @@
-# __MODULE_NAME__ Acceptance
-
-## Verdict
-
-- Result: NOT_STARTED
-- Accepted by:
-- Date:
-
-## Evidence Summary
-
-| Source | Conclusion | Link |
-| --- | --- | --- |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no acceptance has been performed yet.
-

package/templates/module/frontend-module/archive.md

@@ -1,17 +0,0 @@
-# __MODULE_NAME__ Archive
-
-## Closure
-
-| Item | Link |
-| --- | --- |
-
-## Learning Proposals
-
-| Finding | Target | Evidence |
-| --- | --- | --- |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; archive has not run yet.
-

package/templates/module/frontend-module/commit.md

@@ -1,15 +0,0 @@
-# __MODULE_NAME__ Commit
-
-## Commit Evidence
-
-| Item | Evidence |
-| --- | --- |
-| Review gate | |
-| Smoke gate | |
-| Commit | |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no commit evidence has been captured yet.
-

package/templates/module/frontend-module/demo-outline.md

@@ -1,59 +0,0 @@
-# __MODULE_NAME__ Demo Outline
-
-## Demo Flow
-
-Use this section as the speaking order. The audience should be able to follow the demo from top to bottom without reading any appendix.
-
-| Step | Show | Function / Business Point | Scenario | Source Alignment | Playwright Case | Presenter Line | Expected Visible Result | Next |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| 1 | Starting state and primary goal |  |  | PRD/SRS + Spec + Task + Test | `scenarios/<case>.spec.ts` |  |  | 2 |
-| 2 | Core happy path / main value |  |  | PRD/SRS + Spec + Task + Test | `scenarios/<case>.spec.ts` |  |  | 3 |
-| 3 | Required branch / role / validation / edge |  |  | PRD/SRS + Spec + Task + Test | `scenarios/<case>.spec.ts` |  |  | Final |
-| Final | Final state, evidence, and known gaps |  |  | PRD/SRS + Spec + Task + Test |  | summarize evidence and known gaps |  | close |
-
-## Opening
-
-- Audience:
-- One-sentence goal:
-- Starting state:
-- Primary user journey:
-- What this demo proves:
-
-## Coverage Alignment
-
-Every required function point in the PRD/SRS should appear here, either as a demo step or as a known gap.
-
-| Function / Business Point | PRD / SRS Need | Spec / Design Contract | Task Scope | Test Case / Assertion | Demo Step | Status |
-| --- | --- | --- | --- | --- | --- | --- |
-|  |  |  |  |  | 1 | covered |
-|  |  |  |  |  | 2 | covered |
-|  |  |  |  |  | 3 | covered |
-
-## Rehearsal Checklist
-
-| Demo Step | Browser Use Handoff | Playwright Case | Rehearsed | Evidence | Ready |
-| --- | --- | --- | --- | --- | --- |
-| 1 |  |  | no | trace/report/screenshot | no |
-| 2 |  |  | no | trace/report/screenshot | no |
-| 3 |  |  | no | trace/report/screenshot | no |
-
-## Pause Rules
-
-- Pause if login/session state is lost.
-- Pause if the UI no longer matches the prepared Playwright case.
-- Pause if a P0/P1 function point cannot be shown.
-- Do not improvise new clicks during the external demo; record the blocker and return to Demo Prep.
-
-## Appendix: Prep Sources
-
-| Source | Path / Link | Used For |
-| --- | --- | --- |
-| SRS / PRD |  | user goal and scope |
-| Spec / AC |  | observable pass criteria |
-| Test cases |  | scenario steps and expected result |
-| Browser Use handoff |  | login state, visible target, candidate locators |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no demo outline has been generated yet.

package/templates/module/frontend-module/demo-report.md

@@ -1,23 +0,0 @@
-# __MODULE_NAME__ Demo Report
-
-## Session
-
-- Session id:
-- Status: NOT_STARTED
-- Mode:
-
-## Coverage
-
-| Function Point | FR/AC | Scenario | Result | Evidence | Issues |
-| --- | --- | --- | --- | --- | --- |
-
-## Reusable Scenarios
-
-| Scenario | Source | Reuse Target | Evidence |
-| --- | --- | --- | --- |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no demo has been performed yet.
-

package/templates/module/frontend-module/deploy.md

@@ -1,18 +0,0 @@
-# __MODULE_NAME__ Deploy
-
-## Deployment
-
-| Environment | URL | Version | Result | Evidence |
-| --- | --- | --- | --- | --- |
-
-## Rollback
-
-- Owner:
-- Command:
-- Notes:
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no deployment has been performed yet.
-

package/templates/module/frontend-module/ready.md

@@ -1,12 +0,0 @@
-# __MODULE_NAME__ Ready
-
-## Gate
-
-| Issue | Fix Evidence | Deployment | Ready |
-| --- | --- | --- | --- |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no fixes have been marked ready for verify yet.
-

package/templates/module/frontend-module/review.md

@@ -1,12 +0,0 @@
-# __MODULE_NAME__ Review
-
-## Review Findings
-
-| Finding | Severity | Owner | Issue |
-| --- | --- | --- | --- |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no review has been performed yet.
-

package/templates/module/frontend-module/scenarios/index.md

@@ -1,21 +0,0 @@
-# __MODULE_NAME__ Scenarios
-
-Reusable demo, verify, and regression scenarios for this module.
-
-Use this index to keep human test cases, Playwright scenarios, and evidence links aligned with module FR/AC IDs. Scenario files should stay module-local and should be referenced from `module.yaml` when they become part of the verification baseline.
-
-## Scenario Lifecycle
-
-| Stage | Responsibility |
-| --- | --- |
-| Spec | Define scenario contract and FR/AC linkage |
-| Design | Define locator/state/auth/evidence strategy |
-| Task | Create Playwright skeleton and fixture work |
-| Demo | Execute, record, and promote scenarios |
-| Verify | Reuse scenarios for fix verification |
-
-## Scenario Index
-
-| Scenario | FR/AC Link | Automation | Evidence | Status |
-| --- | --- | --- | --- | --- |
-| `<scenario-name>` | `<FR/AC id>` | manual / Playwright / other | `<relative evidence path>` | draft / active / blocked / retired |

package/templates/module/frontend-module/scenarios/p0-happy-path.spec.ts

@@ -1,13 +0,0 @@
-import { test, expect } from "@playwright/test";
-
-test.describe("__MODULE_NAME__ demo scenarios", () => {
-  test("P0 happy path", async ({ page }) => {
-    test.skip(!process.env.ZSK_DEMO_BASE_URL, "Set ZSK_DEMO_BASE_URL to run this scenario.");
-
-    await page.goto(process.env.ZSK_DEMO_BASE_URL);
-
-    // Replace this with the scenario contract from spec.md and locator strategy from design.md.
-    await expect(page).toHaveURL(/.+/);
-  });
-});
-

package/templates/module/frontend-module/smoke.md

@@ -1,21 +0,0 @@
-# __MODULE_NAME__ Smoke
-
-## Resource Contract
-
-| Resource | Required | Source | Status | Used For | Blocker If Missing |
-| --- | --- | --- | --- | --- | --- |
-
-## Checks
-
-| Check | Command | Result | Evidence |
-| --- | --- | --- | --- |
-
-## Test Alignment
-
-| Test / Scenario | Source Requirement / Design / Issue | Expected Behavior | Accurate | Evidence |
-| --- | --- | --- | --- | --- |
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no smoke has been performed yet.

package/templates/module/frontend-module/verification.md

@@ -1,6 +0,0 @@
-# __MODULE_NAME__ Verification
-
-## Documentation Feedback
-
-- No-update rationale:
-  - Created from the ZSK module template; no verification has been performed yet.