docs: add shorn to the ecosystem page - #1649

✅ No new issues found.

Reviewed changes

• ark/docs/content/docs/ecosystem/index.mdx — adds a ### shorn section (after DRZL) with a prose intro, a // @noErrors ArkType example, and a closing callout about open objects / "+": "delete".
• ark/docs/content/docs/ecosystem/meta.json — appends the [shorn](/docs/ecosystem#shorn) entry to the pages array.

I verified every substantive claim rather than taking them on trust:

• The "ArkType 2.1.28 and newer implements both Standard Schema and Standard JSON Schema" floor matches the ark/type CHANGELOG (2.1.28: "Standard Schema is now a valid definition" + "Adds support for the new Standard JSON Schema interface").
• The claim that ArkType omits additionalProperties: false for object JSON Schema output matches the ~standard.jsonSchema/toJsonSchema() test snapshots (objects emit properties + required only).
• The section and meta.json entry follow the page's established structure and naming conventions (heading → lowercased anchor, // @noErrors decorator, tab-indented object props).
• The example code compiles against ArkType/CSS syntax (number.integer >= 0, "'M' | 'F' | 'X'"), and shorn's public docs confirm the encode/decode API, the Standard Schema + Standard JSON Schema mechanism, the 2.1.28 floor, the "+": "delete" guidance, and the "8 bytes vs 35 bytes JSON" figures.

ℹ️ Experimental library placement

shorn is at 0.1.0 with a wire format that isn't frozen until 1.0. The author already flagged this and offered to close the PR if the ecosystem page is meant for stable libraries only. Nothing in the docs is inaccurate or misrepresented on this point, but the maintainers should consciously decide whether to feature an experimental serialization format whose encoded bytes are not yet stable — a reader who adopts it now will need to re-encode data after 1.0. This is a policy call for the maintainers, not a defect in the PR.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}