Removed validation policy from template

[magerstam]

Merge Checklist

All boxes should be checked before merging the PR

• The changes in the PR have been built and tested
• Documentation has been updated to reflect the changes (or no doc update needed)
• Ready to merge

Description

This PR updates the ADR for image extension workflows to simplify post-composition validation and better separate composition intent from operational verification behavior. The previous ADR draft introduced several validation-related CLI parameters, which increased complexity and blurred ownership between template-defined configuration and runtime validation execution. This update keeps template/schema responsibilities focused on image composition, while moving comparison behavior into a single, explicit post-composition CLI option.

• Reworked the validation section in to remove template-level validation policy.
• Replaced the multi-flag proposal with one high-level flag: --compare-report <sbom | full>
• Clarified implicit comparison inputs:
  • Baseline image is inferred from baseline.source.path in the template (overlay mode).
  • Output image is inferred from the primary produced artifact in the build working/output path.
• Updated examples and narrative to reflect:
  • SBOM-only comparison mode
  • Full semantic comparison mode
• Clarified that automated CVE checks and automated boot testing are out of scope for the composition command and remain manual or separate workflow steps.

Any Newly Introduced Dependencies

How Has This Been Tested?

[Copilot]

Pull request overview

Updates the image extension workflow ADR to remove template/schema-level validation policy and instead describe post-composition validation/comparison as explicit CLI behavior, keeping templates focused on composition intent and shifting operational verification to execution workflows.

Changes:

• Removes the previously proposed template-embedded validation policy section from the ADR’s schema recommendation.
• Introduces a simplified post-compose comparison interface proposal via --compare-report <sbom|full>.
• Clarifies that automated CVE checks and automated boot testing are out of scope for the composition command.

[arodage]

LGTM. While we are at it can we rename file to adr-image-overlay.md‎?

[srmungar]

The following may be considered to simplify template creation overall.

1. Image Creation Modes inferred implicitly
   Create Mode: No baseline source path specified → Build image from scratch with minimal packages
   Overlay Mode: Baseline source path provided → Apply modifications to existing image
2. Output Format Configuration
   Use the existing template's output format field (raw, ISO, VMDK, etc.) to specify the final image format for overlay operations.
3. ISO Remastering
   ISO remastering should be treated as a standalone feature with its own dedicated section, separate from the baseline section of the overlay mode.
4. Conflict Resolution Policy
   Add a dedicated "Conflict Resolution Policy" section to define how conflicts are handled during overlay operations.
5. Partitioning Scheme Limitations
   Current Issue: The template doesn't clearly specify whether repartitioning is supported in overlay mode.
   Recommendation: If repartitioning is allowed with overlay images, the ICT should only support:
   Extension of existing partitioning schemes, not complete overwriting or creation of entirely new partitioning scheme.This approach maintains compatibility with the base image while allowing controlled modifications.