Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,16 @@ catalog/

Each augment is a single JSON file located under your publisher directory.

New entries should use the canonical `urn:air:` identifier prefix and `type`.
Legacy `urn:ai:` and `mediaType` inputs remain accepted. Generation normalizes
the identifier once, and checks duplicates after normalization.
Comment on lines +15 to +17

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 285cd4c. The template and field table now use canonical urn:air/type, show owner/repository source metadata, and distinguish URL delivery from inline data. A regression test parses and validates the actual documented template. This also exposed a canvas-only validator that still required the legacy field; it now accepts canonical type while rejecting conflicting aliases. All 23 generator tests pass.


Resource-specific metadata may be an inline JSON object in `data` instead of a
`url`. Supply exactly one of them. An extension media type describes the payload;
it does not establish payload validity, runtime support, or execution permission.
For immutable source records, use a distinct identifier per selected revision
and retain the repository URI, environment path, and revision inside the payload.

## How to Add Your Augment

### 1. Fork and clone the repository
Expand Down
Loading
Loading