Publishing an Application via a raw PUT doesn't create its BuiltAppRoute (manifest endpoint 404s)

[rubenvdlinde]

Symptom

tests/integration/openbuilt.postman_collection.json → "GET the manifest endpoint after publish (newman-roundtrip)" fails: after PUT /apps/openregister/api/objects/openbuilt/application/{uuid} with {status:"published", ...}, GET /apps/openbuilt/api/applications/{slug}/manifest returns 404 (3 of the 22 assertions in that collection).

Root cause

GET .../{slug}/manifest resolves {slug} → BuiltAppRoute → Application. The route is supposed to be created by the Application schema's publish transition (on_transition.upsert_relation in lib/Settings/openbuilt_register.json). Since OR's lifecycle engine doesn't execute that action, ApplicationVersionSnapshotListener is the PHP fallback — but it only fires on ObjectTransitionedEvent, and a plain PUT that sets status: published does not currently make OR dispatch ObjectTransitionedEvent (the transition machinery is only exercised via OR's dedicated transition path, not a field-value change on a generic object PUT). #18 added the route-upsert half of the fallback, but the event still has to fire for it to run.

Options (pick one, probably (a) + adjust the test)

a. OR fires ObjectTransitionedEvent when a generic object PUT changes the lifecycle field from a valid from to a valid to state. Most correct — makes the declarative x-openregister-lifecycle actually drive behaviour regardless of which write path is used. Filed against ConductionNL/openregister once confirmed.
b. OpenBuilt adds a POST /api/applications/{slug}/publish endpoint that drives the transition (and thus the route + snapshot) — explicit, but duplicates what the declarative lifecycle is supposed to do.
c. The Newman collection publishes via OR's transition endpoint instead of a raw PUT — fixes the test but not the underlying "raw PUT doesn't transition" surprise for real callers.

Related

• feat(listener): upsert BuiltAppRoute on Application publish #18 (route-upsert listener half — merged)
• CI: Newman + PHPUnit-on-NC-server fail because openbuilt register not seeded at app:enable #11 (openbuilt PHPUnit/Newman CI needs OpenRegister installed)
• ADR-031 §Exceptions(1) (declarative-first failure mode)

[rubenvdlinde]

Collection-side fix done in #28: the Newman publish step now goes through OR's lifecycle transition endpoint (POST .../objects/{uuid}/transition with {"action":"publish"} — the server-side equivalent of ApplicationEditor.vue's publish()) so the transition fires ObjectTransitionedEvent → ApplicationVersionSnapshotListener creates the BuiltAppRoute → the manifest GET resolves. The in-CI verification of this is still blocked by the openbuilt↔OpenRegister-main integration gap (register not seeded on enable; OR main lacks the lifecycle feature) — tracked in #29 along with the OR-development $mail regression. The original symptom (raw PUT status=published doesn't create the route) is correctly addressed; clients should publish via the transition endpoint, which the UI already does.