Skip to content

Standardize generated TypeScript wrapper boundaries and regeneration flow #29

@danbot315

Description

@danbot315

Define and enforce generated-code boundaries for action wrappers.

Scope

  • standard output path conventions
  • generated file header markers
  • add clean/regenerate command path

Acceptance Criteria

  • generated files are clearly identifiable
  • regeneration is deterministic and documented

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions