taskledger 0.6.0__tar.gz → 0.6.1__tar.gz

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/events/events.jsonl

@@ -0,0 +1,13 @@
+{"data":{"status":"planned"},"event":"release.created","event_id":"event-0001","record_revisions":{"release:v0.6.0":1},"release_version":"v0.6.0","schema_version":2}
+{"data":{"entry_ids":["entry-0001","entry-0002","entry-0003","entry-0004","entry-0005","entry-0006","entry-0007","entry-0008","entry-0009","entry-0010","entry-0011","entry-0012","entry-0013","entry-0014","entry-0015","entry-0016","entry-0017","entry-0018","entry-0019","entry-0020","entry-0021","entry-0022","entry-0023"]},"event":"entry.batch_added","event_id":"event-0002","record_revisions":{"entry:v0.6.0/entry-0001":1,"entry:v0.6.0/entry-0002":1,"entry:v0.6.0/entry-0003":1,"entry:v0.6.0/entry-0004":1,"entry:v0.6.0/entry-0005":1,"entry:v0.6.0/entry-0006":1,"entry:v0.6.0/entry-0007":1,"entry:v0.6.0/entry-0008":1,"entry:v0.6.0/entry-0009":1,"entry:v0.6.0/entry-0010":1,"entry:v0.6.0/entry-0011":1,"entry:v0.6.0/entry-0012":1,"entry:v0.6.0/entry-0013":1,"entry:v0.6.0/entry-0014":1,"entry:v0.6.0/entry-0015":1,"entry:v0.6.0/entry-0016":1,"entry:v0.6.0/entry-0017":1,"entry:v0.6.0/entry-0018":1,"entry:v0.6.0/entry-0019":1,"entry:v0.6.0/entry-0020":1,"entry:v0.6.0/entry-0021":1,"entry:v0.6.0/entry-0022":1,"entry:v0.6.0/entry-0023":1,"release:v0.6.0":2},"release_version":"v0.6.0","schema_version":2}
+{"data":{"released_at":"2026-07-28"},"event":"release.finalized","event_id":"event-0003","record_revisions":{"release:v0.6.0":3},"release_version":"v0.6.0","schema_version":2}
+{"data":{"status":"planned"},"event":"release.created","event_id":"event-0004","record_revisions":{"release:v0.6.1":1},"release_version":"v0.6.1","schema_version":2}
+{"data":{"kind":"changed","status":"accepted"},"entry_id":"entry-0001","event":"entry.added","event_id":"event-0005","record_revisions":{"entry:v0.6.1/entry-0001":1,"release:v0.6.1":2},"release_version":"v0.6.1","schema_version":2}
+{"data":{"kind":"quality","status":"accepted"},"entry_id":"entry-0002","event":"entry.added","event_id":"event-0006","record_revisions":{"entry:v0.6.1/entry-0002":1,"release:v0.6.1":3},"release_version":"v0.6.1","schema_version":2}
+{"data":{"kind":"fixed","status":"accepted"},"entry_id":"entry-0003","event":"entry.added","event_id":"event-0007","record_revisions":{"entry:v0.6.1/entry-0003":1,"release:v0.6.1":4},"release_version":"v0.6.1","schema_version":2}
+{"data":{"kind":"added","status":"accepted"},"entry_id":"entry-0004","event":"entry.added","event_id":"event-0008","record_revisions":{"entry:v0.6.1/entry-0004":1,"release:v0.6.1":5},"release_version":"v0.6.1","schema_version":2}
+{"data":{"kind":"added","status":"accepted"},"entry_id":"entry-0005","event":"entry.added","event_id":"event-0009","record_revisions":{"entry:v0.6.1/entry-0005":1,"release:v0.6.1":6},"release_version":"v0.6.1","schema_version":2}
+{"data":{"added_source_refs":["git:c1d0982"],"fields":["source_refs"],"removed_source_refs":[],"source_refs_mode":"merge"},"entry_id":"entry-0003","event":"entry.updated","event_id":"event-0010","record_revisions":{"entry:v0.6.1/entry-0003":2},"release_version":"v0.6.1","schema_version":2}
+{"data":{"added_source_refs":["git:c1d0982"],"fields":["source_refs"],"removed_source_refs":[],"source_refs_mode":"merge"},"entry_id":"entry-0005","event":"entry.updated","event_id":"event-0011","record_revisions":{"entry:v0.6.1/entry-0005":2},"release_version":"v0.6.1","schema_version":2}
+{"data":{"added_source_refs":["git:94965d3"],"fields":["source_refs"],"removed_source_refs":[],"source_refs_mode":"merge"},"entry_id":"entry-0004","event":"entry.updated","event_id":"event-0012","record_revisions":{"entry:v0.6.1/entry-0004":2},"release_version":"v0.6.1","schema_version":2}
+{"data":{"released_at":"2026-08-14"},"event":"release.finalized","event_id":"event-0013","record_revisions":{"release:v0.6.1":7},"release_version":"v0.6.1","schema_version":2}

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/releases/v0.6.1/entries/entry-0001.md

