taskledger 0.2.0__tar.gz → 0.3.0__tar.gz

{taskledger-0.2.0 → taskledger-0.3.0}/.codecrate.toml

@@ -6,7 +6,7 @@ respect_gitignore = true
 # exclude = ["*/.venv/*", "integration_tests", "examples", "docs"]
 gitignore_allow = ["taskledger/_version.py"]
 exclude = ["*/.venv/*", "integration_tests", "todo.md"]
-include = ["**/*.py", "**/*.toml", "**/*.rst", "**/*.md", "**/*.typed"]
+include = ["**/*.py", "**/*.toml", "**/*.rst", "**/*.md", "**/*.typed", "**/*.js", "**/*.css"]
 split_max_chars = 0
 manifest = false
 layout = "full"

{taskledger-0.2.0 → taskledger-0.3.0}/.pre-commit-config.yaml

@@ -64,11 +64,3 @@ repos:
         args:
           - --plugin=@prettier/plugin-xml
         files: \.(css|htm|html|js|json|jsx|less|md|scss|toml|ts|xml|yaml|yml)$
-  - repo: https://github.com/pre-commit/mirrors-eslint
-    rev: v10.2.1
-    hooks:
-      - id: eslint
-        verbose: true
-        args:
-          - --color
-          - --fix

taskledger-0.3.0/.taskledger.toml

@@ -0,0 +1,30 @@
+# Project-local taskledger configuration.
+# This file lives in the source project root.
+config_version = 2
+taskledger_dir = '.taskledger'
+
+# Stable project identity. Commit this with your source tree.
+project_uuid = "081c7c05-2d10-42b7-9b37-3d814c2f400a"
+
+# Taskledger branch-scoped state. This block is intentionally safe to commit.
+ledger_ref = "main"
+ledger_parent_ref = ""
+ledger_next_task_number = 81
+ledger_branch_guard = "off"
+
+[prompt_profiles.planning]
+profile = "balanced"
+question_policy = "ask_when_missing"
+max_required_questions = 5
+min_acceptance_criteria = 1
+todo_granularity = "implementation_steps"
+require_files = true
+require_test_commands = true
+require_expected_outputs = true
+require_validation_hints = true
+plan_body_detail = "normal"
+required_question_topics = []
+extra_guidance = ""
+
+[agent_logging]
+enabled = true

{taskledger-0.2.0 → taskledger-0.3.0}/API.md

