Greptile Summary

This PR fixes a data truncation issue reported in #1471 by increasing the MaxLen of the external_id field from unset (which defaults to VARCHAR(191) on MySQL) to 512 on both the Request and RequestExecution ent schemas, then regenerates all downstream ent artifacts. The application uses ent's auto-migration on startup (client.Schema.Create), so the ALTER TABLE to widen the column will execute automatically when the service restarts.

Confidence Score: 5/5

Safe to merge — a targeted, correctly regenerated schema fix with no logic changes.

The change is minimal and consistent: both schema files and all generated ent artifacts are updated in lockstep. The app uses ent auto-migration on startup so the column resize will happen automatically. The runtime validator is derived from the schema descriptor, ensuring the new 512-char limit is enforced everywhere. No P0 or P1 findings.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant RequestCreate/Update
    participant ExternalIDValidator
    participant MySQL DB

    Client->>RequestCreate/Update: SetExternalID(value)
    RequestCreate/Update->>ExternalIDValidator: ExternalIDValidator(value)
    Note over ExternalIDValidator: MaxLen check: len ≤ 512
    alt len > 512
        ExternalIDValidator-->>RequestCreate/Update: ValidationError
        RequestCreate/Update-->>Client: error
    else len ≤ 512
        ExternalIDValidator-->>RequestCreate/Update: nil
        RequestCreate/Update->>MySQL DB: INSERT/UPDATE external_id (VARCHAR 512)
        MySQL DB-->>Client: success
    end

_{Reviews (1): Last reviewed commit: "chore: generate schema" | Re-trigger Greptile}