Skip to content

fix: use consistent status labels in update reports - #331

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/consistent-update-status
Sep 8, 2026
Merged

Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/consistent-update-status

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

Summary

  • Use one plain-language Status column across the main Amplifier update report, Modules (local and cached), and Bundles sections.
  • Reuse the existing SourceReportState vocabulary, preserving update classification, action eligibility, execution, source inventory, and bundle behavior.
  • Remove the obsolete symbol legend from concise and verbose reports; leave utils/display.py and the standalone amplifier module update command unchanged.

Verification

  • Focused suite: 83 passed using the existing CLI virtualenv with offline, credential-scrubbed environment settings.
  • Prior full suite evidence on the same base: 2075 passed, 3 skipped, 13 deselected, 1 xfailed.
  • Reviewed mocked-boundary terminal captures at 80- and 120-column widths for concise and verbose output; no live update, network, LLM, or DTU claims.
  • Independent reviewer: PASS.

Scope

  • Exactly three files: AGENTS.md, amplifier_app_cli/commands/update.py, and tests/test_update_reporting.py.
  • Diff: 243 insertions, 56 deletions.
  • Tests cover word labels, shared status vocabulary, concise/verbose output, no legend, and unchanged execution behavior.

Breaking changes

None expected.

Generated with Amplifier

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
@bkrabach
Brian Krabach (bkrabach) merged commit 80312f7 into main Sep 8, 2026
9 checks passed
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.

2 participants