Honor operation extraction filters in OpenAPI specifications

[Copilot]

Operation filters excluded individual artifacts but left the full API specification intact, allowing publishing to recreate excluded operations.

• Consistent filtering: Apply existing operation matching to YAML/JSON OpenAPI and Swagger specifications, including x-ms-paths. Remove excluded methods and paths with no remaining operations.
• Preserved behavior: Retain shared definitions and metadata. Leave specifications unchanged when operation filters are omitted; leave GraphQL, WSDL, and WADL handling unchanged.

For example:

apis:
  - api1:
      operations:
        - create-resources

The exported specification now contains only create-resources, matching the operation artifacts.

• Fixes [Bug] Selective API operation extraction filter does not filter paths in specification.yaml #294

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

Whole-document parsing and serialization can corrupt untouched large numeric and date-like values.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Filtering corrupts untouched scalar values during document reserialization · New

[Copilot]

Copilot review overview

🟡 Changes recommended

Unsafe fractional or exponent-form numbers can be rounded when filtered specifications are reserialized.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Preserve precision for all unsafe JSON numeric forms · New

Resolved since last review (1)

• Filtering corrupts untouched scalar values during document reserialization

[Copilot]

Copilot review overview

🔵 Needs a closer look

JSON and YAML filtering can still alter unrelated high-precision decimal values.

Review effort: Balanced
Findings: 1

Open (1)

• Preserve precision for all unsafe JSON numeric forms

[Copilot]

Copilot review overview

🟡 Changes recommended

JSON and YAML floating-point values can still be corrupted during specification reserialization.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1 · 1

Open (2)

• Preserve all JSON numeric tokens to prevent corruption · New
• Preserve precision for all unsafe JSON numeric forms

[Copilot]

Copilot review overview

🔵 Needs a closer look

YAML high-precision floating-point metadata can still be silently rounded during filtering.

Review effort: Balanced
Findings: None

Resolved since last review (2)

• Preserve all JSON numeric tokens to prevent corruption
• Preserve precision for all unsafe JSON numeric forms

[Copilot]

Copilot review overview

🔵 Needs a closer look

YAML floating-point metadata can still be silently rounded during filtering.

Review effort: Balanced
Findings: None

Previously missed (1)

In code that hasn't changed since last review

Preserve YAML float precision during filtering

src/​services/​api-extractor.ts:449

YAML floating-point scalars are still parsed through CORE_SCHEMA as JavaScript numbers, so this path remains lossy whenever filtering modifies the document. For example, an unrelated value such as 9223372036854775807.0 or a high-precision decimal is rounded before yaml.dump; the custom type only preserves tokens resolved as YAML integers. Please preserve the raw representation of YAML float/exponent tokens as well (or use a lossless YAML AST) so filtering operations cannot change unrelated schema examples or bounds.