Manifest reference

Every package provides a plugin.toml manifest. The following flat form is suitable for a post-pitch package:

protocol = "amadeus.plugin/v1"
id = "com.example.pitch"
name = "Pitch adjustment"
version = "0.1.0"
role = "hook"
stage = "post_pitch"
runtime = "quickjs"
entry = "dist/plugin.iife.js"
order = 100
enabled_by_default = true
sha256 = "..."

Field	Requirement	Purpose
`protocol`	Required	Must be `amadeus.plugin/v1`.
`id`	Required	Stable package identifier.
`name`	Required	User-visible package name.
`version`	Required	Package version.
`role`	Required	`language`, `hook`, `importer`, or `exporter`.
`stage`	Hook only	Hook stage. Omit it for a language package.
`runtime`	Required	`quickjs` for a JavaScript entry.
`entry`	Required	Compiled JavaScript entry relative to the manifest.
`sha256`	Optional	Integrity checksum for the entry.
`order`	Optional	Relative hook order; lower values execute first.
`enabled_by_default`	Optional	Initial enabled state.

A sectioned manifest places identity under [package], loading fields under [plugin], and sha256 under [verification]. Use one stable identifier and preserve it across updates. For remote distribution, add an [update] block with metadata_url and entry_url; see Publishing and updating.

Importer and exporter role values are reserved; registration is unavailable in the current release.