agentic-project-kit 1.0.2__tar.gz → 1.0.4__tar.gz

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/.agentic/dpa/acceptance/current_handoff_operational_state.json

@@ -1,9 +1,9 @@
 {
-  "accepted_at": "2026-08-20T17:12:48.430547+00:00",
+  "accepted_at": "2026-08-23T21:27:15.054215+00:00",
   "accepted_gate_result": "pass",
   "accepted_gate_set_id": "dpa-current-handoff-minimal-gate-set-v1",
   "accepted_lifecycle_outcome": "accepted",
-  "branch": "docs/post-pr2113-handoff-refresh",
+  "branch": "docs/post-pr2133-handoff-refresh",
   "claims": {
     "generated_outputs_manually_patched": false,
     "kit_conformance_claimed": false,
@@ -17,17 +17,17 @@
   },
   "schema_version": 1,
   "source": {
-    "fingerprint": "4da0c79f150af077ca9a1a0deaa83fe7b37c4e48f68549ae18a33af8e2778153",
+    "fingerprint": "fe1c1e4db786e666eb7d81a7275c8963d853f5836347d22511064ac541f2cf91",
     "path": ".agentic/operational_handoff_state.yaml"
   },
   "status": "accepted",
   "target": {
-    "complete_target_fingerprint": "de76a3ad26e82b0c6073182fe8d5f06e8c18986dcc8ac4b764c004b28fa595ac",
+    "complete_target_fingerprint": "7ea46779ab4fe05dfbd8f86b80dd762b28035001211a6d86bdba8e19c0b75447",
     "path": "docs/handoff/CURRENT_HANDOFF.md",
-    "payload_fingerprint": "de76a3ad26e82b0c6073182fe8d5f06e8c18986dcc8ac4b764c004b28fa595ac",
-    "pre_write_fingerprint": "1fcb9a1ba437f85ce7311e741d5739959690131bbe49fd39165ae3372650eb8f"
+    "payload_fingerprint": "7ea46779ab4fe05dfbd8f86b80dd762b28035001211a6d86bdba8e19c0b75447",
+    "pre_write_fingerprint": "fbcd83f167420c80f4f06d0ec221d9ab0bc528b8c5901623bc3904c93e294cb8"
   },
   "target_scope": "CURRENT_HANDOFF_OPERATIONAL_STATE_BLOCK",
-  "validation_ref": "8cd7a5cfee2d7176797fd6335492d0c890de9999",
+  "validation_ref": "5afde2f0dd4dbc92f1a8f3ff2754ad921d6c87d8",
   "writer_id": "WRT-CH-001"
 }

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/.agentic/handoff_state.yaml

@@ -10,8 +10,8 @@ repo:
   default_branch: main
 safe_state:
   branch: main
