fix: sanitize absolute runner paths in generated schemas

[CWAbhi]

Notes for Reviewers
This PR fixes #526
This PR addresses the issue of absolute environment paths being leaked into the repository during the automated type generation process. Currently, the GitHub Action runner’s local workspace path (e.g., /home/runner/work/...) is being captured by the generation tool and committed directly into the TypeScript schemas, such as SchemasOpenApiSchema.ts.

This causes unnecessary git noise and pollutes the codebase with environment-specific metadata that is irrelevant to other developers and production environments.

Changes

•Workflow Sanitization: Updated the generate-types workflow to include a post-generation cleanup step. This step dynamically identifies the $GITHUB_WORKSPACE and replaces it with a relative ./ path across all generated .ts files.

•Verification Gate: Added a validation check before the commit step. The CI will now scan for any remaining /home/runner strings and fail the build if a path leak is detected.

•Standardized Error Logging: Integrated a descriptive error moniker for the verification failure to align with the project's event-tracking framework.

• [✅] Yes, I signed my commits.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[CWAbhi]

@leecalcote can you check this out . if it works i think we should close and merge this into schemas

[alphaX86]

Hi @CWAbhi, has this GH action been tested out and working in your forked copy of repo?

[hortison]

@CWAbhi did you address the primary concern of this path being included during mesheryctl docs builds in the meshery/meshery repo?

[CWAbhi]

@hortison Yes, this PR directly addresses the root issue by sanitizing generated schema artifacts, preventing absolute paths from propagating into downstream consumers like mesheryctl docs builds in the meshery/meshery repo.

[alphaX86]

This may cause workflow to fail every time based on global grep cmd usage on checking paths...

[CWAbhi]

@alphaX86 You’re right , a global recursive grep can cause false positives, especially since mesheryctl docs generation may legitimately include /home/runner paths.
We can scope the check to only the schema-generated files (or exclude docs/build directories) to ensure we only fail on unintended path leakage.
I can update the workflow to restrict the grep to specific artifact paths.

[CWAbhi]

@alphaX86 I’ve updated the workflow to scope the /home/runner path check to schema-generated artifacts only.

[alphaX86]

@lekaf974 @hortison would require your review here...