[nichinichisou0609]

Summary

Product stages (nnnotes.pipeline.assemble.ProductStage) assemble a product from the unity.export results of the objects it reaches, never from a bundle.

Request roots

• A product's task starts from root objects: the objects of the catalog keys it gives for the subject (through the address table of link.addresses), and the object ids it names.
• assemble.request(stages, products, env) turns that into the fact roots ({keys, objects}), which the unit request uses. A run then exports the units those roots reach and nothing else of their bundles.

Reach and the object table

• reach walks the units of the roots, then every unit an item of a reached unit references, through the results.
• A sprite whose atlas is in another bundle takes its image from the sprite.crop result of that atlas.
• A reached unit that the request did not export is an error of the request; an object no census holds is listed as missing.
• The reached objects become the object table (nnnotes.objects/1), the task's only input: class, name, item status, files by role, the object holding a contained one, and the reason code of a generic, unsupported or failed one. Its key therefore follows exactly the files the product can read.

Result and layout

• The result holds the product's files as <task id>#<path>, its object table as <task id>#objects, and one item for the subject (exported, or unsupported with a reason code).
• layout.product_entries / layout.product_manifest place a product for a player: every file and every file of its objects at assets/<sha256>.<ext>, and one manifest (nnnotes.product/1) per product listing its files and its objects' files. A file several products share is written once.
• view.voices now reads the address table through the same cached reader as the unit table.

Docs

• New docs/products.md, with the request, the object table, the layout and the manifest; stages.md, contracts.md and schemas.md updated, plus objects.schema.json and product.schema.json.

Test plan

• Full test suite
• New tests/pipeline/test_assemble.py over the bundle fixtures of test_objexport: the request, the table of a prefab hierarchy, a cross-bundle atlas crop, waiting, the result, pruning and the layout
• ruff, pyright, import-linter, mkdocs build --strict

Not in this PR

The CLI wiring and the first real product (Live2D) come with the assemblers; no command reads a product yet.

🤖 Generated with Claude Code