App Composer analytics

The live /building article documents a real brief → Init specification → local Worker run, with real captures and editable diagrams. Guestbook commit 019ce0d117f9f89e472a5c7642d51d85301f7fcd publishes GET /r/:resource/api/invitation with open, paused, closed and full states, exact form paths and postcard limits; Linkarooie commit 20ef9a50c19c7a3419dc06fdae020c6a677ed5cf validates the contract and treats a malformed, redirected, foreign or partial response as unavailable. Approval and featuring remain separate. Woodhouse's source plate and contribution flow explain the same contract. The local fictional run is not a hosted deployment, and the invitation is a producer contract, not proof of a live owner configuration or adoption. Woodhouse's flow is a model of the published contract, not a production control.

The live App Composer homepage declares product-og-20261022b.jpg at 1200×630 and the 20261022b icon set; its build identity is 41d488383031169ead44aab3be4d53b5abbf9096. The image was fetched and inspected (SHA-256 0ed47d3fea0628308dec42db8e294bd462c1d82b9092905a5b207df61b31afad). Woodhouse's project record, dossier, portfolio tile and share-image path now use the current image, tile SVG and describing alt text. Social-platform unfurl rendering remains externally unverified. The producer's live metadata and image bytes are verified. Woodhouse's adoption is a reviewed reference, not proof that every external social platform has refreshed its cache, that every consumer outside the producer uses the new mark, or that the identity earned customer demand.

The released demo sends Make this collection to Init’s composition recommendation without overwriting a saved draft. Independent browser interaction checked that explicit Use changes the form while preserving authored settings; the configuration can be downloaded with the two source pins. The live reference explains where to find its fictional sample and links back to the original guestbook item. This demonstrates the available configuration and handoff, not a new creator deploying a production collection or independent adoption. Source pins, privacy and owning release gates remain in force. Browser QA must use the supported verification header; bounded open counts can include unmarked inspection and are not demand evidence.

Opaque credential and dotenv-comment regressions plus adversarial archive fixtures fail closed. The exact current production release and a separately bound preview passed negative credential-path and package-content checks. This is actual release-path and artifact coverage, not a guarantee against every secret format or proof that a new creator has completed onboarding. Private account state and migration work remain separate.

Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Composer and independently deployed Linkarooie identities agree with the owning release record. Native owner Publish/Hide and Remove-confirm interaction remain partial; API curation and public visual checks are separate evidence.

First source-reported collection date. Earlier activity is unavailable; the first day may be partial.