@captain_z/zsk 1.8.5 → 1.8.7

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

@@ -1,5 +1,8 @@
-# Example provider/resource/route shapes. Copy only the entries this project
-# actually needs into .zsk/config.yaml.
+# Example provider/entry-source/route shapes. Configure each platform once,
+# then add only durable entry sources to .zsk/config.yaml. Let prepare produce
+# .zsk/evidence/prepare/<run>/config-draft.yaml and
+# source-promotion-suggestions.md for discovered child pages, nodes, issues, or
+# files; promote selected candidates only after human review.
 #
 # Store secret values in the shell environment, not in config. If credentials
 # live in ~/.zshrc, export them there, for example:
@@ -43,14 +46,14 @@ automation:
         submit: button[type="submit"]
 
 resources:
-  - id: core-api
+  - id: core-api-entry
     type: repository
     area: Backend Services
     source:
       kind: git-submodule
-      path: .zsk/raws/repositories/core-api/repository
+      path: .zsk/raws/repositories/core-api-entry/repository
 
-  - id: my-bugs
+  - id: assigned-bugs-entry
     type: issues
     provider: jira
     query:
@@ -58,15 +61,17 @@ resources:
     classify:
       by: [priority, component, status]
 
-  - id: role-prd
+  - id: product-requirements-entry
     type: document
     area: Confluence
     provider: confluence
     source:
       kind: confluence
       pageId: "12345"
+    metadata:
+      note: Child Confluence pages should be reviewed in config-draft.yaml before promotion.
 
-  - id: public-prd
+  - id: public-product-entry
     type: document
     area: Product
     source:
@@ -76,8 +81,24 @@ resources:
         acquisition: [playwright_cli]
         observation: [computer_use]
 
+# Compatibility prepare tree for projects that still use sources.* directly.
+# Keep this entry-level too: one platform/domain entry here may fan out into
+# many draft candidates under evidence before selected children are promoted.
+sources:
+  prepare:
+    product:
+      product-requirements-entry:
+        type: prd
+        adapter: confluence
+        origin:
+          kind: confluence
+          url: https://confluence.example.com/pages/viewpage.action?pageId=12345
+        metadata:
+          provider: product_requirements_entry
+          promotionPolicy: review config-draft.yaml before adding child pages
+
 routes:
-  - from: my-bugs
+  - from: assigned-bugs-entry
     to:
       module: permission
       artifact: issues

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

@@ -0,0 +1,75 @@
+# ZSK work management policy.
+#
+# This file maps provider-agnostic ZSK Work Events to external work systems.
+# Multica is the default adapter reference, but .zsk/work.jsonl remains generic
+# and can be translated to Jira, GitHub Issues, GitLab, Linear, or local Markdown.
+
+version: 1
+
+ledger:
+  path: .zsk/work.jsonl
+  format: jsonl
+  createWhen: first-work-event
+  providerAgnostic: true
+
+defaultProvider: multica
+
+providers:
+  multica:
+    adapter: multica
+    mode: dry-run-until-explicit-sync
+    workspace: "<workspace-slug>"
+    # Optional generic expert catalog exported or normalized from the provider.
+    # Dispatch also auto-discovers .zsk/providers/<provider>/experts.yaml when
+    # `zsk work import-experts` creates it.
+    # Prefer `.zsk/team.yaml providerCatalogs` when the catalog is part of the
+    # local talent-pool contract.
+    # expertCatalog:
+    #   path: .zsk/providers/multica/experts.yaml
+    commandPlan:
+      executable: multica
+      mode: dry-run-template
+    projectMapping:
+      strategy: module-to-project
+      projects: {}
+    statusMapping:
+      draft: backlog
+      ready: todo
+      implementing: in_progress
+      review: in_review
+      verified: done
+      blocked: blocked
+      cancelled: cancelled
+    assignment:
+      taskCreatesIssuesOnly: true
+      dispatchAssignsAgentsOrSquads: true
+      verifyControlsDone: true
+
+events:
+  accepted:
+    - work.item.upserted
+    - work.item.linked
+    - work.item.status_changed
+    - work.provider_status.imported
+    - work.assignment.requested
+    - work.assignment.accepted
+    - work.comment.added
+    - work.item.verified
+    - work.item.blocked
+
+syncPolicy:
+  idempotency:
+    localKey: workItem.id
+    remoteRefPath: externalRefs
+  dryRunFirst: true
+  createRemoteWhen:
+    - provider is configured
+    - work item has project, module, stage, local id, title, status, and source artifacts
+  updateRemoteWhen:
+    - local work item has an existing remote reference
+    - status, source links, assignment, comments, or evidence changed
+  neverSync:
+    - secrets
+    - raw credential values
+    - provider cookies
+    - private auth state paths

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

