Aligns the proposed convention with the draft SEP:
- skill-path is a locator of one or more segments, not the skill name;
identity lives in SKILL.md frontmatter
- authority component is the first path segment by RFC 3986 mechanics
but carries no special semantics
- add no-nesting constraint (SKILL.md cannot be ancestor of another)
- resource templates are MAY and primarily user-facing via completion
- enumeration via resources/list is optional; clients must not treat
an empty list as proof of absence
- add nested-path examples throughout
The survey section is unchanged; it's historical record.
71fc13af51