-  commit: 8cd7a5cf
-  commit_subject: Prepare v1.0.2 safety release (#2113)
+  commit: 5afde2f0
+  commit_subject: Prepare release v1.0.4 (#2133)
   semantics: last_substantive_work_state
   working_tree_expected_clean: true
   administrative_refresh_prs:
@@ -433,7 +433,7 @@ handoff_maintenance:
   no_redundant_rules: true
   no_contradictory_rules: true
   remove_obsolete_rules_when_system_changes: true
-  latest_successor_prompt: docs/reports/terminal/post-pr2113-successor-chat-handoff.md
+  latest_successor_prompt: docs/reports/terminal/post-pr2133-successor-chat-handoff.md
   first_instruction: 'Review PR #1436 and the refreshed successor handoff package
     for the release command authority planning slice. After merge, start from fresh
     main and use centralized historical record docs/planning/PROJECT_DIRECTION.yaml#release-command-authority-slice
@@ -444,6 +444,6 @@ next_step:
     main and use centralized historical record docs/planning/PROJECT_DIRECTION.yaml#release-command-authority-slice
     before DOI, legacy-doc, absolute-path, or GUI work.'
 evidence:
-  latest_successor_prompt: docs/reports/terminal/post-pr2113-successor-chat-handoff.md
+  latest_successor_prompt: docs/reports/terminal/post-pr2133-successor-chat-handoff.md
 # preservation-anchor: use d for log-backed PASS and f for log-backed FAIL
 # preservation-anchor: nested shell/Python quote layers

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/.agentic/operational_handoff_state.yaml

@@ -1,12 +1,12 @@
 schema_version: 1
 current_head:
-  full: 8cd7a5cfee2d7176797fd6335492d0c890de9999
-  short: 8cd7a5cf
-  subject: Prepare v1.0.2 safety release (#2113)
+  full: 5afde2f0dd4dbc92f1a8f3ff2754ad921d6c87d8
+  short: 5afde2f0
+  subject: Prepare release v1.0.4 (#2133)
 last_substantive_work_state:
-  full: 8cd7a5cfee2d7176797fd6335492d0c890de9999
-  short: 8cd7a5cf
-  subject: Prepare v1.0.2 safety release (#2113)
+  full: 5afde2f0dd4dbc92f1a8f3ff2754ad921d6c87d8
+  short: 5afde2f0
+  subject: Prepare release v1.0.4 (#2133)
 administrative_context:
   - "PR #1257 hardened admin-refresh-pr and pr-complete recovery."
   - "PR #1255 added generated operational handoff block replacement."

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/AGENTS.md

@@ -12,7 +12,7 @@ rule_source_boundary: pointer_not_duplicate_rule_book
 # Agent Instructions
 
 <!-- command-manifest-entrypoint:start -->
-MANDATORY FIRST READ: docs/reference/agentic-kit-commands.json (manifest_sha: 072c9526b5cd). Every reply containing commands MUST start with: COMMAND_MANIFEST_ACK 072c9526b5cd. Consult `agentic-kit command-for` before proposing commands and choose the most specific available Kit workflow command.
+MANDATORY FIRST READ: docs/reference/agentic-kit-commands.json (manifest_sha: 2ab1c7c2a951). Every reply containing commands MUST start with: COMMAND_MANIFEST_ACK 2ab1c7c2a951. Consult `agentic-kit command-for` before proposing commands and choose the most specific available Kit workflow command.
 <!-- command-manifest-entrypoint:end -->
 
 > Outer-doc currency note: Operational chat handoff now uses the deterministic Successor Handoff Package. Treat `docs/reports/handoff-packages/latest/successor_context.yaml`, `source_manifest.json`, `validation_report.json`, `execution_contract.json`, and `successor_prompt.md` as the canonical generated handoff package. The markdown prompts are projections, not independent sources of truth.

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/CHANGELOG.md

@@ -1,11 +1,29 @@
+## v1.0.4 - 2026-08-23
+
+- Zenodo DOI verification pending for v1.0.4.
+- Close out v1.0.3 DOI metadata with preserved release evidence.
+- Add governed Planner-Kit-Executor surface with dry-run defaults, bounded action guards, and command-manifest governance.
+- Add measured first-chat onboarding with route-selection documentation, workspace-detection scope anchors, and regression coverage.
+
+## v1.0.3 - 2026-08-23
+
+- Close out v1.0.2 DOI metadata
+- Harden PR lifecycle settle cleanup
+- Preserve release evidence, handoff continuity, and bounded PR lifecycle cleanup governance.
+
+Post-release verification complete: GitHub Release exists, Zenodo concept DOI `10.5281/zenodo.20101359`, verified v1.0.3 DOI `10.5281/zenodo.22071671`.
+
+Zenodo v1.0.3 DOI: 10.5281/zenodo.22071671
 ## v1.0.2 - 2026-08-20
 
-- Zenodo DOI verification pending for v1.0.2.
 - Harden local Docker usage with bounded container smoke evidence and explicit scope boundaries.
 - Harden first-contact validation and PR closeout with regression coverage for clean installs, Git prerequisites, and the four-step handoff lifecycle.
 - Harden workspace remove and site fallback checks with guarded mutation planning and deterministic projection drift tests.
 - Add decomplexification audit roadmap while preserving governance gates and compatibility-safe facade planning.
 
+Post-release verification complete: GitHub Release exists, Zenodo concept DOI `10.5281/zenodo.20101359`, verified v1.0.2 DOI `10.5281/zenodo.22032882`.
+
+Zenodo v1.0.2 DOI: 10.5281/zenodo.22032882
 ## v1.0.1 - 2026-08-14
 
 - Zenodo DOI verification pending for v1.0.1.

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/CITATION.cff

@@ -9,6 +9,8 @@ repository-code: "https://github.com/vfi64/agentic-project-kit"
 url: "https://github.com/vfi64/agentic-project-kit"
 doi: "10.5281/zenodo.20101359"
 # Verified v0.3.29 version DOI: 10.5281/zenodo.20303218
+# Verified v1.0.3 version DOI: 10.5281/zenodo.22071671
+# Verified v1.0.2 version DOI: 10.5281/zenodo.22032882
 # Verified v1.0.0 version DOI: 10.5281/zenodo.21925421
 # Verified v0.5.0 version DOI: 10.5281/zenodo.21850952
 # Verified v0.4.13 version DOI: 10.5281/zenodo.21631484
@@ -60,9 +62,9 @@ license: MIT
 # Verified v0.4.4 version DOI: 10.5281/zenodo.20431326
 # Verified v0.4.5 version DOI: 10.5281/zenodo.20467371
 # Verified v0.4.6 version DOI: 10.5281/zenodo.20593293
-version: 1.0.2
+version: 1.0.4
 # Verified v0.3.30 version DOI: 10.5281/zenodo.20308526
 # Verified v0.3.31 version DOI: 10.5281/zenodo.20313834
 # Verified v0.3.32 version DOI: 10.5281/zenodo.20314341
-date-released: "2026-08-20"
+date-released: "2026-08-23"
 # Verified v0.3.23 version DOI: 10.5281/zenodo.20261956

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: agentic-project-kit
-Version: 1.0.2
+Version: 1.0.4
 Summary: Govern AI-assisted repository work with explicit contracts, gates, evidence, and handoffs.
 Project-URL: Repository, https://github.com/vfi64/agentic-project-kit
 Author: Volker Fickert
@@ -21,7 +21,7 @@ Description-Content-Type: text/markdown
 > Handoff architecture: the deterministic Successor Handoff Package writes `successor_context.yaml`, `source_manifest.json`, `validation_report.json`, `execution_contract.json`, and `successor_prompt.md` under `docs/reports/handoff-packages/latest/` for this repo or `.agentic/state/handoff/packages/latest/` in external workspace mode. New chats verify the package and execution contract, not chat memory.
 
 
-Current version: 1.0.2
+Current version: 1.0.4
 [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.20101359.svg)](https://doi.org/10.5281/zenodo.20101359)
 
 `agentic-project-kit` is a local Python package and CLI for governing AI-assisted repository work with explicit contracts, gates, evidence, handoffs, policy selection, task tracking, GitHub automation, and release validation.
@@ -113,6 +113,12 @@ agentic-kit --help
 
 ## Quick start
 
+First-chat route selection is in `docs/ONBOARDING.md`. It separates creating a
+new governed project, adding the Kit operating layer to an existing repository,
+and working on this Kit repository. Use `agentic-kit onboarding measure` to
+check that the onboarding guide still matches the command manifest and
+workspace-detection message.
+
 For the generated install and usage walkthrough, including the PyPI install
 path, the source install path, a Docker-based safe package test, new
 repositories, and existing repositories, see
@@ -568,6 +574,12 @@ The action inventory classifies by category, safety, and Access level. Access le
 
 Architecture details are documented in `docs/architecture/LOCAL_COCKPIT_FOUNDATION.md`.
 
+## Planner-Kit-Executor Contract
+
+`agentic-kit executor plan INTENT` and `agentic-kit executor run INTENT` expose the governed Planner-Kit-Executor surface. The intent may name `hermes` as the first executor adapter, but every runnable step must still resolve through the generated command manifest or the cockpit/action registry. This keeps Kit authority in one place instead of creating a parallel planner or workflow taxonomy.
+
+`agentic-kit executor run` is dry-run by default. Read-only manifest and cockpit steps may run with `--execute`; bounded cockpit actions also require step-level `allow_bounded: true` and CLI `--allow-bounded`; destructive actions remain blocked. The contract, failure states, and evidence rules are documented in `docs/architecture/PLANNER_KIT_EXECUTOR_CONTRACT.md`.
+
 ## CLI command package structure
 
 The root CLI module is intentionally a thin root command registry. Command implementations live under `src/agentic_project_kit/cli_commands/`.
@@ -744,9 +756,9 @@ These repository settings are maintainer-owned and are not changed by the packag
 
 ## Current status
 
-Prepared release: `v1.0.2`; GitHub Release, tag publication, and Zenodo version DOI verification are pending.
-Version `1.0.2` is the current release line prepared as a safety baseline after the pre-GUI transfer-wrapper, output-discipline, GUI wrapper-gating, PR diagnostics, and release-plan guard hardening work.
-Current verified release: `v1.0.0` with Zenodo version DOI `10.5281/zenodo.21925421`.
+Prepared release: `v1.0.4`; GitHub Release, tag publication, and Zenodo version DOI verification are pending.
+Version `1.0.4` is the current release line prepared as a safety baseline after the pre-GUI transfer-wrapper, output-discipline, GUI wrapper-gating, PR diagnostics, and release-plan guard hardening work.
+Current verified release: `v1.0.3` with Zenodo version DOI `10.5281/zenodo.22071671`.
 Earlier verified version-specific DOI notes are maintained in `docs/releases/VERIFIED_RELEASES.md`; historical release records remain in this section and the verified release archive.
 
 Archived GUI/cockpit release notes: v0.3.22 verified DOI `10.5281/zenodo.20256637`; v0.3.19 verified DOI `10.5281/zenodo.20246121`.

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/README.md

@@ -3,7 +3,7 @@
 > Handoff architecture: the deterministic Successor Handoff Package writes `successor_context.yaml`, `source_manifest.json`, `validation_report.json`, `execution_contract.json`, and `successor_prompt.md` under `docs/reports/handoff-packages/latest/` for this repo or `.agentic/state/handoff/packages/latest/` in external workspace mode. New chats verify the package and execution contract, not chat memory.
 
 
-Current version: 1.0.2
+Current version: 1.0.4
 [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.20101359.svg)](https://doi.org/10.5281/zenodo.20101359)
 
 `agentic-project-kit` is a local Python package and CLI for governing AI-assisted repository work with explicit contracts, gates, evidence, handoffs, policy selection, task tracking, GitHub automation, and release validation.
@@ -95,6 +95,12 @@ agentic-kit --help
 
 ## Quick start
 
+First-chat route selection is in `docs/ONBOARDING.md`. It separates creating a
+new governed project, adding the Kit operating layer to an existing repository,
+and working on this Kit repository. Use `agentic-kit onboarding measure` to
+check that the onboarding guide still matches the command manifest and
+workspace-detection message.
+
 For the generated install and usage walkthrough, including the PyPI install
 path, the source install path, a Docker-based safe package test, new
 repositories, and existing repositories, see
@@ -550,6 +556,12 @@ The action inventory classifies by category, safety, and Access level. Access le
 
 Architecture details are documented in `docs/architecture/LOCAL_COCKPIT_FOUNDATION.md`.
 
+## Planner-Kit-Executor Contract
+
+`agentic-kit executor plan INTENT` and `agentic-kit executor run INTENT` expose the governed Planner-Kit-Executor surface. The intent may name `hermes` as the first executor adapter, but every runnable step must still resolve through the generated command manifest or the cockpit/action registry. This keeps Kit authority in one place instead of creating a parallel planner or workflow taxonomy.
+
+`agentic-kit executor run` is dry-run by default. Read-only manifest and cockpit steps may run with `--execute`; bounded cockpit actions also require step-level `allow_bounded: true` and CLI `--allow-bounded`; destructive actions remain blocked. The contract, failure states, and evidence rules are documented in `docs/architecture/PLANNER_KIT_EXECUTOR_CONTRACT.md`.
+
 ## CLI command package structure
 
 The root CLI module is intentionally a thin root command registry. Command implementations live under `src/agentic_project_kit/cli_commands/`.
@@ -726,9 +738,9 @@ These repository settings are maintainer-owned and are not changed by the packag
 
 ## Current status
 
-Prepared release: `v1.0.2`; GitHub Release, tag publication, and Zenodo version DOI verification are pending.
-Version `1.0.2` is the current release line prepared as a safety baseline after the pre-GUI transfer-wrapper, output-discipline, GUI wrapper-gating, PR diagnostics, and release-plan guard hardening work.
-Current verified release: `v1.0.0` with Zenodo version DOI `10.5281/zenodo.21925421`.
+Prepared release: `v1.0.4`; GitHub Release, tag publication, and Zenodo version DOI verification are pending.
+Version `1.0.4` is the current release line prepared as a safety baseline after the pre-GUI transfer-wrapper, output-discipline, GUI wrapper-gating, PR diagnostics, and release-plan guard hardening work.
+Current verified release: `v1.0.3` with Zenodo version DOI `10.5281/zenodo.22071671`.
 Earlier verified version-specific DOI notes are maintained in `docs/releases/VERIFIED_RELEASES.md`; historical release records remain in this section and the verified release archive.
 
 Archived GUI/cockpit release notes: v0.3.22 verified DOI `10.5281/zenodo.20256637`; v0.3.19 verified DOI `10.5281/zenodo.20246121`.

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/docs/DOCUMENTATION_COVERAGE.yaml

@@ -52,6 +52,71 @@ rules:
     - Documentation System Audit Contract
     - agentic-kit docs-audit
     - review-only
+- id: planner-kit-executor-coverage
+  description: Governed Planner-Kit-Executor commands and Hermes adapter boundary must
+    remain visible without creating a parallel workflow authority.
+  documents:
+  - path: README.md
+    terms:
+    - Planner-Kit-Executor Contract
+    - agentic-kit executor plan INTENT
+    - agentic-kit executor run INTENT
+    - hermes
+    - generated command manifest
+    - cockpit/action registry
+    - dry-run by default
+  - path: docs/architecture/PLANNER_KIT_EXECUTOR_CONTRACT.md
+    terms:
+    - Planner-Kit-Executor Contract
+    - Hermes is the first named executor/browser adapter
+    - command manifest and cockpit registry
+    - agentic-kit executor plan INTENT
+    - agentic-kit executor run INTENT
+    - dry-run by default
+    - block_dirty_worktree
+    - allow_bounded
+    - PASS
+    - PENDING
+    - HARD-FAIL
+  - path: docs/TEST_GATES.md
+    terms:
+    - Planner-Kit-Executor Gate
+    - agentic-kit executor plan INTENT
+    - agentic-kit executor run INTENT
+    - tests/test_planner_executor.py
+    - dry-run-by-default
+    - cockpit/action registry
+- id: measured-agent-onboarding-coverage
+  description: First-chat onboarding must remain measurable and bound to command
+    manifest and workspace detection sources.
+  documents:
+  - path: README.md
+    terms:
+    - First-chat route selection
+    - docs/ONBOARDING.md
+    - agentic-kit onboarding measure
+    - command manifest
+    - workspace-detection message
+  - path: docs/ONBOARDING.md
+    terms:
+    - First-Chat Onboarding
+    - Create a new governed project
+    - Add the Kit operating layer to an existing repository
+    - Work on this Kit repository
+    - agentic-kit init NAME
+    - agentic-kit workspace init --root PATH
+    - agentic-kit command-for
+    - command manifest
+    - governed project
+    - operating layer
+    - handoff
+  - path: docs/TEST_GATES.md
+    terms:
+    - Onboarding Measurement Gate
+    - agentic-kit onboarding measure
+    - docs/ONBOARDING.md
+    - workspace_detection.NON_WORKSPACE_NEXT_STEP
+    - tests/test_onboarding_measurement.py
 - id: planning-doc-slice-gate-coverage
   description: Temporary planning-documentation slice gate must remain discoverable
     and must keep helper-local success separate from governed slice success.
@@ -201,6 +266,9 @@ rules:
     - agentic-kit chat refresher
     - agentic-kit chat session-start
     - agentic-kit commands sync-entrypoints
+    - agentic-kit executor plan
+    - agentic-kit executor run
+    - agentic-kit onboarding measure
     - agentic-kit work-order upload
     - agentic-kit workspace dpa-intake
     - agentic-kit workspace remove

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/docs/DOCUMENTATION_REGISTRY.yaml

@@ -138,9 +138,21 @@ class_rules:
     gate_coverage: doc-mesh audit, lifecycle audit, release DOI list checks, and historical banner checks.
 
 documents:
+  - path: docs/ONBOARDING.md
+    class: user-facing description
+    status: active
+    owner: maintainers
+    review_policy: required
+    summary: Canonical first-chat onboarding route selector and glossary.
   - path: docs/planning/MASTER_IMPLEMENTATION_Q.md
     class: planning
     owner: maintainers
+  - path: docs/architecture/PLANNER_KIT_EXECUTOR_CONTRACT.md
+    class: architecture
+    status: active
+    owner: maintainers
+    review_policy: required
+    summary: Active contract for governed Planner-Kit-Executor intents and the Hermes adapter boundary.
   - path: docs/workflow/WORK_ORDER_TEMPLATES.md
     class: operational/automation
     status: active
@@ -649,6 +661,18 @@ documents:
     class: evidence/log
     owner: maintainers
     notes: Machine-readable appendix for the 2026-08-15 Decomplexification Audit, including per-command classifications and reduction tracks.
+  - path: docs/reports/HERMES_EXECUTOR_H0_INVENTORY_20260823.md
+    class: evidence/log
+    owner: maintainers
+    notes: Read-only H0 inventory evidence for Planner-Kit-Executor integration with Hermes as the first executor adapter.
+  - path: docs/reports/ONBOARDING_O0_BASELINE_20260823.md
+    class: evidence/log
+    owner: maintainers
+    notes: Read-only O0 baseline evidence for measured first-chat onboarding friction and orientation-anchor planning.
+  - path: docs/reports/release/post-release-doi-closeout-1.0.3.json
+    class: evidence/log
+    owner: maintainers
+    notes: Machine-readable post-release DOI closeout evidence for verified v1.0.3 publication and Zenodo DOI metadata.
   - path: docs/architecture/evidence/path-literal-audit-2026-07-04.md
     class: evidence/log
     owner: maintainers

agentic_project_kit-1.0.4/docs/ONBOARDING.md

@@ -0,0 +1,108 @@
+# First-Chat Onboarding
+
+Status: active  
+Date: 2026-08-23  
+Audience: first-time users, maintainers, and LLM coding agents
+
+## Purpose
+
+Use this page at the start of a new chat or first repository session. It chooses
+one route, then points to the existing Kit commands and docs. It is not a second
+planner, rulebook, workflow taxonomy, or release authority.
+
+The generated command manifest remains the command source of truth. Re-check
+command names with `agentic-kit command-for` before turning guidance into a
+terminal command.
+
+## One Decision
+
+Choose exactly one first route.
+
+### Create a new governed project
+
+Use this route when the Kit should create the repository skeleton, project
+contract, starter docs, and local gates.
+
+Core commands:
+
+```bash
+agentic-kit init NAME
+agentic-kit check
+agentic-kit doctor
+```
+
+### Add the Kit operating layer to an existing repository
+
+Use this route when project-owned source files already exist and the Kit should
+wrap the repository with governance, evidence, and handoff files.
+
+Inspect before writing:
+
+```bash
+agentic-kit workspace adopt --root PATH
+agentic-kit workspace init --root PATH
+```
+
+Write only after reviewing the plan:
+
+```bash
+agentic-kit workspace init --root PATH --execute
+agentic-kit check --root PATH
+agentic-kit doctor --root PATH
+```
+
+The shortest brownfield walkthrough is
+`docs/guides/BROWNFIELD_EXTERNAL_REPO_15_MINUTES.md`.
+
+### Work on this Kit repository
+
+Use this route when changing `vfi64/agentic-project-kit` itself.
+
+Start by reading the active agent instructions and the command manifest. Before
+starting a branch or proposing commands, resolve the specific Kit command with:
+
+```bash
+agentic-kit command-for --task work
+```
+
+Then use the governed work lifecycle rather than raw branch, PR, or handoff
+steps.
+
+## Non-Workspace Message Binding
+
+The canonical non-workspace next-step wording comes from
+`agentic_project_kit.workspace_detection.NON_WORKSPACE_NEXT_STEP`.
+
+Current source-bound snippets:
+
+```text
+agentic-kit init NAME
+agentic-kit workspace init --root PATH
+```
+
+If that source message changes, this document and the onboarding measurement
+must change in the same slice.
+
+## Minimal Glossary
+
+- governed project: a repository with Kit project contracts, docs, gates, and
+  handoff state.
+- operating layer: the `.agentic/` governance layer added around an existing
+  repository without taking ownership of product source.
+- command manifest: the generated command reference in
+  `docs/reference/agentic-kit-commands.json`.
+- gate: a deterministic check that reports pass, fail, warn, or blocked state.
+- handoff: repo-backed context for continuing work without relying on chat
+  memory.
+
+## Repeatable Measurement
+
+Run the onboarding measurement before claiming first-chat guidance is current:
+
+```bash
+agentic-kit onboarding measure --json
+```
+
+The measurement checks this document, README anchors, required command-manifest
+entries, glossary terms, and the workspace-detection next-step snippets. It
+records counts so future onboarding edits can be compared instead of guessed.

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/docs/STATUS.md

@@ -2,15 +2,15 @@
 
 ## Current State
 
-Current version: 1.0.2
-Current verified release: 1.0.0.
-Current release tag: v1.0.0.
+Current version: 1.0.4
+Current verified release: 1.0.3.
+Current release tag: v1.0.3.
 Zenodo concept DOI: `10.5281/zenodo.20101359`.
-Verified Zenodo version DOI: `10.5281/zenodo.21925421`.
-Current verified main: `8cd7a5cf` (`Prepare v1.0.2 safety release (#2113)`).
-Latest substantive work: PR #2113 (`Prepare v1.0.2 safety release (#2113)`).
+Verified Zenodo version DOI: `10.5281/zenodo.22071671`.
+Current verified main: `5afde2f0` (`Prepare release v1.0.4 (#2133)`).
+Latest substantive work: PR #2133 (`Prepare release v1.0.4 (#2133)`).
 Current governed slice: continue from fresh main with the next planned governed slice after post-merge handoff checks pass; do not repeat already verified release publication steps.
-Post-merge handoff status: PASS/NOOP after PR #2113 administrative refresh.
+Post-merge handoff status: PASS/NOOP after PR #2133 administrative refresh.
 Next safe step: continue from fresh main with the next planned governed slice.
 
 ## Historical State Snapshots
@@ -416,6 +416,6 @@ DPA-700 evidence, exact refs and Maintainer-authorized scope.
 ## Operational documentation refresh state after PR #2013
 
 Current administrative handoff refresh state is `e3509718` (`Refresh handoff state after PR2013 (#2014)`). The post-PR2013 administrative refresh is committed and merged; the next substantive slice must be created from fresh main.
-## Operational documentation refresh state after PR #2113
+## Operational documentation refresh state after PR #2133
 
-Current administrative handoff refresh state is `8cd7a5cf` (`Prepare v1.0.2 safety release (#2113)`). Continue next only after this post-PR2113 refresh is committed and merged; the next substantive slice must be created from fresh main.
+Current administrative handoff refresh state is `5afde2f0` (`Prepare release v1.0.4 (#2133)`). Continue next only after this post-PR2133 refresh is committed and merged; the next substantive slice must be created from fresh main.

{agentic_project_kit-1.0.2 → agentic_project_kit-1.0.4}/docs/TEST_GATES.md

@@ -36,6 +36,8 @@ The repository must not rely on memory, chat history, or informal claims. Releva
 | Post-release archive check | Unit tests plus agentic-kit post-release-check CLI smoke command |
 | TODO validation change | Unit tests plus agentic-kit check-todo CLI smoke command |
 | Project health check change | Unit tests plus agentic-kit doctor CLI smoke command |
+| Planner-Kit-Executor change | Unit tests plus CLI smoke commands for `agentic-kit executor plan INTENT` and `agentic-kit executor run INTENT`; confirm `run` is dry-run-by-default, resolves through the command manifest or cockpit/action registry, blocks dirty worktrees by default, and blocks bounded actions without explicit step and CLI allow signals |
+| Onboarding guidance change | Unit tests plus CLI smoke command for `agentic-kit onboarding measure`; confirm docs/ONBOARDING.md remains bound to the generated command manifest and `workspace_detection.NON_WORKSPACE_NEXT_STEP` |
 | DPA repository adoption gate change | Unit tests plus CLI smoke command for `agentic-kit dpa repo-adoption-assessment`; confirm it remains read-only and does not claim external-repo conformance |
 | Workspace DPA intake orchestration change | Unit tests plus CLI smoke command for `agentic-kit workspace dpa-intake`; confirm it remains read-only by default, writes evidence only under the DPA assessment evidence root when explicitly executed, and does not claim external-repo conformance |
 | Workspace remove lifecycle change | Unit tests plus CLI smoke command for `agentic-kit workspace remove`; confirm it is dry-run by default, removes only exact Kit-generated workspace files, unknown or modified `.agentic/` paths block execution, and project docs/source files are preserved |
@@ -236,6 +238,42 @@ The documentation mesh is split into explicit document classes:
 
 The hard audit checks only machine-checkable drift classes, including version mismatches, stale current-state wording, missing historical-source-of-truth banners, and release DOI list mismatches. It must not claim semantic proof of documentation quality.
 
+## Planner-Kit-Executor Gate
+
+Changes to the governed Planner-Kit-Executor surface must preserve Kit command
+authority. `agentic-kit executor plan INTENT` is a read-only diagnostic over the
+intent schema, generated command manifest, and cockpit/action registry.
+`agentic-kit executor run INTENT` is dry-run-by-default and may execute only
+resolved read-only steps unless a bounded cockpit action has both step-level
+`allow_bounded` and CLI `--allow-bounded`.
+
+Required evidence:
+
+    python -m pytest -q tests/test_planner_executor.py
+    agentic-kit executor plan INTENT
+    agentic-kit executor run INTENT
+    agentic-kit check-docs
+
+The gate must confirm that raw external commands, direct Hermes commands, dirty
+worktrees, destructive actions, and non-read-only direct manifest commands fail
+closed instead of becoming a second workflow authority.
+
+## Onboarding Measurement Gate
+
+Changes to first-chat guidance, workspace detection wording, public onboarding
+links, or generated quickstart projections must keep `docs/ONBOARDING.md`
+measurable and command-manifest-bound.
+
+Required evidence:
+
+    python -m pytest -q tests/test_onboarding_measurement.py
+    agentic-kit onboarding measure
+    agentic-kit check-docs
+
+The gate must confirm that `docs/ONBOARDING.md` contains the three first routes,
+the minimal glossary, required command-manifest entries, and snippets derived
+from `workspace_detection.NON_WORKSPACE_NEXT_STEP`.
+
 ## Status Current-State Audit Gate
 
 Use `agentic-kit audit-status-current-state` when changing `docs/STATUS.md`, current-state handoff projections, release-state reporting, or post-merge status-refresh behavior.

agentic_project_kit-1.0.4/docs/architecture/PLANNER_KIT_EXECUTOR_CONTRACT.md

@@ -0,0 +1,90 @@
+# Planner-Kit-Executor Contract
+
+Status: active  
+Date: 2026-08-23  
+Scope: governed executor intents, Kit command authority, and the first Hermes adapter boundary
+
+## Purpose
+
+Planner-Kit-Executor integration lets an external planner or executor describe
+work as a typed intent while `agentic-kit` remains the authority for command
+selection, safety classification, evidence, state, release, and handoff.
+
+Hermes is the first named executor/browser adapter, but Hermes is not a new
+workflow taxonomy and is not a repository authority. A Hermes-backed intent must
+still resolve each runnable step through the generated command manifest or the
+local cockpit/action registry.
+
+## Contract
+
+A planner intent is YAML with `schema_version: 1`, an `id`, a `title`, an
+`executor_adapter`, and ordered `steps`.
+
+Supported adapters are:
+
+- `hermes`: external executor/browser adapter name; repository execution still
+  passes through Kit-owned command or cockpit surfaces.
+- `kit-local`: local adapter for deterministic tests and non-browser operation.
+
+Supported step kinds are:
+
+- `command`: an argv list that starts with `agentic-kit` and resolves to the
+  generated command manifest.
+- `cockpit_action`: an action ID that resolves to the local cockpit registry.
+
+The command manifest and cockpit registry are the only durable authorities for
+step resolution. Raw `git`, `gh`, browser, shell, or Hermes commands are not
+valid intent steps.
+
+## Safety
+
+`agentic-kit executor plan INTENT` is read-only. It resolves steps, reports
+safety, reports dirty-worktree state, and returns blockers without executing
+work.
+
+`agentic-kit executor run INTENT` is dry-run by default. It writes a bounded JSON
+result under `tmp/` unless an explicit `--report` path under `docs/reports/` or
+`tmp/` is supplied.
+
+Execution rules:
+
+- read-only command-manifest steps may run with `--execute`;
+- read-only cockpit actions may run with `--execute`;
+- bounded cockpit actions require both step-level `allow_bounded: true` and CLI
+  `--allow-bounded`;
+- direct non-read-only command-manifest execution is blocked until a narrower
+  action surface exists;
+- destructive steps are always blocked;
+- dirty worktrees block by default when `block_dirty_worktree` is true;
+- external credentials, browser sessions, and GUI transports are outside the
+  durable intent and must be represented as explicit capability boundaries
+  before they affect repository state.
+
+## Evidence And Failure States
+
+Planner-executor run results use the same result vocabulary as cockpit and typed
+work-order execution: `PASS`, `FAIL`, `PENDING`, and `HARD-FAIL`.
+
+The JSON result records:
+
+- intent ID and executor adapter;
+- dirty-worktree state;
+- whether execution happened;
+- bounded evidence path;
+- blockers;
+- per-step command/action results.
+
+This result is evidence that the Kit authorized and ran a bounded set of steps.
+It is not evidence that an LLM independently judged its own semantic quality.
+
+## H1-H3 Closeout
+
+The H0 inventory is recorded in
+`docs/reports/HERMES_EXECUTOR_H0_INVENTORY_20260823.md`.
+
+This contract closes H1 by defining the proof-of-concept schema and resolution
+rules. The `agentic-kit executor plan` command closes H2 as the minimal
+read-only adapter surface. The dry-run-by-default `agentic-kit executor run`
+command closes the first H3 bounded action surface by permitting only
+manifest/cockpit-governed execution with explicit bounded-action gates and
+tests.