Documentation

[SethHollandsworth]

The main README was getting bloated, so this splits it up into subcommands and adds more information about the --input flag as well as VN2

[Copilot]

Pull Request Overview

Splits the bloated main README into focused subcommand guides, enriches the --input flag documentation, and adds details for the VN2 scenario.

• Introduced a standalone JSON schema reference in v1_json_file_format.md.
• Added separate docs for katapolicygen, acipolicygen, and acifragmentgen commands.
• Extracted common concepts to common.md and expanded enforcement point reference.

Reviewed Changes

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

Show a summary per file

File	Description
src/confcom/azext_confcom/docs/v1_json_file_format.md	Detailed JSON input schema reference
src/confcom/azext_confcom/docs/katapolicygen.md	CLI examples for katapolicygen
src/confcom/azext_confcom/docs/common.md	Extracted common documentation
src/confcom/azext_confcom/docs/acipolicygen.md	CLI examples with --input and VN2 scenario
src/confcom/azext_confcom/docs/acifragmentgen.md	CLI examples for acifragmentgen
src/confcom/azext_confcom/docs/Policy Enforcement Points.md	Framework rule reference and sample policy docs

Comments suppressed due to low confidence (4)

src/confcom/azext_confcom/docs/acipolicygen.md:60

• [nitpick] For consistent styling, change "NOTE:" to "Note:" and correct the casing in "In most cases."

**NOTE:** Generating JSON policy is for use by the customer only, and is not used by ACI In most cases.

src/confcom/azext_confcom/docs/Policy Enforcement Points.md:364

• The flag is defined as allow_dump_stacks elsewhere; update this reference to allow_dump_stacks to match the actual rule name.

`allow_dump_stack` VS `dump_stack`

src/confcom/azext_confcom/docs/v1_json_file_format.md:55

• [nitpick] This subheading duplicates the top-level fragments field name and may confuse readers; consider renaming to something like "#### Fragment Object Definition".

#### fragments

src/confcom/azext_confcom/docs/common.md:10

• [nitpick] For consistency with other list items, add a trailing period.

This can be explored using `docker image inspect`

[ksayid]

thoughts on having each example title in the ToC? makes for easy navigation