@@ -1,15 +0,0 @@
-# Shared Evidence
-
-Use this directory for shared evidence and reports that are not owned by a single
-module.
-
-`zsk prepare sync` writes human-readable preparation reports here, such as:
-
-```text
-.zsk/evidence/prepare/sync-report.md
-.zsk/evidence/prepare/blocked-resources.md
-```
-
-Runtime state, temporary files, traces, videos, and raw provider payloads must
-stay out of committed evidence unless a workflow explicitly promotes a redacted
-artifact.

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

@@ -1,10 +0,0 @@
-# Global Issues
-
-Use this directory for global or cross-module issues:
-
-- missing provider credentials;
-- blocked resource preparation;
-- route conflicts across multiple modules;
-- architecture or governance blockers that are not owned by one module.
-
-Module-specific work belongs in `.zsk/modules/<module>/_issues/**`.

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

@@ -1,13 +0,0 @@
-# Module Template
-
-Copy this template through `zsk module init`; do not create real module
-directories by hand unless the same file contract is preserved.
-
-Required files:
-
-- `module.yaml`
-- `README.md`
-- `proposal.md`
-- `spec.md`
-- `design.md`
-- `tasks.md`

package/templates/project-init/.zsk/templates/module/design.md

@@ -1,22 +0,0 @@
-# Design
-
-## Output Quality Check
-
-status: NEEDS_CLARIFICATION
-owner: design
-source_basis: []
-blocking_items:
-  - Map approved behavior to implementation surfaces.
-next_action: Resolve Interface, data flow, rollout, and verification gaps.
-
-## Module
-
-## Interfaces
-
-## Implementation
-
-## Data Flow
-
-## Risks
-
-## Verification

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

@@ -1,15 +0,0 @@
-# yaml-language-server: $schema=__ZSK_MODULE_SCHEMA_URL__
-
-module:
-  id: "<module-id>"
-  name: "<Module Name>"
-
-outputs:
-  docs: .zsk/modules/<module-id>
-  issues: .zsk/modules/<module-id>/_issues
-
-tests:
-  raw_cases: []
-  derived_cases: []
-  automated:
-    e2e: []

package/templates/project-init/.zsk/templates/module/proposal.md

@@ -1,20 +0,0 @@
-# Proposal
-
-## Output Quality Check
-
-status: NEEDS_CLARIFICATION
-owner: proposal
-source_basis: []
-blocking_items:
-  - Fill the proposal from reviewed sources.
-next_action: Record scope, non-goals, success criteria, and open questions.
-
-## Problem
-
-## Scope
-
-## Non-Goals
-
-## Success Criteria
-
-## Open Questions

package/templates/project-init/.zsk/templates/module/spec.md

@@ -1,22 +0,0 @@
-# Spec
-
-## Output Quality Check
-
-status: NEEDS_CLARIFICATION
-owner: spec
-source_basis: []
-blocking_items:
-  - Fill observable behavior and acceptance criteria from reviewed sources.
-next_action: Resolve missing behavior questions before design.
-
-## Functional Requirements
-
-## Non-Functional Requirements
-
-## Acceptance Criteria
-
-## Scenarios
-
-## Edge Cases
-
-## Open Questions

package/templates/project-init/.zsk/templates/module/tasks.md

@@ -1,16 +0,0 @@
-# Tasks
-
-## Output Quality Check
-
-status: NEEDS_CLARIFICATION
-owner: task
-source_basis: []
-blocking_items:
-  - Convert design into executable tasks.
-next_action: Add ordered tasks with dependencies, owners, and evidence hooks.
-
-## Task Queue
-
-- [ ] Define the first implementation task.
-
-## Evidence Hooks