Define simple asset pages and flat file names

[codekiln]

Each garden asset now has a small page representing its file. The page name supplies a flat filename using triple underscores between namespace segments and preserving spelling within each segment; B2 stores that filename at the bucket root and local copies use assets/.remote/.

The September 24 MP3 is uploaded under this convention and embedded as an audio player. Its asset page has entity and documented duration frontmatter. DVC owns checksums; feed metadata owns enclosure size and media type. Bucket and storage details are not repeated on the asset page.

The shared definitions and asset-linking skill use this convention. Session links, JSON export, and the DVC plan point to the renamed upload. Uploading makes the audio available; the episode is published only after its Gitpa publication PR is merged and CI updates the site and RSS feed.

Gitpa PR #10 adds the matching episode audio player and URL while keeping the episode unpublished.

Validation: uploaded audio matches the source recording; garden episode tests and commit checks pass. Gitpa importer/feed tests and feed consistency check pass.

The definitions use general examples and validate filename characters so filenames map back to their exact page names. Namespaces imply ownership without duplicate properties. Backblaze/B2 is documented as a software product.

DVC is initialized with the garden B2 remote. The September 24 MP3 has committed .dvc metadata, and restoration from a fresh checkout matched the original recording. The binary remains excluded from Git.