fix(detail): the raw manifest editor showed {} for every app and saved to a dead field

[rubenvdlinde]

The defect

ApplicationManifestTab.vue seeded its buffer from JSON.stringify(app.manifest || {}, null, 2). Under the versioned model (ADR-002) the manifest lives on the ApplicationVersion, and the Application record carries no manifest key at all — ApplicationsController says so itself: "reading applicationArray['manifest'] directly returns null for every app".

So the integrator-facing raw JSON editor displayed {} for every application, and Save wrote that through obPatchApp({ manifest }) onto a field nothing reads back. Empty on read, dead on write.

This is the same root cause as the Save-as-template defect fixed in #63 — the Application record is not where the manifest lives — now found in a third consumer. The tab loads and saves through /api/applications/{slug}/manifest, which resolves the active version. Note the endpoint asymmetry, which the code comments: GET returns the manifest bare, PUT expects it wrapped in { manifest }. A failed load falls back to the record and surfaces the error rather than blanking the editor.

Credit where due

The defect was diagnosed (not fixed) by whoever wrote the skip on REQ-OBR-005 — a valid edit is PUT to OR and survives a reload, with the evidence spelled out in the skip body. That test is now un-skipped and green: it asserts the editor loads the real manifest (the exact thing that broke), that a valid edit reaches the server, and that it survives a reload — then restores the fixture.

Cleanup

tests/e2e/application-editor.spec.ts is deleted. It was kept as a signpost to this REQ-OBR-005 coverage while that coverage was skipped; now that the replacement runs, the pointer is a second, dead name for the same scenario.

Verification

18 passed / 13 skipped across openbuild-runtime, save-as-template and rbac-403 on the Vue 3 instance. ESLint clean apart from the repo-wide pre-existing n/no-unpublished-import.