Skip to content

plan update-step silently ignores --file, --test, and --doc evidence fields #692

Closed

Description

@unbraind

Summary

pm plan update-step and pm plan complete-step accept --file, --test, and --doc options, report success, and update the step timestamp/evidence, but do not persist the supplied linked evidence on an already-completed step.

Reproduction

Using pm CLI 2026.7.24-3:

pm plan update-step pm-example plan-step-003 \
  --file "path=src/feature.ts,scope=project,note=Implementation" \
  --test "command=bun run test -- tests/feature.test.ts,path=tests/feature.test.ts,note=Coverage" \
  --force
pm plan show pm-example --depth deep

The command exits successfully and changes updated_at, but the step retains only its previous files and tests. Repeating with pm plan complete-step has the same result.

Expected

The evidence flags should append or upsert linked evidence consistently for pending, active, and completed steps, or the CLI should reject unsupported state/field combinations with an actionable error. Silent success makes PM delivery evidence incomplete and is hard to detect.

Duplicate search

Searched all-state repository issues for plan update-step file test completed evidence, completed step linked files tests ignored, plan update-step linked file test, and plan completed step evidence file test; no matching issue was found.

Activity

  1. coderabbitai commented on Jul 25, 2026

    @coderabbitai
    🔗 Related PRs

    #51 - Polish CLI ergonomics, delete safety, and templates dedup [closed]
    #200 - Add validation self-repair and agent ergonomics primitives [closed]
    #291 - feat(update): allow audit evidence appends [merged]
    #512 - Expose governed plan workflows through the public SDK [merged]
    #545 - SDK contract integrity: workspace paths, dependency truth, validation, and MCP parity [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. unbraind commented on Jul 25, 2026

    @unbraind
    OwnerAuthor

    Tracked as pm-z5vamp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions