feat: support --iteration-id in story update

[huangdijia]

Summary

• add --iteration-id to tapd story update
• pass the iteration id through to UpdateStoryRequest
• add tests and a README example

Background

• the TAPD SDK already supports UpdateStoryRequest.IterationID, but the CLI did not expose it on tapd story update

Changes

• register --iteration-id on the story update command
• include IterationID when building the update request
• verify help/spec output and request mapping in tests

Test Plan

• run go test ./...

Risks

• only supports setting or changing an iteration id
• does not add a separate clear-iteration flow

#1

[Copilot]

Pull request overview

This PR exposes TAPD SDK’s UpdateStoryRequest.IterationID through the CLI by adding --iteration-id to tapd story update, wiring it into the update request, and documenting/validating the behavior with tests and a README example.

Changes:

• Register --iteration-id on tapd story update.
• Pass flagIterationID into model.UpdateStoryRequest.IterationID.
• Add tests for spec output / flag registration / request mapping, plus a README usage example.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
internal/cmd/story.go	Adds --iteration-id to story update and maps it to UpdateStoryRequest.IterationID.
internal/cmd/story_test.go	Adds tests validating help/spec includes the flag and that update requests send iteration_id.
README.md	Documents updating a story while switching iteration via --iteration-id.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.