@@ -0,0 +1,25 @@
+---
+schema_version: 2
+object_type: release_entry
+versioning:
+  schema_version: 1
+  revision: 1
+entry_id: entry-0001
+release_version: v0.6.1
+kind: changed
+summary: Ledgercore minimum version requirement updated to >=0.6.1
+status: accepted
+audience: null
+scopes: []
+source_refs:
+  - git:c1d0982
+paths:
+  - taskledger/compat/ledgercore.py
+issues: []
+prs: []
+sources: []
+contributors: []
+breaking: false
+internal: false
+order: 1
+---

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/releases/v0.6.1/entries/entry-0002.md

@@ -0,0 +1,25 @@
+---
+schema_version: 2
+object_type: release_entry
+versioning:
+  schema_version: 1
+  revision: 1
+entry_id: entry-0002
+release_version: v0.6.1
+kind: quality
+summary: Test suite performance improvements with atomic fast I/O and focused fixtures
+status: accepted
+audience: null
+scopes: []
+source_refs:
+  - git:94965d3
+paths:
+  - tests/conftest.py
+issues: []
+prs: []
+sources: []
+contributors: []
+breaking: false
+internal: false
+order: 2
+---

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/releases/v0.6.1/entries/entry-0003.md

@@ -0,0 +1,27 @@
+---
+schema_version: 2
+object_type: release_entry
+versioning:
+  schema_version: 1
+  revision: 2
+entry_id: entry-0003
+release_version: v0.6.1
+kind: fixed
+summary:
+  Workspace snapshot hash exclusions now resolve Taskledger state roots relative
+  to the Git root
+status: accepted
+audience: null
+scopes: []
+source_refs:
+  - git:c1d0982
+paths:
+  - taskledger/services/workspace_snapshot.py
+issues: []
+prs: []
+sources: []
+contributors: []
+breaking: false
+internal: false
+order: 3
+---

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/releases/v0.6.1/entries/entry-0004.md

@@ -0,0 +1,25 @@
+---
+schema_version: 2
+object_type: release_entry
+versioning:
+  schema_version: 1
+  revision: 2
+entry_id: entry-0004
+release_version: v0.6.1
+kind: added
+summary: Atomic index update functions for dependency and introduction indexes
+status: accepted
+audience: null
+scopes: []
+source_refs:
+  - git:94965d3
+paths:
+  - taskledger/storage/indexes.py
+issues: []
+prs: []
+sources: []
+contributors: []
+breaking: false
+internal: false
+order: 4
+---

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/releases/v0.6.1/entries/entry-0005.md

@@ -0,0 +1,25 @@
+---
+schema_version: 2
+object_type: release_entry
+versioning:
+  schema_version: 1
+  revision: 2
+entry_id: entry-0005
+release_version: v0.6.1
+kind: added
+summary: Ledgercore version inspection with module and distribution provenance tracking
+status: accepted
+audience: null
+scopes: []
+source_refs:
+  - git:c1d0982
+paths:
+  - taskledger/compat/ledgercore.py
+issues: []
+prs: []
+sources: []
+contributors: []
+breaking: false
+internal: false
+order: 5
+---

taskledger-0.6.1/.ledger/releaseledger/data/ledgers/main/releases/v0.6.1/release.md

@@ -0,0 +1,26 @@
+---
+schema_version: 2
+object_type: release
+versioning:
+  schema_version: 1
+  revision: 7
+version: v0.6.1
+status: released
+title: Release v0.6.1
+released_at: "2026-08-14"
+previous_version: v0.6.0
+cancel_reason: null
+superseded_by: null
+changelog_file: null
+boundary_ref: null
+source_refs: []
+source_count: null
+entry_count: 5
+artifact_count: 0
+git_base_ref: null
+git_base_sha: null
+git_head_ref: null
+git_head_sha: null
+git_range: null
+git_commit_count: null
+---

