Stamp debug identifiers in API responses and render as data-* attributes so agents can reconstruct debug artifact URLs from the public surface.
When building an agent-driven validation workflow for a production feature (e.g., Pulse editorial check), stamp opaque identifiers (task IDs, archive keys) into the API response and render them as invisible data-* attributes on the frontend component. This lets an OMP agent reconstruct debug artifact URLs from the public API alone — no admin endpoints needed.
Pattern: (1) stamp metadata in the DB record's extras/JSON column during artifact upload; (2) expose it as a defaulted field on the public API response VO (non-breaking additive change); (3) render as data-edition-date, data-task-id etc. on the component's outer div; (4) write an OMP skill that teaches the agent to fetch the API, extract the metadata, construct the artifact URL, download and validate.
The data attributes are invisible to users but show up in DevTools, tab.observe(), and tab.evaluate(() => el.dataset) in the OMP browser tool. Pre-existing records without the metadata get the default empty string — the skill documents the fallback URL pattern for these.