Skip to content

Standard should mandate typeDiagram for model/type generation (remove Dart codegen assumptions) #17

Description

@MelbourneDeveloper

Context

The AgentPMO-managed standard currently assumes a Dart codegen/ toolkit (pubspec.yaml) for generating shared model types. In a TypeScript / VSIX repo that toolkit has been replaced by typeDiagram — a single .td source compiled with typediagram --to typescript. The Dart toolkit was deleted.

Asks

  1. Mandate typeDiagram as the model/type generation tool in the standard, so agents pick it up from the standard rather than discovering it ad hoc. (This is the gap that prompted this issue: the standard did not mention it, so it was not picked up automatically.)

  2. Remove the Dart / pub assumptions baked into the managed files. These reference the now-deleted codegen/ toolkit and were hand-corrected downstream:

    • .github/dependabot.ymlpub ecosystem pointing at /codegen (now a dangling directory -> dependabot error).
    • .github/workflows/codeql.yml — "Dart codegen/ toolkit is NOT analysed" comment.
    • .claude/skills/upgrade-packages/SKILL.md — Dart section + codegen/pubspec.yaml reference.
    • .claude/skills/code-dedup/SKILL.md — deslop "dart" supported-language note.
    • .claude/skills/spec-check/SKILL.md — Dart (flutter_test) reference.
    • CLAUDE.md — "Primary language ... plus a small Dart codegen/ toolkit" + the codebase-structure codegen/ line.

Note

These were corrected by hand in the downstream repo; the generator templates should reflect the change so the Dart references are not re-added on the next sync.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    Type

    No type

    Fields

    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