Restore from cli.__version__ import __version__ in cli/__init__.py; add init wizard sanity CI step

[Copilot]

This pull request includes several improvements and fixes across documentation, workflow configuration, and frontend styles. The main changes are grouped below:

Documentation and Versioning:

• Added a version badge for 0.2.0 to the top of the README.md for clearer version visibility.
• Updated CLI usage examples in README.md to include Kubernetes deployment instructions.
• Changed the way __version__ is imported in cli/__init__.py for better maintainability.
• Removed the lengthy test run output from docs/CLI-TEST-REPORT.md to keep documentation concise.

Continuous Integration:

• Added a new CLI init wizard scenario to the sanity.yml workflow, ensuring the CLI initialization process is tested in CI.

Frontend/CSS Fixes:

• Fixed all CSS custom property references in feature-announcements/announcement.html from the invalid – (en dash) to the correct -- (double hyphen), resolving color and style issues throughout the announcement page. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25]

These changes improve code quality, documentation clarity, CI reliability, and frontend appearance.Two regressions introduced during the merge conflict resolution with main:

cli/__init__.py — version import reverted to inline duplicate

The merge conflict resolution replaced the canonical import with an inline definition, breaking the single-source-of-truth contract:

# broken (post-merge)
__version__ = "0.2.0"

# restored
from cli.__version__ import __version__

sanity.yml — devopsos init had no dedicated CI scenario

The init wizard was only swept in by the broad final "CLI integration tests" step. Added an explicit scenario so init failures surface with per-feature granularity, matching the pattern of every other scenario in the workflow:

- name: "Scenario: CLI init wizard"
  run: pytest cli/test_cli.py -k init -v

Covers: --help option visibility, --dir placement, Space-to-toggle instruction on checkboxes, and wizard selections written to devcontainer.env.json.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.