Standardize CLI terminal output: separator widths and missing emojis

[Copilot]

• Standardize summary separator width from 50 → 40 across 8 files to match printBanner width convention
• Standardize status.go separator width from 42 → 40 for consistency
• Fix status.go indented separator: " " + Repeat("─", 38) so total visible width = 40
• Add emojis to section headers in cleanup.go — 📋 Deployment found, 🗑️ Resources to delete, 🌐 Endpoints that will be removed
• Add emoji to section header in deploy_azure.go — 📋 Configuration
• Add trailing blank lines after closing separators in configure_projects.go, configure_full.go (both branches) per terminal output standards
• Verify build and tests still pass
• Code review passed
• CodeQL security scan passed (0 alerts)

Original prompt

Can you please do a detailed analysis and generate a report of any improvement we can make to the CLI UX/TUI? Is spacing and indentation appropritate? Anywhere we can safely add emojis? How to make it more readable?

Custom agent used: prettify
Terminal UX specialist — enforces output formatting rules, improves readability, and ensures consistent visual rhythm across all CLI commands.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Standardizes the CLI’s terminal output formatting to better match the repository’s terminal UX conventions by aligning summary separator widths and adding emoji-prefixed section headers where they were missing.

Changes:

• Normalize summary separators from 50 to 40 characters across multiple configure/status flows.
• Add emoji prefixes to previously plain section headers in Azure deploy/cleanup output.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
cmd/status.go	Adjusts the status section separator width to 40.
cmd/deploy_azure.go	Adds 📋 emoji to the “Configuration” header.
cmd/configure_scope_delete.go	Updates summary separator width to 40.
cmd/configure_scope_add.go	Updates summary separator width to 40.
cmd/configure_projects.go	Updates project finalization summary separator width to 40.
cmd/configure_project_delete.go	Updates delete summary separator width to 40.
cmd/configure_full.go	Updates connection-setup summary separator widths to 40.
cmd/configure_connection_update.go	Updates update summary separator width to 40.
cmd/configure_connection_delete.go	Updates delete summary separator width to 40.
cmd/configure_connection_add.go	Updates add summary separator width to 40.
cmd/cleanup.go	Adds emoji-prefixed headers for deployment/resources/endpoints sections.

[Copilot]

This summary block ends with a closing separator and then returns without printing a trailing blank line. Terminal Output Standards recommend a blank line after separators so the shell prompt (or subsequent output) doesn’t jam against the separator. Consider printing a final blank line after the closing separator here.

Suggested change

	fmt.Println(strings.Repeat("\u2500", 40))
	fmt.Println(strings.Repeat("\u2500", 40))
	fmt.Println()

[Copilot]

In the len(results) == 0 branch, the summary separator block ends and the function returns an error immediately. Per Terminal Output Standards (blank line after separators), this will cause the subsequent error message printed by Execute() to appear directly under the separator with no breathing room. Add an extra blank line after the closing separator (or ensure the next output starts with a blank line) before returning.

Suggested change

	fmt.Println(strings.Repeat("─", 40))
	fmt.Println(strings.Repeat("─", 40))
	fmt.Println()

[ewega]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied both review suggestions in 95ebf11 — added fmt.Println() after the closing separator in configure_projects.go:356 (finalizeProject) and configure_full.go:173 (no-connections error branch) so the shell prompt / error output doesn't jam against the separator.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

[Copilot]

sep is built as two leading spaces plus 40 box-drawing characters, so the visible separator line is 42 chars wide. If the goal is to standardize separators to 40 (matching the banner width convention), either drop the indent or reduce the repeat count so the total width is 40.

Suggested change

	sep := " " + strings.Repeat("─", 40)
	sep := " " + strings.Repeat("─", 38)

[Copilot]

The success summary returns immediately after printing the closing separator, so there’s no trailing blank line. Terminal output standards require a blank line after separators; add a final empty line after the closing separator here as well (matching the len(results)==0 branch).

Suggested change

	fmt.Println(strings.Repeat("─", 40))
	fmt.Println(strings.Repeat("─", 40))
	fmt.Println()

[ewega]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied both review suggestions in 17ea180:

• cmd/status.go:83: Changed Repeat("─", 40) → Repeat("─", 38) so the 2-space indent + 38 box-drawing chars = 40 total visible width.
• cmd/configure_full.go:187: Added fmt.Println() after the success-path closing separator to match the error branch.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated no new comments.