{taskledger-0.6.0/taskledger.egg-info → taskledger-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskledger
-Version: 0.6.0
+Version: 0.6.1
 Summary: Durable project-state storage and CLI for coding workflows
 Author: Taskledger Contributors
 Maintainer: Holger Nahrstaedt
@@ -29,6 +29,7 @@ License-File: LICENSE
 Requires-Dist: typer
 Requires-Dist: click
 Requires-Dist: PyYAML
+Requires-Dist: packaging<26,>=23
 Requires-Dist: ledgercore<0.7.0,>=0.6.1
 Requires-Dist: tomlkit<1,>=0.13
 Requires-Dist: filelock<4,>=3.16
@@ -152,8 +153,9 @@ taskledger validate check --criterion ac-0001 --status pass --evidence "pytest t
 ## Planning guidance profiles
 
 Taskledger supports project-local advisory planning guidance under
-`[prompt_profiles.planning]` in the active project config file (`taskledger.toml`
-or `.taskledger.toml` when legacy config is still present).
+`[prompt_profiles.planning]` in the active project config file
+(`.ledger/taskledger/config.toml`). Legacy `taskledger.toml` and
+`.taskledger.toml` projects remain readable only for explicit migration.
 
 ```toml
 [prompt_profiles.planning]
@@ -193,7 +195,8 @@ taskledger config set prompt_profiles.planning.question_policy always_before_pla
 
 ## Optional worker pipelines
 
-Projects may optionally configure worker pipelines in `taskledger.toml` to guide
+Projects may optionally configure worker pipelines in
+`.ledger/taskledger/config.toml` to guide
 fresh-context handoffs. Worker pipelines are advisory overlays on the existing
 planning, implementation, and validation lifecycle. They can be three steps,
 four steps, five steps, or custom. When no worker pipeline is configured, the
@@ -309,7 +312,7 @@ taskledger --root /path/to/repo init
 
 `init` writes a schema-3 `.ledger/ledger.toml` manifest and
 `.ledger/taskledger/config.toml`. Default data is external at `../ledger`; indexes
-are cache storage. Use `storage set data user-data --local` for a local override.
+are cache storage. Use `storage set data user-data --scope local` for a local override.
 
 Canonical discovery is fail-closed. Once `.ledger/ledger.toml` is found,
 Taskledger never falls back to a root `taskledger.toml`, `.taskledger.toml`, or
@@ -535,8 +538,11 @@ fresh-context transfer.
 
 ## Legacy storage layout
 
-`taskledger` keeps project-local configuration in the workspace root and durable
-records under the configured storage root. The checked-in `taskledger.toml`
+### Legacy branch-scoped layout (migration only)
+
+The following layout applies only to legacy projects without a canonical
+`.ledger/ledger.toml` manifest. New projects use the canonical Ledgercore
+layout described below. In legacy projects, checked-in `taskledger.toml`
 stores project identity plus the current branch-scoped ledger pointer and next
 task number. Operational task state remains ignored under
 `.taskledger/ledgers/<ledger_ref>/`:
@@ -650,7 +656,7 @@ Syncthing/rclone caveats.
 Use `--json` for machine-readable payloads:
 
 ```bash
-taskledger --json status --full
+taskledger --json info
 taskledger --json task active
 taskledger --json task show
 taskledger --json task show task-0001
@@ -662,13 +668,13 @@ Example status payload:
 ```json
 {
   "ok": true,
-  "command": "status",
+  "command": "info",
   "result": {
     "kind": "taskledger_status",
     "workspace_root": "/home/me/src/project-a",
-    "config_path": "/home/me/src/project-a/taskledger.toml",
-    "taskledger_dir": "/home/me/src/project-a/.taskledger",
-    "project_dir": "/home/me/src/project-a/.taskledger",
+    "config_path": "/home/me/src/project-a/.ledger/taskledger/config.toml",
+    "taskledger_dir": "/home/me/src/project-a/.ledger/taskledger",
+    "project_dir": "/home/me/src/project-a/.ledger/taskledger",
     "counts": {
       "tasks": 1,
       "introductions": 0,
@@ -692,7 +698,7 @@ Action/event logging is **enabled by default**. Taskledger writes immutable
 todo completion, validation checks, etc.) so `taskledger monitor` shows recent
 activity without extra configuration.
 
-To disable new action events, set in `taskledger.toml`:
+To disable new action events, set in `.ledger/taskledger/config.toml`:
 
 ```toml
 [event_logging]
@@ -798,7 +804,8 @@ taskledger-export-{project_slug}-{ledger_ref}-{timestamp}.tar.gz
 taskledger-task-{project_slug}-{ledger_ref}-{task_id}-{timestamp}.tar.gz
 ```
 
-`project_slug` is derived from `project_name` in `taskledger.toml`. If
+`project_slug` is derived from `project_name` in
+`.ledger/taskledger/config.toml`. If
 `project_name` is missing, taskledger falls back to the workspace directory name.
 Import safety still relies on `project_uuid`, not the name/slug.
 

{taskledger-0.6.0 → taskledger-0.6.1}/README.md

@@ -100,8 +100,9 @@ taskledger validate check --criterion ac-0001 --status pass --evidence "pytest t
 ## Planning guidance profiles
 
 Taskledger supports project-local advisory planning guidance under
-`[prompt_profiles.planning]` in the active project config file (`taskledger.toml`
-or `.taskledger.toml` when legacy config is still present).
+`[prompt_profiles.planning]` in the active project config file
+(`.ledger/taskledger/config.toml`). Legacy `taskledger.toml` and
+`.taskledger.toml` projects remain readable only for explicit migration.
 
 ```toml
 [prompt_profiles.planning]
@@ -141,7 +142,8 @@ taskledger config set prompt_profiles.planning.question_policy always_before_pla
 
 ## Optional worker pipelines
 
-Projects may optionally configure worker pipelines in `taskledger.toml` to guide
+Projects may optionally configure worker pipelines in
+`.ledger/taskledger/config.toml` to guide
 fresh-context handoffs. Worker pipelines are advisory overlays on the existing
 planning, implementation, and validation lifecycle. They can be three steps,
 four steps, five steps, or custom. When no worker pipeline is configured, the
@@ -257,7 +259,7 @@ taskledger --root /path/to/repo init
 
 `init` writes a schema-3 `.ledger/ledger.toml` manifest and
 `.ledger/taskledger/config.toml`. Default data is external at `../ledger`; indexes
-are cache storage. Use `storage set data user-data --local` for a local override.
+are cache storage. Use `storage set data user-data --scope local` for a local override.
 
 Canonical discovery is fail-closed. Once `.ledger/ledger.toml` is found,
 Taskledger never falls back to a root `taskledger.toml`, `.taskledger.toml`, or
@@ -483,8 +485,11 @@ fresh-context transfer.
 
 ## Legacy storage layout
 
-`taskledger` keeps project-local configuration in the workspace root and durable
-records under the configured storage root. The checked-in `taskledger.toml`
+### Legacy branch-scoped layout (migration only)
+
+The following layout applies only to legacy projects without a canonical
+`.ledger/ledger.toml` manifest. New projects use the canonical Ledgercore
+layout described below. In legacy projects, checked-in `taskledger.toml`
 stores project identity plus the current branch-scoped ledger pointer and next
 task number. Operational task state remains ignored under
 `.taskledger/ledgers/<ledger_ref>/`:
@@ -598,7 +603,7 @@ Syncthing/rclone caveats.
 Use `--json` for machine-readable payloads:
 
 ```bash
-taskledger --json status --full
+taskledger --json info
 taskledger --json task active
 taskledger --json task show
 taskledger --json task show task-0001
@@ -610,13 +615,13 @@ Example status payload:
 ```json
 {
   "ok": true,
-  "command": "status",
+  "command": "info",
   "result": {
     "kind": "taskledger_status",
     "workspace_root": "/home/me/src/project-a",
-    "config_path": "/home/me/src/project-a/taskledger.toml",
-    "taskledger_dir": "/home/me/src/project-a/.taskledger",
-    "project_dir": "/home/me/src/project-a/.taskledger",
+    "config_path": "/home/me/src/project-a/.ledger/taskledger/config.toml",
+    "taskledger_dir": "/home/me/src/project-a/.ledger/taskledger",
+    "project_dir": "/home/me/src/project-a/.ledger/taskledger",
     "counts": {
       "tasks": 1,
       "introductions": 0,
@@ -640,7 +645,7 @@ Action/event logging is **enabled by default**. Taskledger writes immutable
 todo completion, validation checks, etc.) so `taskledger monitor` shows recent
 activity without extra configuration.
 
-To disable new action events, set in `taskledger.toml`:
+To disable new action events, set in `.ledger/taskledger/config.toml`:
 
 ```toml
 [event_logging]
@@ -746,7 +751,8 @@ taskledger-export-{project_slug}-{ledger_ref}-{timestamp}.tar.gz
 taskledger-task-{project_slug}-{ledger_ref}-{task_id}-{timestamp}.tar.gz
 ```
 
-`project_slug` is derived from `project_name` in `taskledger.toml`. If
+`project_slug` is derived from `project_name` in
+`.ledger/taskledger/config.toml`. If
 `project_name` is missing, taskledger falls back to the workspace directory name.
 Import safety still relies on `project_uuid`, not the name/slug.
 

{taskledger-0.6.0 → taskledger-0.6.1}/docs/changelog.md

@@ -2,6 +2,27 @@
 
 > **Generated by releaseledger.** Manual edits may be overwritten. Update releaseledger entries and rebuild this file instead.
 
+## [v0.6.1] - 2026-08-14
+
+### Added
+
+- Atomic index update functions for dependency and introduction indexes
+- Ledgercore version inspection with module and distribution provenance tracking
+
+### Changed
+
+- Ledgercore minimum version requirement updated to >=0.6.1
+
+### Fixed
+
+- Workspace snapshot hash exclusions now resolve Taskledger state roots relative to the Git root
+
+### Quality
+
+- Test suite performance improvements with atomic fast I/O and focused fixtures
+
+<!-- generated by releaseledger -->
+
 ## [v0.6.0] - 2026-07-28
 
 ### Added

{taskledger-0.6.0 → taskledger-0.6.1}/docs/command_contract.md

@@ -257,9 +257,10 @@ Taskledger does not provide changelog entry, changelog context, or
 [docs/changelog.md](changelog.md) build commands; those belong to the separate `releaseledger`
 tool. Load both skills when cross-ledger release notes need task context.
 
-## Ledger commands
+## Legacy branch-scoped ledger commands (migration only)
 
-Branch-scoped ledgers isolate ignored local task state by the checked-in
+In legacy projects without a canonical manifest, branch-scoped ledgers isolate
+ignored local task state by the checked-in
 `ledger_ref` stored in `taskledger.toml`:
 
 ```bash
@@ -305,7 +306,7 @@ Rules:
 - `storage where` is read-only and reports the resolved workspace root,
   config path, `taskledger_dir`, project identity, ledger ref, Git detection,
   and active lock count.
-- `storage move` updates `taskledger.toml` atomically after the target has
+- In legacy projects, `storage move` updates `taskledger.toml` atomically after the target has
   been copied or explicitly adopted.
 - `sync preflight` performs only local checks. It must not perform network
   push/pull operations.

{taskledger-0.6.0 → taskledger-0.6.1}/docs/full_task_cycle.md

@@ -18,7 +18,7 @@ Run this once per workspace:
 ```bash
 taskledger init
 taskledger doctor
-taskledger status --full
+taskledger info
 ```
 
 `init` writes a schema-3 `.ledger/ledger.toml` registration and
@@ -287,7 +287,7 @@ taskledger task close --note "Fixed parser delimiter handling and validated pars
 taskledger release tag 0.4.2 --at-task parser-fix --note "0.4.2 released."
 taskledger task show
 taskledger task show parser-fix
-taskledger status --full
+taskledger info
 taskledger doctor
 ```
 

{taskledger-0.6.0 → taskledger-0.6.1}/docs/index.md

@@ -19,6 +19,7 @@ transfer
 sync
 service_boundary_whitelist
 documentation_freshness
+release_checklist
 changelog
 ```
 

taskledger-0.6.1/docs/release_checklist.md

@@ -0,0 +1,20 @@
+# Release checklist
+
+Build Taskledger from the intended release tag or commit in a clean
+environment. The artifact version must agree across package metadata, the
+imported module, and the CLI before publishing.
+
+```bash
+python -m build
+python -m twine check dist/*
+python -m pip install --force-reinstall dist/taskledger-0.6.1-*.whl
+taskledger --version
+python -c 'import taskledger; print(taskledger.__version__)'
+python -c 'from importlib.metadata import version; print(version("taskledger"))'
+```
+
+The clean environment must contain Ledgercore 0.6.1, and all three version
+checks must report `0.6.1`. Confirm that the wheel contains `taskledger/py.typed`
+and required runtime package files. Run the full test, lint, type, Sphinx,
+Documentledger, and SpecMason gates before changing release metadata or
+publishing artifacts.

{taskledger-0.6.0 → taskledger-0.6.1}/docs/service_boundary_whitelist.md

@@ -114,7 +114,12 @@ Current sanctioned imports:
 ## Catch-all exception whitelist (`except Exception`)
 
 Current allowed sites are listed with reasons in
-`tests/test_service_boundaries.py` under `EXCEPT_EXCEPTION_WHITELIST`.
+`tests/test_service_boundaries.py` under `EXCEPT_EXCEPTION_WHITELIST`. Each
+catch-all key uses the stable form
+`path::qualified_function:except-N`, where `N` is the ordinal of the
+catch-all handler within that function. It intentionally does not use source
+line numbers, so unrelated edits above an approved handler do not create
+policy churn.
 
 The reviewed resilience sites include storage validation, migration command
 and hook handling, and project-config parsing boundaries listed in the test
@@ -125,3 +130,5 @@ Policy intent:
 - Allow catch-all handling only in doctor/repair and resilience wrappers.
 - Block new catch-all sites unless explicitly reviewed and justified.
 - Require whitelist edits to be intentional and reasoned.
+- Fail when a new handler is added, an approved handler disappears, or a
+  function gains another catch-all handler.

{taskledger-0.6.0 → taskledger-0.6.1}/docs/sync.md

@@ -22,7 +22,8 @@ taskledger init
 taskledger storage where
 taskledger storage path data
 taskledger storage path indexes
-taskledger storage set data user-data --local --move
+taskledger storage set data user-data --scope local
+# Use `taskledger migrate` for data relocation; `storage set` changes topology only.
 ```
 
 The project UUID and Ledgercore binding keep shared projects isolated.
@@ -49,7 +50,7 @@ git clone <source-repo-url> project-a
 git clone <private-state-repo-url> taskledger-state
 
 cd project-a
-taskledger status --full
+taskledger info
 taskledger doctor
 taskledger task list
 ```

{taskledger-0.6.0 → taskledger-0.6.1}/docs/usage.md

@@ -68,7 +68,7 @@ registrations and the legacy source remain in place by default. Metadata-only ta
 are backed up and replaced atomically; authoritative split-brain targets are blocked.
 Do not create bindings or copy task directories manually.
 
-## Branch-local task work
+## Legacy branch-local task work (migration only)
 
 When creating a long-lived Git branch, fork the Taskledger ledger pointer so
 active task state, plans, todos, events, indexes, and releases stay isolated
@@ -120,10 +120,9 @@ taskledger validate check --criterion ac-0001 --status pass --evidence "pytest t
 
 Taskledger always provides built-in planning guidance via `taskledger plan guidance`.
 Project-local advisory guidance can extend this with project-specific advice. Configure
-it in the active project config file discovered for your workspace. Newer
-projects usually use `taskledger.toml`. Existing projects may still use
-`.taskledger.toml`; if both files exist, `.taskledger.toml` is discovered
-first.
+it in `.ledger/taskledger/config.toml` for canonical projects. Legacy
+`taskledger.toml` and `.taskledger.toml` files remain readable only during
+explicit migration.
 
 Configure `[prompt_profiles.planning]` in that active config:
 
@@ -200,7 +199,8 @@ harness instructions.
 
 ## Optional worker pipelines
 
-Projects may optionally configure worker pipelines in `taskledger.toml` to
+Projects may optionally configure worker pipelines in
+`.ledger/taskledger/config.toml` to
 guide fresh-context handoffs without changing the underlying task lifecycle.
 Worker pipelines are advisory overlays on the existing planning,
 implementation, and validation lifecycle. They can be three steps, four steps,
@@ -515,7 +515,7 @@ documentation updates, or follow-up implementation work.
 
 ```bash
 taskledger task export task-0030 -o task-0030.llm.md
-taskledger task export task-0030 --no-source-files -o task-0030.records.md
+taskledger task export task-0030 -o task-0030.records.md
 taskledger task export task-0030 --source-file README.md -o task-0030.llm.md
 taskledger --json task export task-0030 -o task-0030.llm.md
 ```
@@ -592,7 +592,7 @@ taskledger implement command -- ruff check --config=.ruff.toml .
 taskledger implement command --allow-failure -- python -c "raise SystemExit(7)"
 ```
 
-When `[agent_logging].enabled = true` in `taskledger.toml`, `taskledger`
+When `[agent_logging].enabled = true` in `.ledger/taskledger/config.toml`, `taskledger`
 records CLI invocations and managed command outputs. Keep logging opt-in because
 stdout/stderr may contain sensitive data. Route task-relevant commands through
 `plan command` and `implement command` so their output is included in task
@@ -643,7 +643,7 @@ taskledger implement restart --summary "Fix failed validation findings."
 ## Machine-readable output
 
 ```bash
-taskledger --json status --full
+taskledger --json info
 taskledger --json task active
 taskledger --json task show
 taskledger --json task show task-0001
@@ -656,11 +656,11 @@ taskledger --json review list --task task-0001
   "ok": true,
   "command": "status",
   "result": {
-    "kind": "taskledger_status",
+    "kind": "taskledger_info",
     "workspace_root": "/workspace",
-    "config_path": "/workspace/taskledger.toml",
-    "taskledger_dir": "/workspace/.taskledger",
-    "project_dir": "/workspace/.taskledger",
+    "config_path": "/workspace/.ledger/taskledger/config.toml",
+    "taskledger_dir": "/workspace/.ledger/taskledger",
+    "project_dir": "/workspace/.ledger/taskledger",
     "counts": {
       "tasks": 1,
       "introductions": 0,
@@ -686,7 +686,8 @@ taskledger init
 taskledger storage where
 taskledger storage path data
 taskledger storage path indexes
-taskledger storage set data user-data --local --move
+taskledger storage set data user-data --scope local
+# Use `taskledger migrate` for data relocation; `storage set` changes topology only.
 ```
 
 Default data is external at `../ledger`; indexes are checkout-specific cache data.
@@ -738,7 +739,7 @@ taskledger-export-{project_slug}-{ledger_ref}-{timestamp}.tar.gz
 taskledger-task-{project_slug}-{ledger_ref}-{task_id}-{timestamp}.tar.gz
 ```
 
-`project_slug` is derived from `project_name` in `taskledger.toml`.
+`project_slug` is derived from `project_name` in `.ledger/taskledger/config.toml`.
 If unset, taskledger falls back to the workspace directory name.
 UUID safety checks still use `project_uuid` only.
 

{taskledger-0.6.0 → taskledger-0.6.1}/pyproject.toml

@@ -1,5 +1,5 @@
 [build-system]
-requires = ["setuptools>=45", "wheel", "setuptools_scm[toml]>=6.2"]
+requires = ["setuptools>=69", "wheel", "setuptools_scm[toml]>=8.0"]
 build-backend = "setuptools.build_meta"
 
 [tool.setuptools.packages.find]
@@ -22,6 +22,7 @@ markers = [
     "slow: intentionally slower than normal unit tests",
     "subprocess: starts a child process or managed shell command",
     "git: shells out to git or requires a git repository",
+    "durable_io: verifies real flush/fsync/replace durability behavior",
 ]
 
 [project]
@@ -37,6 +38,7 @@ dependencies = [
     "typer",
     "click",
     "PyYAML",
+    "packaging>=23,<26",
     "ledgercore>=0.6.1,<0.7.0",
     "tomlkit>=0.13,<1",
     "filelock>=3.16,<4",
@@ -114,6 +116,27 @@ deps =
     pytest-xdist
 commands =
     pytest -q -n auto --dist=worksteal {posargs}
+
+[testenv:test-fast]
+deps =
+    pytest
+    pytest-xdist
+commands =
+    pytest -q -m 'unit and not slow' -n auto --dist=worksteal {posargs}
+
+[testenv:test-standard]
+deps =
+    pytest
+    pytest-xdist
+commands =
+    pytest -q -m 'not git and not subprocess and not slow' \
+        -n auto --dist=worksteal {posargs}
+
+[testenv:test-durable]
+deps =
+    pytest
+commands =
+    pytest -q -m 'durable_io' {posargs}
 """
 
 [tool.mypy]