feat(iid-spec): add the normative IID specification package

[kamescg]

Summary

P01 of the iid-v1.1.0-alpha release train. Adds @0xintuition/iid-spec — the normative Intuition ID specification with a machine-readable conformance corpus — as the first (docs-only) package in the release registry.

Ported from the authoritative private reference (0xIntuition/intuition-v2 @ 8b9e9aa11, PR #914) with private-monorepo references removed. The per-scheme documents, implementation-notes, and conformance corpus are new authorship for this release (the private package promised but never contained them); scheme documents are grounded in the reference canonicalizers, and every conformance vector was generated from and asserted against the reference implementation, with the spec's own stated golden values cross-checked.

Contents

• explainer.md + spec/00–09 (grammar, identity classes/tiers, NORM-1, ladders, gen1, representation profiles, equivalence, governance)
• schemes/ — registry index + 26 normative per-scheme documents (grammar, ordered canonicalization, validation, vectors, limitations)
• conformance/ — 145 versioned vectors in 6 files + JSON schema: per-scheme canonicalization (positive+negative for all 26), NORM-1, gen1 with exact preimages, parsing (colon-bearing CAIP-10, int:src:* guard), validation/anchor-eligibility, registry snapshot
• implementation-notes.md — records the parser value-grammar deviation (private parser accepted spaces/non-ASCII in values); the P02 port fixes the character class to the spec's %x21-7E
• Package integrity test: schema shape, per-scheme coverage, globally unique fixture IDs, internal link resolution, private-reference leak guard

Tooling

• iid-spec registered first in the central package registry as docs-only
• guard-direct-publish learns docs-only rules (no dist/main/types; README+LICENSE required) from the registry

Package impact

Package	Change
@0xintuition/iid-spec	new, docs-only, 0.1.0-alpha.0
all existing packages	none

Target versions

@0xintuition/iid-spec@0.1.0-alpha.0. No internal dependencies.

Identity impact

Identity impact: none — existing golden bytes unchanged

Fixture impact

New corpus: fixture files canonicalization (101), norm1 (13), gen1 (6), parse (11), validation (14), schemes snapshot — specVersion 0.1.0, fixtureVersion 1. Append-only from here; changing an existing vector is identity-impacting.

Contract artifact

n/a

Rollout notes

• P02 (@0xintuition/iid) consumes this corpus as its conformance test input and must pass every vector, including the two parse vectors the private implementation fails (documented in implementation-notes).
• Open ratification question for the spec owner: the purl canonicalizer truncates at the first @, so scoped npm packages (npm/@babel/core) reject. Documented as a limitation in schemes/purl.md. If any int:purl: atoms already exist, this is frozen per §9.3; if none exist, a pre-ratification fix is still possible but must land before P02 merges and be reflected in spec, fixtures, and reference implementation together.
• Local validation: full turbo test (18 tasks), registry check, supply-chain guard, pack dry-run, and clean-room tarball smoke (now 11 packages, Node+Bun) all pass.

🤖 Generated with Claude Code