@captain_z/zsk 1.7.0 → 1.8.1

package/templates/project-init/.zsk/issues/README.md

@@ -1,58 +0,0 @@
-# .zsk/issues - Local Verification And Bug Evidence
-
-This is the default issue root configured by `.zsk/config.yaml` `paths.issues`. It stores local review findings, bug reports, screenshots, logs, reproduction evidence, and verification records created during project work.
-
-Every actionable finding from demo, smoke, review, formal test, verify, or acceptance should be persisted here or under the configured `paths.issues` root. Chat-only findings are not durable tracking.
-
-## Directory Contract
-
-```text
-.zsk/issues/
-├── README.md
-├── _taxonomy.md
-├── index.md                         # global module issue totals
-└── {area-or-module}/
-    ├── index.md                     # module issue index and status table
-    ├── BUG-0001-short-slug/
-    │   ├── issue.md                 # required issue body
-    │   ├── analysis.md              # optional root-cause notes
-    │   ├── reproduction.md          # optional detailed repro script
-    │   ├── assets/                  # screenshots, videos, HAR, exported state
-    │   │   └── index.md
-    │   └── debug-logs/              # console, test, network, investigation logs
-    │       └── index.md
-    ├── demo/                        # optional stage view / evidence bucket
-    │   └── index.md
-    ├── _evidence/                   # shared evidence referenced by multiple issues/docs
-    └── _debug-logs/                 # untriaged or cross-issue historical logs only
-```
-
-Use `zsk issue create -m <module-id>` to generate issue folders from the packaged template. `zsk init` does not write `_templates/` into the project.
-
-`zsk issue update -m <module-id> --id <issue-dir> --status <status>` updates the concrete issue and refreshes:
-
-- `.zsk/issues/{module}/index.md` - all issues and statuses for one module.
-- `.zsk/issues/index.md` - module totals across the project.
-
-## Bug Directory Rules
-
-- Keep one confirmed bug per `BUG-xxxx-short-slug/` directory.
-- Put the issue body in `issue.md`.
-- Put screenshots, recordings, HAR files, JSON payloads, exported browser state, and reproduction artifacts that belong to one bug under that bug's `assets/`.
-- Put console output, test output, debug logs, and investigation notes that belong to one bug under that bug's `debug-logs/`.
-- Use `analysis.md` only when root-cause reasoning is long enough that it would obscure the issue body.
-- If two symptoms share one root cause, keep one bug directory and list all symptoms as evidence inside it.
-
-## Closure And Documentation Feedback
-
-- Record the affected PRD/SRS, spec, design, task, test case, and evidence links in the issue.
-- After the fix is verified and confirmed by the user/product owner, update the relevant `.zsk/modules/{module}/spec.md`, `.zsk/modules/{module}/design.md`, `.zsk/modules/{module}/tasks.md`, or `.zsk/docs/SYSTEM-SPEC.md` for gaps or vague behavior exposed by the issue.
-- Close the issue only after it links verification evidence, confirmation, documentation feedback update or no-update rationale, and regression guard.
-
-## Relationship To Other Project Directories
-
-| Directory | Purpose | May contain local screenshots/logs? |
-|---|---|---|
-| `.zsk/resources/` | Upstream facts, mirrored snapshots, original external test cases | No |
-| `.zsk/modules/{module}/` | Human-authored module proposal/spec/design/tasks | No |
-| `.zsk/issues/{module}/` | Local defects, verification evidence, debug logs, issue-quality records | Yes |

package/templates/project-init/.zsk/issues/_taxonomy.md

@@ -1,35 +0,0 @@
-# Issue Taxonomy
-
-Managed issue records belong under `.zsk/issues/` or the configured `.zsk/config.yaml#paths.issues` root.
-
-Each module has a module index at `.zsk/issues/{module}/index.md`. The issue root has a global index at `.zsk/issues/index.md` with module totals. `zsk issue create` and `zsk issue update` refresh both indexes.
-
-| Type | Concrete Issue Directory | Prefix |
-| --- | --- | --- |
-| Demo Issue | `.zsk/issues/{module}/{prefix}-0001-slug/` | `DEMO` |
-| Smoke Issue | `.zsk/issues/{module}/{prefix}-0001-slug/` | `SMOKE` |
-| Review Issue | `.zsk/issues/{module}/{prefix}-0001-slug/` | `REV` |
-| Defect | `.zsk/issues/{module}/{prefix}-0001-slug/` | `DEFECT` |
-| Verify Issue | `.zsk/issues/{module}/{prefix}-0001-slug/` | `VER` |
-| Acceptance Issue | `.zsk/issues/{module}/{prefix}-0001-slug/` | `ACC` |
-
-Stage directories such as `.zsk/issues/{module}/demo/index.md` may exist as stage views or evidence buckets. The authoritative status indexes are `.zsk/issues/{module}/index.md` and `.zsk/issues/index.md`.
-
-`.zsk/resources/issues/` is reserved for imported external issue feeds or compatibility inputs.
-
-## Required Intake
-
-Every actionable issue should include:
-
-- reproduction steps or triggering command;
-- actual/current behavior;
-- expected behavior;
-- severity and rationale;
-- environment/version/data source;
-- evidence links;
-- root-cause hypothesis and confidence;
-- fix route;
-- Documentation Feedback target or no-update rationale;
-- regression guard;
-- verification evidence and user/product confirmation before closing behavior-changing issues;
-- updated module index and global issue index.

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

@@ -1,7 +0,0 @@
-# Issues Index
-
-Module-level issue totals. `zsk issue create` and `zsk issue update` refresh this file.
-
-| Module | Total | Open | Closed |
-| --- | ---: | ---: | ---: |
-|  | 0 | 0 | 0 |

package/templates/project-init/.zsk/modules/.gitkeep

@@ -1 +0,0 @@
-

package/templates/project-init/.zsk/plans/.gitkeep

@@ -1 +0,0 @@
-

package/templates/project-init/.zsk/playwright/.gitkeep

@@ -1 +0,0 @@
-

package/templates/project-init/.zsk/resources/.gitkeep

@@ -1 +0,0 @@
-