README lists non-existent `deploy` and `config` commands, missing `logs` command

[Yogeshp-MSFT]

Description

The README Features section lists commands that don't exist in the CLI, and is missing one that does.

CLI version tested: v1.1.184 (latest stable, 2026-05-19)

Commands listed in README but NOT in CLI

README Entry	Result of running command
deploy — "Deploy Agent 365 application binaries to the configured Azure App Service and update Agent 365 Tool permissions"	a365 deploy shows root help — command does not exist
config — "Configure Azure subscription, resource settings, and deployment options for Agent 365 CLI commands"	a365 config shows root help — command does not exist

The official CLI reference at https://learn.microsoft.com/en-us/microsoft-agent-365/developer/reference/cli does not list deploy or config either, confirming these are README-only references.

Note: The deploy-to-Azure docs correctly instruct users to use az webapp deploy — there is no a365 deploy equivalent.

Command exists in CLI but MISSING from README

Command	CLI Help	Microsoft Learn Docs
logs (a365 logs export)	✅ Works — exports redacted diagnostic logs safe for Microsoft support	✅ Documented

Suggested Fix

In the README Features section:

1. Remove the deploy bullet
2. Remove the config bullet
3. Add a logs bullet: **logs**: Export redacted CLI diagnostic logs safe to share with Microsoft support

Steps to Reproduce

a365 --version   # 1.1.184+3e624511bc
a365 deploy      # Shows root help (not a recognized command)
a365 config      # Shows root help (not a recognized command)
a365 logs --help # Shows valid help for logs command

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'documentation' because the issue pertains to inaccuracies in the README file, which is part of the project's documentation.
Priority: Assigned P2 because the incorrect and missing information in the README could mislead users and cause confusion, but it does not directly affect the functionality of the software.
Copilot: This issue involves updating the README to correct and align the listed commands with the actual CLI functionality. It is a well-scoped, documentation-only change with clear instructions, making it highly suitable for Copilot.
Assignment: Issue is suitable for Copilot automated fix. This issue involves updating the README to correct and align the listed commands with the actual CLI functionality. It is a well-scoped, documentation-only change with clear instructions, making it highly suitable for Copilot.
Labels: Applied labels documentation, P2 based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: documentation
Priority: P2
Confidence: 100.0%

Recommended Assignee: @copilot

Analysis:
type rationale: Classified as 'documentation' because the issue pertains to inaccuracies in the README file, which is part of the project's documentation.

priority rationale: Assigned P2 because the incorrect and missing information in the README could mislead users and cause confusion, but it does not directly affect the functionality of the software.

copilot rationale: This issue involves updating the README to correct and align the listed commands with the actual CLI functionality. It is a well-scoped, documentation-only change with clear instructions, making it highly suitable for Copilot.

assignment rationale: Issue is suitable for Copilot automated fix. This issue involves updating the README to correct and align the listed commands with the actual CLI functionality. It is a well-scoped, documentation-only change with clear instructions, making it highly suitable for Copilot.

labels rationale: Applied labels documentation, P2 based on issue type and priority

[OK] This issue appears to be Copilot-fixable!

[SUGGESTION] Suggested Approach

1. Update the README file in the root directory (`README.md`) to remove the `deploy` and `config` commands from the Features section. Replace them with an entry for the `logs` command, such as: `**logs**: Export redacted CLI diagnostic logs safe to share with Microsoft support`.
2. Cross-check the CLI commands listed in the README against the official CLI reference documentation at https://learn.microsoft.com/en\-us/microsoft\-agent\-365/developer/reference/cli to ensure all commands are accurately represented and no discrepancies remain.
3. Add a test case in `src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Helpers` to validate that the CLI help output (`a365 --help`) matches the commands listed in the README. This will help prevent future mismatches between the documentation and the CLI functionality.
4. Update the `docs` folder to include a CONTRIBUTING.md or similar file that outlines a process for keeping the README and CLI commands in sync, such as requiring updates to the README whenever new commands are added or removed.
5. If not already present, add a CI workflow in `.github/workflows` to validate that the README commands are consistent with the CLI's available commands. This could involve running `a365 --help` and comparing the output to a predefined list of expected commands.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models

[gwharris7]

@claude Fix this issue. Only refer to existing commands in the repo. Keep descriptions brief.