@@ -53,6 +53,8 @@ from taskledger.errors import (
 - `project_doctor`
 - `project_export`
 - `project_import`
+- `project_export_archive`
+- `project_import_archive`
 - `project_snapshot`
 - `project_tree`
 
@@ -71,7 +73,10 @@ from taskledger.errors import (
 - `cancel_task`
 - `uncancel_task`
 - `close_task`
+- `archive_task`
+- `unarchive_task`
 - `create_follow_up_task`
+- `list_archived_task_summaries`
 - `add_requirement`
 - `remove_requirement`
 - `waive_requirement`
@@ -99,17 +104,31 @@ from taskledger.errors import (
 - `propose_plan`
 - `plan_template`
 - `upsert_plan`
+- `export_plan`
+- `amend_plan`
 - `regenerate_plan_from_answers`
 - `materialize_plan_todos`
 - `list_plan_versions`
 - `show_plan`
 - `diff_plan`
 - `lint_plan`
+- `plan_guidance`
 - `approve_plan`
 - `reject_plan`
 - `revise_plan`
 - `run_planning_command`
 
+Planning guidance API example:
+
+```python
+from pathlib import Path
+
+from taskledger.api.plans import plan_guidance
+
+payload = plan_guidance(Path.cwd(), "task-0001")
+# payload includes: kind, task_id, has_project_guidance, guidance, profile, question_policy
+```
+
 ### `taskledger.api.questions`
 
 - `add_question`

{taskledger-0.2.0 → taskledger-0.3.0}/CHANGELOG.md

@@ -1,5 +1,40 @@
 # Changelog
 
+## v0.2.0 - 2026-05-03
+
+### Added
+
+- Added `taskledger task record` for creating done tasks that represent manually completed work, with change records, evidence, and implementation summaries. Does not acquire locks or activate the task. Recorded tasks are included in release changelogs.
+- Added branch-scoped ledger state with `taskledger ledger` command group (`status`, `list`, `fork`, `switch`, `adopt`, `doctor`). Each git branch can maintain its own isolated task ledger, with `adopt` for copying branch-local task history into the current ledger.
+- Added `taskledger tree` command to render ledger and task structure with follow-up nesting, subtree filtering, release boundaries, and per-ledger release counts in both human and JSON output.
+- Added compressed export/import with a project UUID guard to prevent importing archives into the wrong project, plus archive member-count and manifest/payload size limits for safety.
+- Added `taskledger status --check` to run doctor diagnostics alongside status, keeping the default `status` fast by avoiding full record parsing.
+- Added structured diagnostics to `taskledger doctor` JSON output with task IDs, change IDs, run IDs, types, relative paths, and actionable repair hints.
+- Added explicit `repair` command for existing planning-command change records that were incorrectly persisted as code changes.
+- Added a top-level `Makefile` with a `release-check` automation target (compile, test, lint, type-check, build, twine check).
+- Added AST-based service boundary guardrail tests with explicit whitelists and documented rationale.
+
+### Changed
+
+- Split core plan/implement/validate service entrypoints from `tasks.py` into dedicated `planning_flow.py`, `implementation_flow.py`, and `validation_flow.py` modules. `tasks.py` remains a compatibility facade.
+- Decoupled validation service from private task helpers by extracting shared query logic into a new `task_queries` module.
+- Planning commands are now persisted as planning-run evidence (worklog/artifacts/event) instead of creating `CodeChangeRecord` entries.
+- Replaced chmod-dependent storage write failure test with a deterministic synthetic `OSError` monkeypatch.
+- Sped up test suite with test-only fast fsync bypass, command-runner seam, and reduced subprocess-heavy setup.
+
+### Fixed
+
+- Fixed import replace so it no longer restores stale locks across machines.
+
+### Documentation
+
+- Documented branch-scoped ledger workflow, `task record` usage and warnings, `tree` command, and `make release-check` across README, RST docs, API docs, and the taskledger skill.
+- Added `docs/service_boundary_whitelist.md` documenting temporary module/function boundary whitelist entries and split targets.
+
+### Quality
+
+- Expanded regression coverage for branch-scoped ledgers, task record, tree command, compressed export/import, doctor diagnostics, status performance, service boundaries, and planning command persistence. Repo-wide pytest, ruff, and mypy passed.
+
 ## v0.1.2 - 2026-04-30
 
 ### Fixed

{taskledger-0.2.0/taskledger.egg-info → taskledger-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskledger
-Version: 0.2.0
+Version: 0.3.0
 Summary: Durable project-state storage and CLI for coding workflows
 Author: Taskledger Contributors
 Maintainer: Holger Nahrstaedt
@@ -82,6 +82,53 @@ The supported command surface is organized as:
 
 - `init`, `status`, `export`, `import`, `snapshot`, `release`
 
+### Which read command to use
+
+| Need                       | Command                                             |
+| -------------------------- | --------------------------------------------------- |
+| Next step                  | `next-action`                                       |
+| Next implementation item   | `todo next`                                         |
+| Active task summary        | `task show`                                         |
+| Specific task summary      | `task show TASK_REF` or `task show --task TASK_REF` |
+| Project/ledger overview    | `status`, `tree`                                    |
+| Human dashboard            | `serve`                                             |
+| Reviewable markdown report | `task report`                                       |
+| Fresh worker context       | `context` or durable `handoff show`                 |
+| Command audit              | `task transcript`                                   |
+
+## 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).
+
+```toml
+[prompt_profiles.planning]
+profile = "strict"
+question_policy = "always_before_plan"
+max_required_questions = 3
+min_acceptance_criteria = 2
+todo_granularity = "atomic"
+require_files = true
+require_test_commands = true
+require_expected_outputs = true
+require_validation_hints = true
+plan_body_detail = "detailed"
+required_question_topics = ["scope", "compatibility", "test strategy"]
+extra_guidance = "Every plan must mention docs, tests, and rollback or repair behavior."
+```
+
+Inspect guidance for the active task:
+
+```bash
+taskledger plan guidance
+taskledger --json plan guidance
+```
+
+This guidance is advisory and cannot override lifecycle gates, user approval,
+validation requirements, lock rules, or higher-priority harness instructions.
+See `docs/usage.rst` for the full key reference and workflow details.
+
 ## Install
 
 ```bash
@@ -137,6 +184,16 @@ taskledger validate check --criterion ac-0001 --status pass --evidence "pytest -
 taskledger validate finish --result passed --summary "Validated the rewrite."
 ```
 
+To revise a proposed plan, re-enter planning and edit an exported workspace
+copy. Never edit `.taskledger/` files directly:
+
+```bash
+taskledger plan revise
+taskledger plan export --version latest --file ./plan.md
+# edit ./plan.md
+taskledger plan upsert --file ./plan.md
+```
+
 For manually completed work (e.g., manual testing, operations tasks, or work
 completed outside the task-first lifecycle), use `task record` to create a
 done task directly without acquiring lifecycle locks. **Note**: `task record`
@@ -148,6 +205,17 @@ taskledger task record "Deploy to production" --summary "Deployed v0.4.1 to prod
 taskledger task record "Manual API testing" --summary "Tested new endpoints" --allow-empty-record --reason "Exploratory testing, no formal changes tracked"
 ```
 
+Archive is a visibility operation: it hides tasks from default list/tree/dashboard
+views without deleting history. Task ids stay monotonic and are never reused.
+Slugs can be reused after archive.
+
+```bash
+taskledger task archive task-0030 --reason "Hide historical task"
+taskledger task list --archived
+taskledger task unarchive task-0030 --reason "Need to continue work" --slug task-0030-reopened
+taskledger tree --include-archived
+```
+
 If validation finds an implementation bug, keep the accepted plan and restart
 implementation explicitly:
 
@@ -340,6 +408,7 @@ Use `--json` for machine-readable payloads:
 taskledger --json status --full
 taskledger --json task active
 taskledger --json task show
+taskledger --json task show task-0001
 taskledger --json context --for validation --format json
 ```
 
@@ -441,11 +510,28 @@ for task-first handoff guidance.
 ## Export, import, and snapshots
 
 ```bash
-taskledger export ./taskledger-transfer.tar.gz
+taskledger init --project-name "Taskledger"
+taskledger export
+taskledger import ./taskledger-transfer.tar.gz --dry-run
 taskledger import ./taskledger-transfer.tar.gz --replace
 taskledger snapshot ./artifacts
 ```
 
+Default export filenames use this policy:
+
+```text
+taskledger-export-{project_slug}-{ledger_ref}-{timestamp}.tar.gz
+```
+
+`project_slug` is derived from `project_name` in `taskledger.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.
+
+`--include-bodies` and `--include-run-artifacts` now change archive content:
+
+- `--no-include-bodies` strips record body text (`body` / `context_body`) from exported payloads.
+- `--include-run-artifacts` embeds task and agent-log artifact files under `artifacts/` in the archive.
+
 Cross-machine imports preserve durable task/run data, but imported runtime locks
 are quarantined by default. After importing an in-progress implementation,
 run:

{taskledger-0.2.0 → taskledger-0.3.0}/README.md

@@ -39,6 +39,53 @@ The supported command surface is organized as:
 
 - `init`, `status`, `export`, `import`, `snapshot`, `release`
 
+### Which read command to use
+
+| Need                       | Command                                             |
+| -------------------------- | --------------------------------------------------- |
+| Next step                  | `next-action`                                       |
+| Next implementation item   | `todo next`                                         |
+| Active task summary        | `task show`                                         |
+| Specific task summary      | `task show TASK_REF` or `task show --task TASK_REF` |
+| Project/ledger overview    | `status`, `tree`                                    |
+| Human dashboard            | `serve`                                             |
+| Reviewable markdown report | `task report`                                       |
+| Fresh worker context       | `context` or durable `handoff show`                 |
+| Command audit              | `task transcript`                                   |
+
+## 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).
+
+```toml
+[prompt_profiles.planning]
+profile = "strict"
+question_policy = "always_before_plan"
+max_required_questions = 3
+min_acceptance_criteria = 2
+todo_granularity = "atomic"
+require_files = true
+require_test_commands = true
+require_expected_outputs = true
+require_validation_hints = true
+plan_body_detail = "detailed"
+required_question_topics = ["scope", "compatibility", "test strategy"]
+extra_guidance = "Every plan must mention docs, tests, and rollback or repair behavior."
+```
+
+Inspect guidance for the active task:
+
+```bash
+taskledger plan guidance
+taskledger --json plan guidance
+```
+
+This guidance is advisory and cannot override lifecycle gates, user approval,
+validation requirements, lock rules, or higher-priority harness instructions.
+See `docs/usage.rst` for the full key reference and workflow details.
+
 ## Install
 
 ```bash
@@ -94,6 +141,16 @@ taskledger validate check --criterion ac-0001 --status pass --evidence "pytest -
 taskledger validate finish --result passed --summary "Validated the rewrite."
 ```
 
+To revise a proposed plan, re-enter planning and edit an exported workspace
+copy. Never edit `.taskledger/` files directly:
+
+```bash
+taskledger plan revise
+taskledger plan export --version latest --file ./plan.md
+# edit ./plan.md
+taskledger plan upsert --file ./plan.md
+```
+
 For manually completed work (e.g., manual testing, operations tasks, or work
 completed outside the task-first lifecycle), use `task record` to create a
 done task directly without acquiring lifecycle locks. **Note**: `task record`
@@ -105,6 +162,17 @@ taskledger task record "Deploy to production" --summary "Deployed v0.4.1 to prod
 taskledger task record "Manual API testing" --summary "Tested new endpoints" --allow-empty-record --reason "Exploratory testing, no formal changes tracked"
 ```
 
+Archive is a visibility operation: it hides tasks from default list/tree/dashboard
+views without deleting history. Task ids stay monotonic and are never reused.
+Slugs can be reused after archive.
+
+```bash
+taskledger task archive task-0030 --reason "Hide historical task"
+taskledger task list --archived
+taskledger task unarchive task-0030 --reason "Need to continue work" --slug task-0030-reopened
+taskledger tree --include-archived
+```
+
 If validation finds an implementation bug, keep the accepted plan and restart
 implementation explicitly:
 
@@ -297,6 +365,7 @@ Use `--json` for machine-readable payloads:
 taskledger --json status --full
 taskledger --json task active
 taskledger --json task show
+taskledger --json task show task-0001
 taskledger --json context --for validation --format json
 ```
 
@@ -398,11 +467,28 @@ for task-first handoff guidance.
 ## Export, import, and snapshots
 
 ```bash
-taskledger export ./taskledger-transfer.tar.gz
+taskledger init --project-name "Taskledger"
+taskledger export
+taskledger import ./taskledger-transfer.tar.gz --dry-run
 taskledger import ./taskledger-transfer.tar.gz --replace
 taskledger snapshot ./artifacts
 ```
 
+Default export filenames use this policy:
+
+```text
+taskledger-export-{project_slug}-{ledger_ref}-{timestamp}.tar.gz
+```
+
+`project_slug` is derived from `project_name` in `taskledger.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.
+
+`--include-bodies` and `--include-run-artifacts` now change archive content:
+
+- `--no-include-bodies` strips record body text (`body` / `context_body`) from exported payloads.
+- `--include-run-artifacts` embeds task and agent-log artifact files under `artifacts/` in the archive.
+
 Cross-machine imports preserve durable task/run data, but imported runtime locks
 are quarantined by default. After importing an in-progress implementation,
 run:

{taskledger-0.2.0 → taskledger-0.3.0}/docs/api.rst

@@ -32,6 +32,8 @@ Project API
 - ``project_doctor``
 - ``project_export``
 - ``project_import``
+- ``project_export_archive``
+- ``project_import_archive``
 - ``project_snapshot``
 - ``project_tree``
 
@@ -51,7 +53,10 @@ Task API
 - ``cancel_task``
 - ``uncancel_task``
 - ``close_task``
+- ``archive_task``
+- ``unarchive_task``
 - ``create_follow_up_task``
+- ``list_archived_task_summaries``
 - ``add_requirement``
 - ``remove_requirement``
 - ``waive_requirement``
@@ -80,10 +85,13 @@ Plan API
 - ``propose_plan``
 - ``plan_template``
 - ``upsert_plan``
+- ``export_plan``
+- ``amend_plan``
 - ``list_plan_versions``
 - ``show_plan``
 - ``diff_plan``
 - ``lint_plan``
+- ``plan_guidance``
 - ``approve_plan``
 - ``reject_plan``
 - ``revise_plan``
@@ -91,6 +99,15 @@ Plan API
 - ``materialize_plan_todos``
 - ``run_planning_command``
 
+Planning guidance example:
+
+.. code-block:: python
+
+   from pathlib import Path
+   from taskledger.api.plans import plan_guidance
+
+   payload = plan_guidance(Path.cwd(), "task-0001")
+
 Question API
 ------------
 

{taskledger-0.2.0 → taskledger-0.3.0}/docs/command_contract.rst

@@ -20,8 +20,8 @@ should prefer ``--root``.
 Task Scoping
 ------------
 
-Task-scoped commands default to the active task. Use ``--task TASK_REF`` only
-when explicitly targeting another task.
+Task-scoped workflow commands default to the active task. Use
+``--task TASK_REF`` when explicitly targeting another task.
 
 .. code-block:: bash
 
@@ -32,7 +32,57 @@ when explicitly targeting another task.
    taskledger implement finish --task task-0001 --summary "Implemented."
    taskledger validate status --task task-0001
 
-Optional positional task refs are not supported.
+Task-resource commands accept the task as their direct positional resource:
+
+.. code-block:: bash
+
+   taskledger task show task-0001
+   taskledger task cancel task-0001 --reason "Duplicate"
+   taskledger task archive task-0001 --reason "Hide historical task"
+   taskledger task unarchive task-0001 --reason "Restore task"
+   taskledger task report task-0001
+
+Optional positional task refs are not supported for workflow commands.
+
+Plan guidance command
+---------------------
+
+``taskledger plan guidance`` is a read-only planning helper command:
+
+.. code-block:: bash
+
+   taskledger plan guidance [--task TASK_REF] [--format markdown|json]
+
+Rules:
+
+* defaults to the active task when ``--task`` is omitted;
+* ``--format`` accepts only ``markdown`` or ``json``;
+* when a planning run is active, it records a one-time guidance-view marker for
+  that run and appends a ``plan.guidance.viewed`` event;
+* root ``--json`` continues to return the standard CLI success/error envelope.
+
+The command payload shape is:
+
+* ``kind``
+* ``task_id``
+* ``has_project_guidance``
+* ``guidance``
+* ``profile``
+* ``question_policy``
+
+Plan revision commands
+----------------------
+
+``taskledger plan export`` renders an editable plan draft outside durable
+storage, and ``taskledger plan amend`` applies structured plan-review edits:
+
+.. code-block:: bash
+
+   taskledger plan export [--task TASK_REF] [--version latest|N] [--file PATH] [--overwrite] [--stdout]
+   taskledger plan amend [--task TASK_REF] [--drop-criterion CRITERION_ID ...] [--drop-todo TODO_ID ...] [--remove-file PATH ...] --reason "..."
+
+Plan proposal commands that accept ``--file`` reject file paths under
+``.taskledger/`` because that directory is private durable ledger state.
 
 Archive import lock policy
 --------------------------
@@ -47,6 +97,31 @@ The default is ``quarantine`` so imported source-machine runtime locks are not
 restored as active ``lock.yaml`` files. ``keep`` is diagnostic-only behavior
 for full-fidelity lock restoration.
 
+Transfer archive manifest contract
+----------------------------------
+
+Transfer archives include both machine identity and human-readable metadata:
+``manifest.project.name`` and ``manifest.project.slug`` are display metadata,
+while ``manifest.project.uuid`` remains the safety identity.
+
+.. code-block:: json
+
+   {
+     "project": {
+       "uuid": "<project_uuid>",
+       "name": "<project_name>",
+       "slug": "<project_slug>",
+       "ledger_ref": "<ledger_ref>"
+     }
+   }
+
+Import compatibility is backward-safe: older archives that only contain
+``project.uuid`` and ``project.ledger_ref`` remain valid. UUID comparison is
+still authoritative for import safety.
+
+``taskledger import --dry-run`` must not mutate taskledger state for either
+archive or JSON payload imports.
+
 Positional Resource Refs
 ------------------------
 
@@ -138,6 +213,8 @@ and may also include:
 * ``template_command`` plus ``required_plan_fields`` and
   ``recommended_plan_fields`` when the next step is regenerating a plan from
   answered questions
+* ``guidance_command`` when planning guidance should be reviewed before drafting
+  or regenerating a plan
 
 Agents should inspect ``next_item``, prefer ``next_command`` when it is safe,
 avoid inventing question answers, and never mark todos done without evidence.
@@ -153,7 +230,8 @@ latest implementation run and no active lock, it should direct agents to
 For an approved task with a non-implementation run still marked running,
 ``next-action`` must not direct agents to ``taskledger implement start``.
 It should report a repair-oriented action and point to ``taskledger doctor``.
-Truly cancelled tasks recover through ``taskledger task uncancel --reason "..."``
+Truly cancelled tasks recover through
+``taskledger task uncancel --task TASK_REF --reason "..."``
 
 Compact mutation output
 ........................
@@ -188,6 +266,40 @@ to a durable non-active stage rather than directly re-entering an active stage.
 Run and lock repair
 -------------------
 
+Managed command wrappers
+------------------------
+
+``plan command`` and ``implement command`` mirror the inner command exit code by
+default.
+
+Use ``--allow-failure`` when you intentionally want to record a non-zero inner
+exit code while returning wrapper exit code ``0``:
+
+.. code-block:: bash
+
+   taskledger plan command -- pytest tests/ -q
+   taskledger plan command --allow-failure -- pytest tests/ -q
+   taskledger implement command -- ruff check --config=.ruff.toml .
+   taskledger implement command --allow-failure -- python -c "raise SystemExit(7)"
+
+Transcript review modes
+-----------------------
+
+``task transcript`` defaults to review mode, which groups wrapper +
+managed-shell pairs, highlights failures and wrapper/managed mismatches, and
+flags late lifecycle commands. Raw per-record audit table is available with
+``--raw``::
+
+.. code-block:: bash
+
+   taskledger task transcript --task TASK_REF
+   taskledger task transcript --task TASK_REF --raw
+   taskledger task transcript --task TASK_REF --failures
+
+``--review`` is the default (no flag needed). ``--raw`` shows every record
+without collapsing. ``--failures`` renders only failed command rows and retry
+detection. ``--raw``, ``--review``, and ``--failures`` are mutually exclusive.
+
 ``taskledger doctor`` and ``taskledger doctor locks`` report running runs without
 matching active locks. Orphaned running planning runs can be finished only
 through an explicit repair command with a reason:

{taskledger-0.2.0 → taskledger-0.3.0}/docs/full_task_cycle.rst

@@ -126,8 +126,9 @@ inspection), preserve their output with ``plan command``:
    taskledger plan command -- pytest tests/test_parser.py -q
    taskledger plan command -- python -m compileall taskledger
 
-``plan command`` records the command exit code and output as a change record
-attached to the planning run. Use it to build evidence into the plan before
+``plan command`` records command exit code and output in planning diagnostics.
+With transcript logging enabled, the same output is also captured in the
+ledger-level command transcript. Use it to build evidence into the plan before
 proposal.
 
 6. Materialize Todos And Approve
@@ -178,8 +179,9 @@ Begin implementation and keep durable notes as work progresses:
    taskledger implement status
 
 Use ``implement command`` when you want taskledger to record a command run as
-part of implementation. Use ``implement deviation`` when the implementation
-differs from the approved plan.
+part of implementation. With transcript logging enabled, it also records managed
+stdout/stderr in the task transcript. Use ``implement deviation`` when the
+implementation differs from the approved plan.
 
 Fresh-worker implementation
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -282,6 +284,7 @@ After validation passes, close the task and inspect final state:
    taskledger task close --note "Fixed parser delimiter handling and validated parser regressions."
    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 doctor
 
@@ -318,7 +321,7 @@ cycle:
    taskledger doctor locks
    taskledger lock break --reason "Recover stale planning lock."
    taskledger implement resume --reason "Reacquire implementation lock for existing running run."
-   taskledger task uncancel --reason "Restore the task to a safe durable stage."
+   taskledger task uncancel --task TASK_REF --reason "Restore the task to a safe durable stage."
    taskledger repair index
    taskledger repair task --reason "Inspect task record after manual edit."
    taskledger reindex

{taskledger-0.2.0 → taskledger-0.3.0}/docs/index.rst

@@ -17,6 +17,7 @@ Contents
    api
    public_surface
    command_contract
+   transfer
 
 Indices and tables
 ------------------

{taskledger-0.2.0 → taskledger-0.3.0}/docs/public_surface.rst

@@ -42,6 +42,12 @@ plan subcommands
 - ``plan start``, ``plan propose``, ``plan template``, ``plan upsert``, ``plan lint``, ``plan approve``, ``plan accept``, ``plan reject``, ``plan show``, ``plan diff``
 - ``plan regenerate --from-answers``, ``plan materialize-todos``, ``plan command -- ...``
 
+task reporting and transcripts
+------------------------------
+
+- ``task report`` supports section control including ``--include command-log``
+- ``task transcript`` renders a per-task command transcript in ``markdown`` or ``json``
+
 todo subcommands
 ----------------