sdtk-ops-kit 0.2.6 → 0.2.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -5,7 +5,7 @@
5
5
  ## Package
6
6
 
7
7
  - Package: `sdtk-ops-kit`
8
- - Version in this source snapshot: `0.2.4`
8
+ - Version in this source snapshot: `0.2.9`
9
9
  - CLI: `sdtk-ops`
10
10
  - Latest published version lookup: `npm view sdtk-ops-kit version`
11
11
 
@@ -1,12 +1,12 @@
1
1
  {
2
- "version": "0.2.6",
3
- "sourceCommit": "c47349426d5c0a3cf63e5bb5e6a5e02c7c64b86c",
2
+ "version": "0.2.9",
3
+ "sourceCommit": "12c007b7b4588c7cf1bf13a34ebee83bb9d2e40b",
4
4
  "fileCount": 36,
5
5
  "files": [
6
6
  {
7
7
  "path": "toolkit/AGENTS.md",
8
- "sha256": "0871c6d46c64a093fc5f9d06af373db8143943cd27f144957dad0cc86893dc62",
9
- "size": 15069
8
+ "sha256": "5c76955ecabfae64759c11a3ee0fa777b1e0c0f78bdd177ae8f04340cd572e4b",
9
+ "size": 16469
10
10
  },
11
11
  {
12
12
  "path": "toolkit/install.ps1",
@@ -35,13 +35,13 @@
35
35
  },
36
36
  {
37
37
  "path": "toolkit/sdtk-spec.config.json",
38
- "sha256": "ce760f639a09913b236be6dde6c692ea19ee92eb1d9e63d10dcdeb398e7ed2fb",
39
- "size": 1209
38
+ "sha256": "712382d838a18b6cc6a5285b3c536fac74138c752a3fa1fd318828b19ece6b8f",
39
+ "size": 1231
40
40
  },
41
41
  {
42
42
  "path": "toolkit/sdtk-spec.config.profiles.example.json",
43
- "sha256": "e04ea5e3f72510e569ab849ebef3dea4a8728c2996c485e997d3e13a6c4f1f86",
44
- "size": 1495
43
+ "sha256": "2a306c1609499fb4910b86d5ec6e8c796e0cdf72c5f97fe3df9c1388ac62b913",
44
+ "size": 2134
45
45
  },
46
46
  {
47
47
  "path": "toolkit/SDTKOPS_TOOLKIT.md",
@@ -1,11 +1,11 @@
1
- 0871c6d46c64a093fc5f9d06af373db8143943cd27f144957dad0cc86893dc62 toolkit/AGENTS.md
1
+ 5c76955ecabfae64759c11a3ee0fa777b1e0c0f78bdd177ae8f04340cd572e4b toolkit/AGENTS.md
2
2
  e79e1ab404abf83a4f90838a2f6450c387ada7e65b137a18f70f0cab74fc14f0 toolkit/install.ps1
3
3
  5eae77f4d14b81d56c3c109f563fefafd1967d85093ff1b192293fe438aeabe5 toolkit/scripts/install-claude-skills.ps1
4
4
  68eb662bc9b8906882d32f6cd1247238f6ae663137a489f18054a75724cd1e81 toolkit/scripts/install-codex-skills.ps1
5
5
  2c629d8316b205c6a7cd0d95959b80801b281ef62e205c10a92e3a2568eb8b41 toolkit/scripts/uninstall-claude-skills.ps1
6
6
  fdb9631a80ecfb0d986a52a2833e88bf15c5303ab654d35bad6d64cca43046e8 toolkit/scripts/uninstall-codex-skills.ps1
7
- ce760f639a09913b236be6dde6c692ea19ee92eb1d9e63d10dcdeb398e7ed2fb toolkit/sdtk-spec.config.json
8
- e04ea5e3f72510e569ab849ebef3dea4a8728c2996c485e997d3e13a6c4f1f86 toolkit/sdtk-spec.config.profiles.example.json
7
+ 712382d838a18b6cc6a5285b3c536fac74138c752a3fa1fd318828b19ece6b8f toolkit/sdtk-spec.config.json
8
+ 2a306c1609499fb4910b86d5ec6e8c796e0cdf72c5f97fe3df9c1388ac62b913 toolkit/sdtk-spec.config.profiles.example.json
9
9
  58cfc74a11b8a0a18d0113a12e0e0b7a1188b253f7d19ff259d551914a831c4e toolkit/SDTKOPS_TOOLKIT.md
10
10
  1cd81e12cebdb2be528803e2d8afe43959aab1493e55499af529b99ec566a56c toolkit/skills/ops-backup/references/backup-script-patterns.md
11
11
  76e8385190d967bf98b3cafbbf8925d9b9c656ee7a7ed66ff51285b6459ebff1 toolkit/skills/ops-backup/SKILL.md
@@ -1,5 +1,10 @@
1
1
  # SDTK Orchestrator Routing Contract
2
2
 
3
+ Version: 2.0
4
+ Last Updated: 2026-07-14
5
+
6
+ This file is the single source of the SDTK routing contract. `CLAUDE.md` and `CODEX.md` are thin runtime adapters that defer to it; when they appear to disagree with this file, this file wins.
7
+
3
8
  Goal: use the SDTK Suite as a coordinated operating model:
4
9
  - `SDTK-SPEC` governs upstream discovery, planning, design, traceability, and release gates.
5
10
  - `SDTK-CODE` is the default downstream system for implementation, bug fixing, refactoring, verification, and ship-ready code changes.
@@ -19,16 +24,21 @@ Orchestrator Intake is the always-winning front door for every unprefixed reques
19
24
  - Read stack and command configuration from `sdtk-spec.config.json` in the project root.
20
25
  - For VI/JP source requirements, keep original text in an appendix and add literal English translation for traceability.
21
26
  - `/dev` stops at `FEATURE_IMPL_PLAN + CODE_HANDOFF`; SDTK-CODE is the default downstream coding system.
22
- - Verification-before-completion: no phase may declare done, pass, or handoff-ready without fresh command evidence per `governance/ai/core/SDTK_VERIFICATION_BEFORE_COMPLETION_POLICY.md`.
27
+ - Verification-before-completion: no phase may declare done, pass, or handoff-ready without fresh command evidence — run the relevant verification commands in this session and quote their real output in the phase artifact; assumed, remembered, or stale results do not count.
23
28
  - `toolkit/skills/skills.catalog.yaml` is the inventory source of truth for the 14 core SDTK-SPEC skills, including the bounded `mailbox-dispatch` controller skill.
24
29
 
25
30
  ## 2) Session Bootstrap Protocol
26
31
  When starting a new session, read context in this order when the files exist:
27
32
  1. `AGENTS.md`
28
- 2. `governance/ai/session/SDTK_ACTIVE_BOOTSTRAP.md`
29
- 3. `governance/ai/session/SDTK_AGENT_WORKING_RULES.md`
30
- 4. `governance/ai/core/IMPROVEMENT_BACKLOG.md`
31
- 5. issue-specific controller spec and implementation plan
33
+ 2. `.sdtk/evolve/LEARNED.md` — locally learned, owner-approved lessons (managed by the evolve skill + `sdtk evolve`; never edit it directly)
34
+ 3. `governance/ai/session/SDTK_ACTIVE_BOOTSTRAP.md`
35
+ 4. `governance/ai/session/SDTK_AGENT_WORKING_RULES.md`
36
+ 5. `governance/ai/core/IMPROVEMENT_BACKLOG.md`
37
+ 6. issue-specific controller spec and implementation plan
38
+
39
+ Orientation and health:
40
+ - If `.sdtk/wiki/` exists, it is the project's committed memory layer: orient with `sdtk-wiki search "<topic>"` (entry points: `.sdtk/wiki/pages/_index.md`, the atlas summary) before falling back to repo-wide searching.
41
+ - If any `sdtk-*` CLI behaves unexpectedly (missing verbs, stale help, wrong version), run `sdtk doctor` to detect version fragmentation before debugging further.
32
42
 
33
43
  Do not read the entire historical session archive by default. Use `SDTK_SESSION_MEMORY_*.md` only when chronology or past acceptance details are required.
34
44
 
@@ -60,9 +70,11 @@ Use this compact matrix during intake so the agent picks the smallest sufficient
60
70
  | Formal feature delivery | `SDTK-SPEC` pipeline | PM -> BA -> ARCH -> DEV planning -> CODE handoff -> QA |
61
71
  | Build, fix, or refactor implementation | `SDTK-CODE` | code-brainstorm (when slice is ambiguous) -> start -> plan -> build -> verify -> ship |
62
72
  | Debug failure or unexpected behavior | `SDTK-CODE` debug | Root cause, bounded fix, regression verification |
73
+ | Screen/layout design, visual tokens, or prototype evidence before coding | `SDTK-DESIGN` | Reviewable screens/prototype plus a design handoff into SDTK-CODE |
63
74
  | Deployment, release, infra, or CI/CD work | `SDTK-OPS` | ops-plan -> ops-deploy/ops-incident/ops-monitor -> ops-verify |
64
75
  | Code review or spec review | Review / QA workflow | Findings, risks, blockers, acceptance signal |
65
76
  | Atlas graph build or viewer work | `sdtk-spec atlas` compatibility workflow or `sdtk-wiki atlas` for canonical SDTK-WIKI work | Local `.sdtk/atlas` compatibility graph or `.sdtk/wiki` SDTK-WIKI result |
77
+ | Question about existing project knowledge or docs | `sdtk-wiki search` (free) or `sdtk-wiki ask` when available | Grounded answer citing project pages before any repo-wide scan |
66
78
  | SDTK-WIKI Ask | `sdtk-wiki ask` | Grounded answer when `.sdtk/wiki/graph` plus `wiki.ask` entitlement/runtime preconditions are present, otherwise explicit blocker |
67
79
  | Existing project scan: project ingest, project refresh, or project audit | Matching premium project workflow | Project-local foundation, refresh, or audit result without overclaiming entitlement |
68
80
  | Multi-step durable workflow: 3+ dependent steps, human gates between steps, must survive a pause, or spans multiple lanes/sessions | Propose `sdtk-agent` orchestration (opt-in, token-aware, see the orchestration cost gate in section 5) | `.sdtk/agent-runtime/runs/<run_id>/` ledger plus `reports/final_report.md` |
@@ -165,7 +177,7 @@ Cross-cutting capabilities (not a linear lane; usable across every phase):
165
177
  - surface: `sdtk-agent run start|continue|status|report`, `gate approve|reject`, `workflow validate`, `adapter hermes-kanban plan`
166
178
  - use only when a workflow has 3+ dependent steps, needs human gates between steps, or must survive a pause; otherwise route straight to a lane
167
179
  - opt-in and token-aware: always propose-then-confirm before dispatch (see the orchestration cost gate in section 5)
168
- - the CLI is runtime-neutral and installs no skills; the engine is Free, and live external dispatch is not part of this release (hermes-kanban is dry-run only)
180
+ - the CLI is runtime-neutral and installs no skills; the engine is Free; the hermes-kanban adapter defaults to dry-run and live dispatch stays fail-closed behind explicit configuration plus per-run confirmation
169
181
 
170
182
  If the current project only has `SDTK-SPEC` runtime assets installed:
171
183
  - keep `/dev` bounded to planning and `CODE_HANDOFF`
@@ -186,7 +198,7 @@ If the current project only has `SDTK-SPEC` runtime assets installed:
186
198
  - For Codex runtimes: project-local skills require the explicit local `CODEX_HOME=<project>/.codex` contract; native `.codex/skills` auto-discovery is not claimed.
187
199
  - Use `ops-parallel` or `code-parallel` only for truly independent slices. If parallel dispatch is unavailable in the active runtime, execute them sequentially in one controller session.
188
200
  - `SDTK-AGENT` is runtime-neutral: it installs no skills and behaves identically on Claude and Codex. It is CLI-only, so do not invent a slash command for it.
189
- - The `sdtk-agent` hermes-kanban adapter is dry-run only in this release; it never calls a live gateway or creates a real card. Live dispatch is a future Pro capability, so do not claim it.
201
+ - The `sdtk-agent` hermes-kanban adapter defaults to dry-run. Live dispatch exists but is fail-closed behind explicit adapter configuration (`mode: live` plus `live_ack`) and a per-run `--confirm`, and it remains an attended, validation-gated capability. Never claim, enable, or attempt live dispatch on the user's behalf.
190
202
 
191
203
  ## 11) Discovery And PM Readiness
192
204
  - PM initiation starts only after `docs/discovery/REQUIREMENT_[FEATURE_KEY].md` is marked `READY_FOR_PM_INITIATION`.
@@ -1,7 +1,8 @@
1
1
  {
2
+ "schemaVersion": 1,
2
3
  "docs": {
3
4
  "artifactsLanguage": "EN",
4
- "guidanceLanguage": "VI",
5
+ "guidanceLanguage": "EN",
5
6
  "preserveOriginalInput": true,
6
7
  "appendixIncludeEnglishTranslation": true,
7
8
  "aiPeerReviewAllowed": true
@@ -1,5 +1,26 @@
1
1
  {
2
2
  "profiles": {
3
+ "php-laravel": {
4
+ "orchestration": {
5
+ "apiDesignDetailMode": "auto",
6
+ "testCaseSpecMode": "auto"
7
+ },
8
+ "stack": {
9
+ "backend": "PHP 8.3 + Laravel 11",
10
+ "frontend": "Blade + Vite (or Livewire)",
11
+ "mobile": "N/A",
12
+ "database": "MySQL 8",
13
+ "auth": "Laravel Sanctum"
14
+ },
15
+ "commands": {
16
+ "backendTests": "php artisan test",
17
+ "backendTypecheck": "vendor/bin/phpstan analyse",
18
+ "backendLint": "vendor/bin/pint --test",
19
+ "frontendTests": "npm run test",
20
+ "frontendLint": "npm run lint",
21
+ "e2eTests": "npm run e2e"
22
+ }
23
+ },
3
24
  "django-react": {
4
25
  "orchestration": {
5
26
  "apiDesignDetailMode": "auto",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sdtk-ops-kit",
3
- "version": "0.2.6",
3
+ "version": "0.2.9",
4
4
  "description": "Skill-driven operations toolkit for deployment, verification, monitoring, incident response, backup, security, compliance, and cost discipline.",
5
5
  "bin": {
6
6
  "sdtk-ops": "bin/sdtk-ops.js"