pakem-cli 0.0.0-stage → 1.2.1

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.
Files changed (76) hide show
  1. package/CHANGELOG.md +271 -0
  2. package/LICENSE +21 -0
  3. package/README-ID.md +665 -0
  4. package/README.md +664 -2
  5. package/SKILL.md +264 -0
  6. package/adapters/git-worktree/v1/README.md +17 -0
  7. package/adapters/identity/v1/README.md +26 -0
  8. package/adapters/mcp/v1/README.md +56 -0
  9. package/adapters/storage-sqlite/v1/README.md +5 -0
  10. package/assets/banner.svg +275 -0
  11. package/assets/divider.svg +82 -0
  12. package/assets/footer.svg +174 -0
  13. package/assets/templates/BUG-HISTORY.md +18 -0
  14. package/assets/templates/CONTEXT.md +26 -0
  15. package/assets/templates/DECISIONS.md +8 -0
  16. package/assets/templates/MODULE-MAP.md +14 -0
  17. package/assets/templates/POLICY.json +15 -0
  18. package/assets/templates/PROJECT.md +42 -0
  19. package/conformance/v1/README.md +15 -0
  20. package/coordination/v1/README.md +14 -0
  21. package/coordination/v1/board.schema.json +59 -0
  22. package/coordination/v1/event.schema.json +26 -0
  23. package/coordination/v1/status.schema.json +49 -0
  24. package/evals/README.md +63 -0
  25. package/evals/evals.json +276 -0
  26. package/identity/v1/README.md +14 -0
  27. package/identity/v1/agent-identity.schema.json +95 -0
  28. package/identity/v1/identity-registry.schema.json +29 -0
  29. package/identity/v1/signed-payload.schema.json +42 -0
  30. package/intelligence/v1/README.md +19 -0
  31. package/intelligence/v1/dependency-graph.schema.json +82 -0
  32. package/intelligence/v1/impact-analysis.schema.json +51 -0
  33. package/intelligence/v1/reconciliation.schema.json +156 -0
  34. package/npm/bin/pakem.js +150 -0
  35. package/npm/check-version.js +26 -0
  36. package/package.json +55 -4
  37. package/policy/v1/README.md +15 -0
  38. package/policy/v1/policy.schema.json +20 -0
  39. package/protocol/v1/README.md +68 -0
  40. package/protocol/v1/capabilities.schema.json +17 -0
  41. package/protocol/v1/event.schema.json +114 -0
  42. package/protocol/v1/session.schema.json +51 -0
  43. package/references/artifacts.md +96 -0
  44. package/references/conventions.md +83 -0
  45. package/references/reviews.md +44 -0
  46. package/runtime/v1/README.md +21 -0
  47. package/runtime/v1/approval.schema.json +100 -0
  48. package/runtime/v1/checkpoint.schema.json +17 -0
  49. package/runtime/v1/hook-decision.schema.json +34 -0
  50. package/runtime/v1/hook-payload.schema.json +12 -0
  51. package/runtime/v1/task-evidence.schema.json +38 -0
  52. package/runtime/v1/work-report.schema.json +123 -0
  53. package/runtime/v1/workflow.schema.json +21 -0
  54. package/scripts/__pycache__/pakem.cpython-312.pyc +0 -0
  55. package/scripts/pakem.py +4911 -0
  56. package/scripts/pakem_core/__init__.py +3 -0
  57. package/scripts/pakem_core/__pycache__/__init__.cpython-312.pyc +0 -0
  58. package/scripts/pakem_core/__pycache__/coordination.cpython-312.pyc +0 -0
  59. package/scripts/pakem_core/__pycache__/git_worktree.cpython-312.pyc +0 -0
  60. package/scripts/pakem_core/__pycache__/identity.cpython-312.pyc +0 -0
  61. package/scripts/pakem_core/__pycache__/intelligence.cpython-312.pyc +0 -0
  62. package/scripts/pakem_core/__pycache__/mcp_server.cpython-312.pyc +0 -0
  63. package/scripts/pakem_core/__pycache__/protocol.cpython-312.pyc +0 -0
  64. package/scripts/pakem_core/__pycache__/reconcile.cpython-312.pyc +0 -0
  65. package/scripts/pakem_core/__pycache__/runtime.cpython-312.pyc +0 -0
  66. package/scripts/pakem_core/coordination.py +977 -0
  67. package/scripts/pakem_core/git_worktree.py +265 -0
  68. package/scripts/pakem_core/identity.py +494 -0
  69. package/scripts/pakem_core/intelligence.py +684 -0
  70. package/scripts/pakem_core/mcp_server.py +308 -0
  71. package/scripts/pakem_core/protocol.py +61 -0
  72. package/scripts/pakem_core/reconcile.py +119 -0
  73. package/scripts/pakem_core/runtime.py +457 -0
  74. package/scripts/run_evals.py +289 -0
  75. package/storage/v1/README.md +14 -0
  76. package/storage/v1/team-storage.schema.json +27 -0
