Skip to content

fix: keep document updates within the active workflow - #169

Merged
shinpr merged 1 commit into
mainfrom
fix/update-doc-execution-boundary
Aug 26, 2026
Merged

fix: keep document updates within the active workflow#169
shinpr merged 1 commit into
mainfrom
fix/update-doc-execution-boundary

Conversation

@shinpr

@shinpr shinpr commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • Keep in-flow requirement changes in the orchestrator-owned convergence record instead of forcing a requirement-analyzer rerun.
  • Resume from the earliest invalidated gate while preserving outputs that remain valid.
  • Restart document design only when the requirement change invalidates an approved requirement, contract, data flow, verification strategy, or task boundary.
  • Bump the bundled plugin version to 0.24.9.

Why

Document updates already have an authorized target and requested outcome. Forcing them through fresh requirement analysis introduces unrelated scope and cost evaluation before applying the requested change.

Verification

  • pnpm sync:check
  • pnpm check:skills-index
  • git diff --check
  • claude plugin validate .claude-plugin/marketplace.json
  • claude plugin validate dev-workflows
  • claude plugin validate dev-workflows-frontend
  • claude plugin validate dev-workflows-fullstack
  • claude plugin validate dev-skills

@shinpr shinpr self-assigned this Aug 26, 2026
@shinpr
shinpr merged commit 87fd2ae into main Aug 26, 2026
1 check passed
@shinpr
shinpr deleted the fix/update-doc-execution-boundary branch August 26, 2026 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant