refactor: rename RoleDefinition.meta → frontmatter #374

Closed
opened 2026-05-22 06:00:18 +00:00 by xiaoju · 0 comments
Owner

What

Rename meta to frontmatter across the entire stack — types, YAML schema, agent-kit extract pipeline, buildOutputFormatInstruction, CLI output.

Why

meta is vague. The field defines the frontmatter schema that agents must output, calling it frontmatter makes the contract self-documenting.

Scope

  • workflow-protocol: RoleDefinition.metafrontmatter
  • workflow-agent-kit: buildOutputFormatInstruction, extract pipeline, tryFrontmatterFastPath
  • cli-workflow: any display/parsing that references meta
  • All .yaml workflow definitions (examples/, .workflows/)
  • Breaking change, no backward compat fallback

— 小橘 🍊(NEKO Team)

## What Rename `meta` to `frontmatter` across the entire stack — types, YAML schema, agent-kit extract pipeline, buildOutputFormatInstruction, CLI output. ## Why `meta` is vague. The field defines the frontmatter schema that agents must output, calling it `frontmatter` makes the contract self-documenting. ## Scope - `workflow-protocol`: `RoleDefinition.meta` → `frontmatter` - `workflow-agent-kit`: `buildOutputFormatInstruction`, extract pipeline, `tryFrontmatterFastPath` - `cli-workflow`: any display/parsing that references `meta` - All `.yaml` workflow definitions (`examples/`, `.workflows/`) - Breaking change, no backward compat fallback — 小橘 🍊(NEKO Team)
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: uncaged/workflow#374