package/CHANGELOG.md ADDED
@@ -0,0 +1,271 @@
1
+ ## 1.2.1 — 2026-11-17
2
+
3
+ ### Added
4
+ - `npx pakem` installer (npm package `pakem`): copies the skill into `~/.claude/skills/pakem` (or `--project` for `./.claude/skills/pakem`, or `--dir` for another skills folder), then delegates any other argument to the bundled Python CLI (`npx pakem init --type app`). The package ships `SKILL.md`, scripts, schemas, references, and assets; it adds no npm dependency to the target project. `npm pack` refuses to build when `package.json` and `scripts/pakem.py` versions differ, and `tests/test_docs.py` guards the same invariant.
5
+
6
+ ### Fixed
7
+ - Gate `scope` compared only the working tree (`git diff HEAD`), so an agent that committed its work and then ran `check`/`finish` passed without ever being compared against plan scope. The gate now anchors on the HEAD recorded when the session started (`.pakem/sessions/*.json` → `git.head`) and diffs that commit against the working tree in one pass: commits made during the session, uncommitted edits, and untracked files all count. Without an active session it falls back to `git diff HEAD`, so CI on a clean checkout still needs an explicit base to mean anything.
8
+ - `reconcile`/`impact --base REF` used `REF...HEAD`, which lists commits only and hides everything uncommitted. It now runs `git diff REF` (working tree against REF) and adds untracked files, so the manual report and gate `scope` agree.
9
+ - Deleted files never appeared: `_git_changed_files` passed `--diff-filter=ACMR`, which drops `D`. A task could delete an out-of-scope module and the report said the change set was aligned. The filter is gone; a deletion is a code change like any other.
10
+ - `NEEDS_JSONSCHEMA` guarded only `jsonschema`, while `tests/test_release_110.py` also imports `referencing`. A machine with jsonschema below 4.18 errored instead of skipping. The guard checks both and the skip message names `pip install -r requirements-dev.txt`; `requirements-dev.txt` already pins `jsonschema>=4.20`, which pulls `referencing`.
11
+ - `SKILL.md` gate table and `README.md` now state the anchor for gate `scope`, so "code outside scope fails" is not read as working-tree-only.
12
+
13
+ ### Changed
14
+ - Generated project documents are English: `PROJECT.md`, `CONTEXT.md`, `MODULE-MAP.md`, `DECISIONS.md`, `BUG-HISTORY.md`, `SPEC.md`, ADRs, `HANDOVER.md`, `PLAN.md`, and the protocol block installed into `CONTEXT.md` and adapters. Placeholders are now `[FILL: ...]`; gate `placeholder` still detects legacy `[ISI`, so projects initialized earlier keep failing until filled. New projects get the English templates; existing documents are not rewritten. `pakem upgrade`/`pakem adapt` rewrites the protocol block, and `doctor` reports an old block as stale until then.
15
+ - Legacy documents keep working after that switch: `pakem bug` recognizes `## Entri` and `_Belum ada bug tercatat._`, so a new entry still lands on top and the old empty marker is replaced; `pakem adr` likewise replaces `_Belum ada keputusan tercatat._` instead of leaving it above the index.
16
+ - CLI output is English. Status prefixes (`[PASS]`, `[FAIL]`, `[SKIP]`, `[WARN]`), gate names, flags, event names, schema ids, and JSON keys are unchanged, but prose and several labels moved: `[BUKTI]` → `[EVIDENCE]`, `HASIL:` → `RESULT:`, `PERIKSA` → `CHECK`, `REKONSILIASI` → `RECONCILIATION`, audit tiers `wajib`/`disarankan`/`tidak` → `required`/`recommended`/`not-needed`, `[WARN] aturan-berubah` → `[WARN] rules-changed`, `[WARN] wajib`/`risiko` → `[WARN] required`/`risk`. `audit --json` rows use the new tier values (the legacy `wajib_gap`/`disarankan_gap`/`tidak_perlu` summary keys are kept so existing readers do not break). Anything grepping the old prose must be updated; the bracketed prefixes and `pakem.*` identifiers are stable.
17
+ - Counted nouns are pluralized (`1 task`, `2 tasks`, `1 new commit`) in the plan, task-verify, report, handover, and resume output instead of printing `1 tasks`.
18
+
19
+ ### Documented
20
+ - Documentation is English-first: `README.md` and `SKILL.md` are English, the Indonesian README is preserved as `README-ID.md` and linked from both, and `references/`, `adapters/`, `protocol/v1/README.md`, `evals/README.md`, and schema descriptions are English. CLI output and `evals/evals.json` are English too; the Indonesian README keeps Indonesian prose, but its command blocks and quoted output match the English CLI.
21
+ - Source docstrings and code comments are English too (63 docstrings, 27 comment lines across `scripts/pakem.py` and `pakem_core/*`). The pass changes documentation only: executable strings, identifiers, schema ids, event names, flags, and control flow are untouched. Legacy sentinels (`## Entri`, `[ISI`, `_Belum ada bug tercatat._`, `_Belum ada keputusan tercatat._`) remain where the compatibility code expects them.
22
+ - `README.md` is now a designed front page (banner, badges, arc-style table of contents, dividers, footer), and `README-ID.md` mirrors the same shell with Indonesian text. Both keep byte-identical command blocks. `tests/test_docs.py` checks that every ToC anchor resolves in both files, that heading outlines stay parallel, and that local `<img>` assets exist.
23
+ - `tests/test_docs.py` keeps the README pair honest: identical fenced blocks (a CLI change must land in both), links both ways, and a `SKILL.md` description that stays under the 57-character index budget with the trigger word intact.
24
+
25
+ ### Validation
26
+ - 223 tests, all passing in one uninterrupted run with `requirements-dev.txt` installed in a clean venv (jsonschema 4.26, referencing, cryptography). Without optional dependencies the two URN-resolution tests skip instead of erroring.
27
+ - Four new regression tests in `tests/test_release_120.py`: committed out-of-scope code fails the gate, committed in-scope code passes, a deleted out-of-scope file is counted, and an untracked new file fails the gate. Before the fix, the committed case printed `[PASS] scope: tidak ada perubahan tertunda` and the deletion was absent from `changed_files`.
28
+ - Two legacy-document tests in `tests/test_pakem.py`: a pre-1.2.1 `BUG-HISTORY.md` with `## Entri` still receives a new entry on top without the stale empty marker, and a legacy `DECISIONS.md` placeholder is replaced by the ADR index entry.
29
+
30
+ ## 1.2.0 — 2026-11-10
31
+
32
+ ### Added
33
+ - `pakem reconcile [--base REF] [--staged] [--json] [--strict]` and `intelligence/v1/reconciliation.schema.json` (`urn:pakem:intelligence:v1:reconciliation`). The release ledger had nine features that each knew their own artifact — plan tasks declared `--files`, worktrees produced diffs, specs declared acceptance, tests produced results — and nothing compared them. `reconcile` puts Git changes, plan scope, and acceptance in one report. The comparison itself is a pure function in `pakem_core/reconcile.py`: no disk access, no subprocess, so it is testable without a repository.
34
+ - Gate `scope`. Code changed outside every plan task's `--files` fails `check` and `finish`, with the offending paths named and the remedy spelled out (`plan add ... --files ...`). Non-code files (docs, config, lockfiles) are reported in the gate line but do not fail: widening scope for a README is not the same failure as silently editing an unrelated module. Scope entries accept an exact path, a directory, or a glob.
35
+ - Gate `acceptance`, evaluated only by `finish`. `spec --approve` proves the plan; only checked boxes prove the result. It runs at `finish` and not at `check` because approval necessarily happens before the work that fills those boxes — failing a mid-work `check` on them would be noise, not a signal.
36
+ - Gate `handover` is `WARN` during `check` and `FAIL` during `finish`. A handover that lags one commit behind is normal in an active repository; making `check` red for it trains agents to ignore gates. Gates may now also return `warn`, which is reported but does not fail the run.
37
+ - `pakem handover` now stamps the document with the HEAD it was written against (`<!-- pakem:handover head=… at=… -->`). `handover --check` exits 1 when HEAD moved, and gate `handover` (check + finish) fails the same way, because a filled-in handover describing an older tree misleads whoever receives it. `handover --stamp` re-stamps after the text is updated; `handover=true` without the file also fails.
38
+ - `plan done <id>` now removes the task's worktree when it is clean and its commits are already part of HEAD, printing `[WT ] … dihapus`. Worktrees with unmerged commits or uncommitted files are left alone with `[WARN] … dibiarkan: <reason>` — unmerged work is not garbage. `worktree cleanup [task] [--dry-run]` does the same sweep on demand.
39
+ - `pakem ci` now also runs `doctor`, `audit --strict`, and `events --verify` after `check`, so CI catches a broken installation, WAJIB artifact gaps, and a rewritten ledger rather than only failing tests.
40
+ - MCP gains `pakem.session.start`, `pakem.session.step`, and `pakem.session.finish`, all behind `--allow-write` + bound `--agent-id`. They call the project's own CLI, so events are recorded, task verify runs, and a failing `finish` returns `ok: false` with the gate lines instead of raising.
41
+ - `pakem start` now pins a manifest of `pakem.py` and every `pakem_core/*.py`, not just the CLI hash. Gates live in Core too, and editing one module there used to leave no trace at all. `pakem integrity` compares the manifest with the current tree, reports changed/missing/added files, and exits 1 on drift; `--re-pin --reason "..."` is the only way to accept a change and it records an `integrity.repinned` event. `check` reports drift as `[WARN] aturan-berubah`, `finish --strict` fails on it. `doctor`, when run from the skill installation, compares the project's Core against the skill's own files.
42
+ - Private signing keys can live outside the host config: `identity create --key-out PATH`, `events --sign --key PATH` (or `PAKEM_SEAL_KEY`), and PEM PKCS8 as well as Pakem's 32 raw bytes. Verification only needs the public key, so `identity import <id> --public-key ...` registers an identity on a machine that will never hold the private half. `events --sign` warns when the key path points inside the repository, because a key stored next to the ledger proves nothing.
43
+ - `pakem report [--json] [--session ID] [--limit N]` prints a work roll-up from artifacts that already exist: sessions (wall-clock duration, steps, events, gate failures, status), every task in `PLAN.md` with its verify outcome and the files whose hashes were recorded, and ledger health with the chain head. `totals.unproven_done` counts `[x]` tasks with no valid evidence — the same ones gate `task-verify` will refuse. Exit code 1 when the ledger chain is broken, so CI can gate on it.
44
+ - Report times are session wall clock, not agent compute time. Pakem does not measure the latter and the report says so rather than estimating. Sessions still open are counted up to `generated_at`.
45
+ - `runtime/v1/work-report.schema.json` (`urn:pakem:runtime:v1:work-report`) pins the JSON shape; `--session` filters the session list only, and the text output says so instead of implying per-session tasks.
46
+ - Event ledger entries are hash-chained: every new event carries `integrity: {prev, hash}`, where `hash` covers the event body plus the previous event's hash. `pakem events --verify` recomputes the chain and reports the exact line that fails. Editing an event breaks its own hash; deleting one in the middle breaks the next event's `prev`. Events written before 1.2.0 have no chain fields and are reported as `pra-rantai` rather than as corruption — the chain simply restarts after them.
47
+ - `pakem events --sign --identity <id>` appends a `ledger.sealed` event carrying an Ed25519 envelope over `{ledger, chain_head, event_count, sealed_at}`. `events --verify` checks the signature, the identity's revocation state, and that the chain before the seal still equals the signed head — so an attacker who rewrites the whole chain and recomputes every hash is caught by the seal, not by the chain.
48
+ - Gate `ledger` (check + finish) verifies the chain and prints `head=<hash>`. That head is the anchor: record it in CI output or a ticket and `events --verify --expect-head <hash>` later proves the ledger was not rewritten. Truncating the last events is only detectable with such an anchor — a chain cannot see its own end.
49
+ - Protocol: `integrity` is a reserved, optional envelope field (capability `events.integrity.v1`) and `ledger.sealed` is a new event type. `protocol/v1/README.md` records this as the one additive exception to the otherwise strict v1 envelope; older ledgers stay valid.
50
+ - `plan done <id>` now runs the task's own `--verify` command and records the result in `.pakem/verify/tasks.json` (`runtime/v1/task-evidence.schema.json`): exit code, output hash, duration, and a digest of every file in the task's `--files` scope. A failing verify leaves the task open. Before this, a task was "done" because a box was ticked, while the `--verify` command sat in PLAN.md unused — the only proof was a global check at the end.
51
+ - Gate `task-verify`: every `[x]` task needs passing evidence, and the evidence must not be stale (any scope file changed afterwards invalidates it). `plan done` on an already-finished task re-runs verify to refresh. Waivers are allowed but explicit — `--no-verify --reason "..."` — and the gate always names them, so a shortcut is visible in the output instead of silent.
52
+ - `plan done` runs the verify command outside the session lock. `flock` is not reentrant: a verify command that itself calls pakem (e.g. `pakem check`) would otherwise wait on a lock its own parent holds, until the timeout.
53
+ - `graph` reads `paths` and `baseUrl` from `tsconfig.json`/`jsconfig.json`, following `extends` and ignoring JSONC comments and trailing commas. Before this, `import { u } from "@/lib/util"` was parsed as the scoped npm package `@/lib` and dropped: no edge, no warning, and `impact` would answer "no dependents" with confidence. Import specifiers that still fail are now listed in `unresolved_imports` with a reason (`relative`, `alias`, `baseUrl`) instead of disappearing; bare packages are not reported, so the list stays signal.
54
+ - `graph` reports `circular_dependencies` (strongly connected components, Tarjan, iterative) and `circular_dependency_count`. A cycle makes impact analysis transitive in both directions and usually means the "which module owns this" question is unresolved.
55
+ - `impact` gains `graph_health` (`alias_rules`, `unresolved_imports`, `circular_dependencies`, `complete`) and says so in its recommendations when the graph it used is incomplete; changed files inside a cycle are named in the risk reasons. The point is that "no dependents found" and "we could not resolve the imports" stop looking identical.
56
+ - `pakem worktree scope <name> [--json] [--strict]`: compares a managed worktree against the scope declared for the task in its name. The diff is taken from the merge-base with the root branch, so work already committed on `pakem/<task>/<agent>` is not invisible; untracked files are added from status. `git_worktree.resolve()` accepts `T1--solo`, `T1/solo`, or a path and refuses anything outside `.pakem/worktrees/`.
57
+ - Gate `worktree`, run by `check` and `finish`: every managed worktree still on disk is checked the same way. Isolation without this gate only hides the widening — the change shows up at merge time, when nobody attributes it to a task.
58
+ - Board tasks (`team add --files`) are now a scope source next to `PLAN.md`, merged per `taskId`. Before this, a team that tracked scope only on the board looked like it had declared no scope at all, and every changed file counted as out of scope.
59
+ - `team register` now binds the agent's Ed25519 fingerprint from `.pakem/identity/registry.json` (or an explicit `--fingerprint`), so the board records which key stands behind a name.
60
+ - `team submit --sign` and `team review --sign` seal the action payload (submission summary + evidence, review decision + note + implementer) with the agent's key and store the envelope on the board.
61
+ - `pakem team verify [--json]` checks three things per signed action: the signature verifies, the identity is not revoked, and the board content still matches the payload that was signed. Any invalid signature exits 1. Unsigned actions are counted separately rather than treated as failures.
62
+
63
+ ### Changed
64
+ - Running Pakem from inside a linked worktree now uses the main worktree as the project root. `.pakem` is checked out into every worktree, so a copy of the plan/board existed there while sessions, locks, and worktree bookkeeping did not; agents working in isolation were reading stale state and `worktree scope` could not find its own worktree.
65
+ - `coordination.tasks_map()` normalises the board: `status()` returns tasks as a list while every caller needed a map keyed by `taskId`, and two new call sites hit that mismatch immediately.
66
+ - `SKILL.md` gate table, `README.md` gate list and quickstart table, and the team section now describe `scope`, `acceptance`, and signed board actions.
67
+
68
+ ### Notes
69
+ - Upgrade note: tasks marked `[x]` before 1.2.0 have no evidence, so gate `task-verify` rejects them until you run `plan done <id>` once (or record a waiver). That is deliberate — the alternative is letting old ticks pass as if they had ever been verified.
70
+ - Signing makes the board tamper-evident, not authenticated: it proves a payload was not altered after sealing and that the key was not revoked at verification time. Binding a caller to `--agent` remains the host's job.
71
+ - `reconcile` is advisory on its own (`--strict` to make it exit 1); what blocks `finish` is the gate, which reads the same reconciliation.
72
+
73
+ ### Validation
74
+ - 209 tests, all passing with `requirements-dev.txt`; 61 of them are the new 1.2.0 profile (`tests/test_release_120.py`): seven worktree-scope cases, five graph-resolution cases, five task-evidence cases, seven ledger-integrity cases, six work-report cases, seven handover/worktree/CI/MCP cases, three integrity-pin cases, and four external-key cases.
75
+ - `reconcile --json` output validates against its schema; tampering with a signed submission and revoking a signer are both caught by `team verify`.
76
+ - Alias resolution, `extends` chains, JSONC comments, cycle detection, missing alias targets, and external packages each have a test; `graph` and `impact` output validate against their schemas.
77
+ - Worktree scope was exercised against uncommitted edits, committed branch work, untracked files, a rename-free diff, and a task with no declared scope; the gate fails on the first three and names the missing scope on the last.
78
+
79
+ ## 1.1.3 — 2026-11-09
80
+
81
+ ### Added
82
+ - `runtime/v1/approval.schema.json` (`urn:pakem:runtime:v1:approval`). `approvals.json` was the only runtime artifact without a contract, and it is the one hosts read to decide whether an action may run: an unannounced field rename there could let a host treat an expired approval as valid. The schema pins the envelope, every field, the category/risk enums, and the average-case cap of 500 records. Installed by `init` and `upgrade`, checked by `doctor`.
83
+ - `scripts/run_evals.py` + `evals/README.md`. `evals/evals.json` had 24 prompts and 103 assertions and no way to execute them. The runner provisions a clean sandbox per eval, feeds the prompt to `--agent-cmd` on stdin, records exit code, transcript, and written files, then hands grading to `--judge-cmd`. Assertions are natural language, so grading needs a judge; without one the runner records but does not pretend to score. A judge that silently skips assertions scores them failed instead of passing by omission.
84
+ - `EvalRunnerTests`: 5 tests covering structure validation, record-only mode, pass/fail grading, the skip-detection rule, and surfacing a broken `--agent-cmd` instead of reporting a silent zero-file run.
85
+
86
+ ### Changed
87
+ - `SKILL.md` `description` shortened from 506 to 48 characters (`Pakem: disiplin kerja agent dengan gate selesai.`). Agent skill indexes truncate around 57 characters, and the old text pushed the trigger word "pakem" out of view entirely. The removed detail now lives in a `## Kapan dipakai` section at the top of the body, where it is read when the skill actually loads.
88
+ - `worktree remove` without `--force` now raises a Pakem message ("worktree masih punya perubahan yang belum di-commit…") instead of forwarding git's raw `fatal:` line.
89
+
90
+ ### Notes
91
+ - `format: date-time` is an annotation in JSON Schema 2020-12; validating timestamps requires a format checker. Plain `required`/`enum`/`const`/`pattern` violations are enforced by every validator.
92
+
93
+ ### Validation
94
+ - 148 tests: 148 OK with `requirements-dev.txt`, 148 OK (15 skipped) without optional dependencies. Full suite uninterrupted, ~95s.
95
+ - `python3 scripts/run_evals.py --validate` reports a healthy 24-eval / 103-assertion file.
96
+
97
+ ## 1.1.2 — 2026-11-09
98
+
99
+ ### Fixed
100
+ - Schema `$id` values were split across two schemes: `urn:pakem:...` for runtime/coordination/protocol/policy/intelligence, and `https://pakem.dev/schemas/...` for identity and team storage. `pakem.dev` has no DNS record and belongs to no one, so those identifiers pointed at a domain outside the project's control. A third party registering that domain would decide what any schema-fetching validator trusts. All schema identifiers are now `urn:pakem:...` (`identity:v1:agent-identity`, `identity:v1:identity-registry`, `identity:v1:signed-payload`, `storage:v1:team-storage`).
101
+ - `identity/v1/identity-registry.schema.json` referenced `agent-identity.schema.json` relatively. That only resolved because the base was a URL; with a URN base it fails exactly like `checkpoint.schema.json` did in 1.1.1. The reference is now absolute.
102
+
103
+ ### Added
104
+ - `SchemaContractTests` guard: every `*.schema.json` in the package must carry a unique `urn:pakem:` `$id`, every non-fragment `$ref` must resolve to one of those ids, and no JSON file may point at a third-party domain. This makes the mixed-scheme regression impossible instead of merely fixed.
105
+ - Offline resolution test: a real identity registry document is validated against `identity-registry` using a registry built only from `$id` values, with no network access.
106
+
107
+ ### Notes
108
+ - Changing `$id` does not change instance validation, only how schemas are discovered, so this is a patch release. Projects upgrading from 1.1.1 receive the updated identity and storage schemas through `pakem upgrade`.
109
+ - Pakem keeps ship-with-the-package schemas as the source of truth. Validation needs no domain, no hosting, and no network.
110
+
111
+ ## 1.1.1 — 2026-11-09
112
+
113
+ ### Fixed
114
+ - `plan add --verify` dropped shell pipes. `clean_plan_field` stripped `|` from every field because it separates columns in `PLAN.md`, so `--verify "pytest -q | tail -3"` was stored as `pytest -q tail -3` with no warning. `verify` is the last column, so it now keeps pipes; newlines are still removed and task text/files are still sanitized.
115
+ - `runtime/v1/checkpoint.schema.json` referenced `workflow.schema.json` relatively while its own `$id` is a URN. Relative references cannot resolve against a URN base, so standard validators (jsonschema, ajv) failed with `Unresolvable` on the published contract. The reference is now `urn:pakem:runtime:v1:workflow`.
116
+ - The shipped test suite could not go green. `tests/test_pakem.py` asserted `VERSION = "1.0.0"` after an upgrade to the current release (red on every release after 1.0.0), and its legacy-CLI simulation replaced `VERSION = "0.8.0"`, a no-op since 0.8.0 was retired. Both now derive from the source of truth in `scripts/pakem.py`, so a version bump no longer breaks the suite.
117
+ - `tests/test_release_110.py` imported `jsonschema` unconditionally and errored instead of skipping, while `test_pakem.py` skipped the same dependency. Both modules now guard optional dependencies and say which one is missing.
118
+ - `README.md` "Batasan jujur" still claimed worktree isolation and the MCP server were not provided, contradicting 1.0.0. Corrected.
119
+
120
+ ### Changed
121
+ - `pakem audit` treats `README.md` as DISARANKAN for `type: oneoff`. `verify` that proves real output is the evidence a throwaway script needs; demanding a README contradicted "Pakem does not chase file completeness". `app`, `library`, and `research` still require it.
122
+ - Added `requirements-dev.txt` (`cryptography`, `jsonschema`) so the full suite is reproducible from the package alone.
123
+
124
+ ### Documented
125
+ - `team review` requires both a registered reviewer role (`reviewer`/`lead`/`coordinator`) and a different identity from the implementer. Only the identity rule was documented, so a board of workers could submit and then never complete a task.
126
+ - The placeholder gate also scans `HANDOVER.md` and `docs/HANDOVER.md`; the gate table said only `.pakem/*.md` and `docs/adr/*.md`.
127
+ - `--verify` per plan task is a record, not an execution. Only `PROJECT.md` `verify` runs, via `check`/`finish`.
128
+
129
+ ### Validation
130
+ - **139 tests** in one uninterrupted run: 139 OK with `requirements-dev.txt` installed, 139 OK (13 skipped) without optional dependencies. Runtime ~90s on Python 3.13.
131
+ - The 1.1.0 note about a "subprocess-test-harness hang in long combined batches" was a misdiagnosis: the combined suite completes in about 90 seconds. It was red because of the stale version assertion and the unguarded `jsonschema` import, both fixed here.
132
+
133
+ ## 1.1.0 — 2026-11-09
134
+
135
+ ### Added
136
+ - Ed25519 agent identity registry: public keys and revocation metadata are project-scoped; private keys are stored outside the repository in the user's Pakem config directory with owner-only permissions where supported.
137
+ - Canonical signed payload envelopes with digest and Ed25519 signature verification.
138
+ - Short-lived delegation tokens scoped to subject, audience, allowed actions, issue time, expiry, and token ID; verification rejects tampering, wrong audience/action, expired tokens, and revoked identities.
139
+ - Explicit Ed25519 key rotation with new key IDs and retained retired public-key metadata.
140
+ - Optional local SQLite coordination backend. Explicit migration retains the original JSON board and JSONL event ledger as backups.
141
+ - Atomic SQLite board+event writes, WAL mode, FULL synchronous mode, bounded busy timeout, and SQLite online backup command.
142
+ - Team storage status/migration/backup CLI and doctor visibility for selected backend.
143
+ - Pakem Conformance Profile v1 and release-specific regression suite.
144
+
145
+ ### Compatibility and security notes
146
+ - JSON/JSONL remains the default storage backend; existing projects are not migrated automatically.
147
+ - Ed25519 operations require the optional `cryptography` package. Core CLI/runtime remains standard-library-only.
148
+ - Signed delegation tokens are bearer credentials. This release does not provide network transport authentication, process attestation, replay prevention, distributed consensus, or a multi-host coordination server.
149
+ - SQLite coordination is local and requires reliable filesystem locking/WAL semantics.
150
+ - Pakem Protocol event/session envelope v1.0 remains unchanged; new functions are advertised through capabilities.
151
+
152
+ ### Validation
153
+ - **24 release-specific tests** in `tests/test_release_110.py` passed when executed individually, including cross-process identity creation and SQLite task-claim contention. The 12 release-1.0 tests also passed as a class.
154
+ - Python source compilation, JSON parsing for all 17 schema files, fresh-install/upgrade checks, and final packaged-archive smoke tests passed.
155
+ - The full legacy suite remains sensitive to a subprocess-test-harness hang in long combined batches; results are reported by targeted/isolated execution rather than claiming one uninterrupted full-suite pass.
156
+
157
+ ## 1.0.0
158
+
159
+ - **Stable Operating Protocol**: Pakem Protocol v1.0 event envelope dan session compatibility rules dinyatakan frozen; feature extension dilakukan melalui capability negotiation (`protocol negotiate`) dan `capabilities.schema.json`.
160
+ - **Protocol capability negotiation**: peer version compatibility, capability intersection, dan unsupported capability reporting tersedia dari Core dan CLI.
161
+ - **MCP stateless stdio adapter**: server dependency-free untuk MCP `2026-07-28`, dengan `server/discover`, `tools/list`, dan `tools/call`; setiap request memvalidasi per-request version/capabilities metadata.
162
+ - **MCP read-only by default**: context/protocol/team/graph/impact/policy tools tersedia read-only. Team mutation tools hanya terekspos dengan `--allow-write` plus host-bound `--agent-id`; actor ID tidak bisa dioverride lewat tool arguments, dan tool exposure mengikuti role.
163
+ - **Git Worktree Isolation**: buat/list/remove worktree task/agent di `.pakem/worktrees/`, branch `pakem/<task>/<agent>`, root/path guard, dirty-removal guard, tanpa merge/push/delete-branch otomatis.
164
+ - **Doctor/upgrade/init integration**: module protocol/MCP/worktree, capability schema, dan adapter docs dipasang saat init/upgrade; doctor memeriksa instalasinya; `.pakem/worktrees/` di-ignore.
165
+ - **Trust model ditegaskan**: agent IDs, actor names, dan MCP `clientInfo` adalah metadata, bukan autentikasi. Host tetap mengikat caller, menegakkan policy, dan memediasi approval.
166
+ - **Test baru**: 12 test spesifik release 1.0.0 untuk compatibility negotiation, init/schema install, MCP discovery/metadata/stdio/role binding, dan Git worktree isolation/removal guards. Seluruh 12 test lulus.
167
+
168
+ # Changelog
169
+
170
+ ## 0.9.0
171
+
172
+ - **Multi-Agent Coordination Core**: modul `pakem_core/coordination.py` menyediakan shared task board untuk registrasi agent, role/capability, assignment, dan dependency-aware task.
173
+ - **Exclusive expiring leases**: claim diserialisasi dengan cross-process file lock; lease dapat diperpanjang dengan heartbeat dan diambil alih setelah kedaluwarsa.
174
+ - **Handoff & recovery**: agent dapat release/handoff task; lead/coordinator dapat reassign task setelah lease pemilik lama kedaluwarsa; task dapat diblock/unblock.
175
+ - **Two-phase completion**: worker submit summary/evidence references ke state `review`; agent reviewer berbeda harus approve sebelum task menjadi `done`; keputusan `rework` mengembalikan task ke `open`.
176
+ - **Pakem Protocol v1.0 events**: event team memakai envelope yang sama dengan session/runtime events; coordination event schema menjadi subset event protocol v1.0.
177
+ - **Machine contracts**: tambah board, status-response, dan coordination-event JSON Schema; CLI `pakem team` menyediakan init/status/register/add/assign/claim/heartbeat/release/handoff/submit/review/block/unblock/events.
178
+ - **Integration**: `init`, `upgrade`, `doctor`, `context --json`, adapter protocol, dan `.gitignore` memahami Multi-Agent Coordination.
179
+ - **Security boundaries**: agent ID/role adalah metadata kooperatif, bukan autentikasi; Pakem tidak spawn agent, menjalankan command, sandbox file scope, merge branch, atau menyediakan distributed consensus.
180
+ - **Tests**: test terarah koordinasi mencakup lease, klaim multi-proses, dependency gate, handoff, independent review, schema, path traversal, context, doctor, dan upgrade. Beberapa kelompok test dijalankan terpisah karena test harness subprocess dapat macet bila dijalankan sebagai satu batch panjang.
181
+
182
+
183
+ ## 0.8.0
184
+
185
+ - **Autonomous Runtime v1**: modul `pakem_core/runtime.py` menyediakan workflow state machine dengan transisi eksplisit, revision tracking, dan lifecycle hooks standar.
186
+ - **Checkpoint & recovery**: snapshot atomic berisi workflow + Git HEAD/working-tree state. Recovery hanya mengembalikan metadata ke `recovering`; tidak menjalankan reset/revert/checkout dan tidak mengubah source code.
187
+ - **Policy Engine**: `.pakem/POLICY.json` mendefinisikan `manual`, `assisted`, `guarded_autonomous`, max autonomous risk, approval-required categories, denied categories, dan TTL.
188
+ - **Approval one-use**: approval terikat pada workflow, kategori, risiko, dan target; memiliki expiry dan tidak dapat digunakan ulang. Host runtime tetap wajib melakukan konfirmasi user tepercaya; CLI bukan mekanisme autentikasi manusia.
189
+ - **Lifecycle hooks**: `runtime hook` untuk `session.start`, `task.before`, `task.after`, `verification.before`, `session.finish`, dan `handover`, mengembalikan `allow`, `require_approval`, atau `deny` tanpa mengeksekusi aksi.
190
+ - **CLI**: tambah `runtime init/status/transition/checkpoint/recover/hook` dan `policy show/check/approve`; `context --json`, `doctor`, `init`, dan `upgrade` memahami runtime/policy.
191
+ - **Protocol events & schemas**: perluas Protocol v1 dengan event runtime/policy; tambah workflow, checkpoint, dan policy JSON Schema.
192
+ - **Safety boundary**: state runtime di `.pakem/runtime/` diabaikan Git; hook ledger menyimpan hash payload/target, bukan payload mentah. Runtime tidak mengeksekusi command, deployment, atau agent.
193
+ - **Regression tests**: tambah 16 test untuk state transition, recovery, one-use/scope-bound approval, autonomy modes, hook decisions, context snapshot, policy validation, dan upgrade yang menjaga konfigurasi policy pengguna; total suite menjadi 89 test case. Semua test dijalankan dan lulus dalam kelompok/isolasi; full suite belum stabil dijalankan sebagai satu proses karena beberapa batch subprocess test dapat macet.
194
+
195
+
196
+ ## 0.7.0
197
+
198
+ - **Pakem Intelligent Core (first modular boundary)**: `scripts/pakem_core/` memisahkan kemampuan intelligence dari entrypoint CLI; `init`/`upgrade` memasang modul Core secara mandiri di `.pakem/pakem_core/`.
199
+ - **Dependency Graph**: `pakem graph [--json] [--output PATH] [--exclude-tests]` memetakan file source dan import lokal yang terdeteksi (Python, JS/TS, Vue/Svelte, Go module lokal, Java/Kotlin).
200
+ - **Impact Analysis**: `pakem impact --files FILE...`, `--base REF`, atau `--staged` melaporkan perubahan, direct/transitive dependents, kandidat test terdampak, rekomendasi verification, dan risk signal.
201
+ - **Machine-readable contracts**: JSON Schema dan dokumentasi `pakem.dependency-graph/v1` serta `pakem.impact-analysis/v1` dipasang ke `.pakem/intelligence/v1/` dan dapat dipakai runtime selain CLI.
202
+ - **Safety boundary**: scanner read-only (kecuali `graph --output` eksplisit), tidak mengeksekusi kode/test/build/network, menolak path impact di luar root; `impact --strict` exit 1 untuk sinyal risiko HIGH.
203
+ - **Doctor/upgrade integration**: doctor memeriksa instalasi Core dan schema; upgrade menyinkronkan CLI, Core, schema protocol/intelligence, dan adapter tanpa menimpa dokumen isi proyek.
204
+ - **Batas analisis**: graph/impact statis dan heuristik; dynamic import, reflection, alias, generated code, framework routing, dan runtime wiring dapat luput. Hasil bukan bukti tidak ada dampak dan tidak menggantikan verification/review.
205
+ - **Test tambahan**: suite kini berisi 73 test case; 10 test baru mencakup dependency Python/TypeScript/Go/Java, direct/transitive impact, kandidat test, path traversal, output JSON, mode strict, dan pemulihan Core/schema melalui upgrade.
206
+
207
+ ## 0.6.0
208
+
209
+ - **Pakem Protocol v1.0**: kontrak independen dari model/tool untuk event dan session, disertai JSON Schema dan catatan kompatibilitas.
210
+ - **Machine context snapshot**: `pakem context --json` merangkum project, sesi aktif, spec/plan, blockers, dan rekomendasi langkah berikutnya tanpa mengirim isi source/secret.
211
+ - **Append-only event ledger**: lifecycle sesi, task, approval spec, dan verification dicatat sebagai JSONL di `.pakem/events/`; penulisan diserialisasi oleh lock Pakem.
212
+ - **Protocol tooling**: `pakem protocol info`, `pakem protocol validate-event FILE`, `pakem protocol validate-session FILE`, dan `pakem events [--json] [--session ID]`.
213
+ - `init` dan `upgrade` memasang/menyinkronkan schema protocol dan mengabaikan direktori event lokal di `.gitignore`; `doctor` memeriksa pemasangan schema dan kesehatan ledger.
214
+ - Adapter agent diberi instruksi untuk memakai machine context dan event ledger. Session baru diberi `schemaVersion: 1`; session lama tetap dapat dibaca.
215
+ - Batasan: ledger belum immutable/ditandatangani, belum ada MCP server/SDK, dan Pakem belum mengeksekusi atau mengorkestrasi agent.
216
+ - Cakupan test menjadi 63 unit test, termasuk validasi kontrak event/session dan pencatatan lifecycle.
217
+
218
+ ## 0.5.0
219
+
220
+ - **`pakem spec`**: membuat `.pakem/SPEC.md` (masalah, non-goal, acceptance, pendekatan) dengan `Status: draft`; `pakem spec --approve` menolak placeholder dan menandai approved. Gate `spec` menggagalkan `check`/`finish` selama SPEC ada tapi belum approved.
221
+ - **`pakem plan`**: mengelola `.pakem/PLAN.md` berisi task kecil (`T1`, `T2`, …) dengan `files` dan `verify`. `plan add`, `plan done T1`, `plan drop T1 --reason ...`, `plan list`. Gate `plan` menggagalkan `check`/`finish` selama masih ada task terbuka.
222
+ - **Workflow ditampilkan**: `start`/`status` menunjukkan status SPEC dan progres PLAN; `doctor` memperingatkan SPEC draft / task terbuka.
223
+ - **Deduplikasi sumber kebenaran**: protokol `CONTEXT.md` dan adapter digenerate dari satu `PROTOCOL_TEXT` (marker + `upgrade`/`doctor`); checklist keamanan hanya di `conventions.md` (reviews menunjuk ke sana); audit handover cukup satu baris; `plan done/drop` menyinkronkan `nextStep` sesi.
224
+ - `SPEC.md` dan `PLAN.md` ikut placeholder gate; `finish --strict` tetap berlaku.
225
+ - 53 unit test.
226
+
227
+ ## 0.4.0
228
+
229
+ - **`finish` menyimpan bukti verify**: perintah, exit code, durasi, hash output, dan hash CLI disimpan di sesi sebagai `verifyEvidence`; dicetak sebagai `[BUKTI] verify: ...`.
230
+ - **`finish --strict`**: gagal bila aturan/verify/CLI berubah, `verify` bukan `pass`, atau ada gap audit WAJIB. Default tetap advisory dengan `[WARN] wajib:`.
231
+ - **Audit WAJIB selaras dengan `finish`**: README/lockfile/`.env.example` yang kurang sekarang terlihat di `finish`, bukan hanya di `audit`.
232
+ - **Atomic untuk semua tulisan**: `.pakem/*.md`, ADR, BUG-HISTORY, adapter, dan config memakai temp + `fsync` + rename, bukan hanya session.
233
+ - **Lock antar-proses** (`pakem_lock`) untuk `start`, `step`, `finish`, `bug`, `adr`, dan `prune`; session ID memakai microseconds agar tidak bertabrakan.
234
+ - **`pakem upgrade`**: memperbarui CLI, flag baru, `.gitignore`, dan adapter tanpa menyentuh `CONTEXT.md`/`MODULE-MAP.md`/ADR. `--dry-run` tersedia.
235
+ - **Perbaikan dari uji Codex**: audit tidak lagi mewajibkan lockfile untuk `package.json` tanpa dependency; `doctor` memperingatkan duplikasi `test/` + `tests/`.
236
+ - **Struktur skill sesuai skill-creator**: `templates/` dipindah ke `assets/templates/`, ditambah `LICENSE` (MIT), `compatibility`, dan `metadata.version` di frontmatter; lolos `quick_validate.py` dan `package_skill.py`.
237
+
238
+ ## 0.3.0
239
+
240
+ - **`pakem audit`** (read-only): memilah artefak proyek menjadi WAJIB / DISARANKAN / TIDAK PERLU berdasarkan `type`, `exposure`, `deploy`, `handover`, `sensitive`, dan isi repo. `--json` untuk agent, `--strict` untuk exit 1 bila WAJIB kurang. Tidak pernah membuat file.
241
+ - **Flag risiko** di `PROJECT.md`: `exposure` (private/public), `deploy` (none/staging/production), `handover` (true/false), di samping `sensitive`. Ditampilkan `init`, dibaca `audit`.
242
+ - **Peringatan penurunan flag**: `start` memotret flag baru; `check`/`finish`/`audit` memberi `[WARN]` bila `exposure`/`deploy`/`handover`/`sensitive` diturunkan diam-diam.
243
+ - **Sesi tahan listrik padam**: `save_session` menulis atomik (temp + `fsync` + rename). File sesi yang korup dilaporkan `[WARN] sesi korup diabaikan`, tidak lagi dilewati diam-diam.
244
+ - **`references/artifacts.md`**: panduan memilih artefak per mode kegagalan (listrik padam, onboarding, insiden, rilis, repo publik, data sensitif), pilihan kanonik, dan daftar yang tidak boleh dibuat otomatis.
245
+ - **Rencana artefak saat `init`**: langsung mencetak berapa WAJIB belum ada, berapa disarankan, berapa tidak perlu.
246
+ - **`finish` memperingatkan gap berisiko**: `[WARN] risiko:` untuk `deploy`/`sensitive`/`exposure`/`handover` yang aktif tapi artefaknya belum ada. Advisory (tidak mengubah exit code), disimpan di sesi sebagai `riskWarnings`.
247
+ - **`pakem handover`**: membuat satu `HANDOVER.md` (status, akses tanpa password, kontak, sisa kerja, risiko). Placeholder-nya ikut gate sampai diisi.
248
+ - **`references/reviews.md`**: lensa review frontend (konsistensi, state, a11y) dan backend (otorisasi, validasi, secret) — bukan gate, dipakai sebelum `finish` bila relevan.
249
+ - **`pakem doctor`**: diagnosis config, placeholder, `.pakem/pakem.py`, git, hook, adapter basi, sesi korup, dan gap WAJIB; `--verify` untuk menjalankan verify, `--json` untuk agent. Exit 1 bila ada FAIL.
250
+ - **`pakem prune`**: pangkas riwayat sesi lama; dry-run default, sesi aktif dan sesi korup tidak disentuh.
251
+ - **`pakem ci`**: generate `.github/workflows/ci.yml` yang menjalankan `pakem check`; langkah setup mengikuti stack (Node npm/pnpm/yarn, Python, Go, Rust).
252
+ - **Perbaikan dari uji Codex**: audit tidak lagi mewajibkan lockfile untuk `package.json` tanpa dependency; `doctor` memperingatkan bila `test/` dan `tests/` dipakai bersamaan.
253
+ - Template `PROJECT.md` memuat flag baru; `init` menyarankan `pakem audit`.
254
+
255
+ ## 0.2.1
256
+
257
+ - **`hook install` memakai folder hooks yang benar-benar dibaca git** (`git rev-parse --git-path hooks`). Sebelumnya hook crash di worktree (`.git` berupa file) dan diam-diam tidak terpakai bila `core.hooksPath` diset. Kini `core.hooksPath` dan worktree didukung, dan path hasil pemasangan dilaporkan.
258
+
259
+ ## 0.2.0
260
+
261
+ - **Peringatan perubahan aturan.** `start` menyimpan potret `rule.*`, `verify`, `sensitive`, dan hash `.pakem/pakem.py`; `check`/`finish` menampilkan `[WARN]` bila ada yang dilonggarkan atau diubah. Tidak memblokir; tercatat di sesi.
262
+ - **Cek kondisi repo saat resume.** `start` dan `step` mencatat HEAD dan file yang berubah; resume melaporkan commit baru atau perubahan sejak catatan terakhir (repo git saja).
263
+ - **Perintah `bug`** dan `finish --fixed-bug` (gate bug). Entri BUG-HISTORY dibuat lewat CLI, terbaru di atas; field kosong menjadi placeholder yang ditolak gate.
264
+ - **Windows:** protokol memakai shorthand `pakem` dengan catatan interpreter; git hook mencari interpreter yang benar-benar jalan (`python3`, `python`, `py -3`); deteksi `verify` lintas OS. Belum diuji di Windows.
265
+ - Perbaikan: parser config tidak lagi memotong tanda kutip penutup di perintah `verify` (mis. `python -c "..."`).
266
+ - Template `BUG-HISTORY.md` memakai bagian `## Entri`.
267
+
268
+ ## 0.1.0
269
+
270
+ - Rilis awal: `init`, `start`, `step`, `status`, `check`, `finish`, `adr`, `adapt`, `hook`; gate session/rules/placeholder/drift/verify; adapter Claude, Codex, Cursor, Gemini, Copilot.
271
+
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Pakem contributors
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.