On this page · jump to a step
This guide uses the bundled RelayDemo source and local acceptance procedure. The source starting point has been checked; the intended diff below is not an executed result.
Who is this for?
Developers who have an Relayard app build and want to validate the connection before authorizing a business project. One visible string makes the task easy to review and restore. It does not establish the ability to deliver a complete iteration of a moderately complex app.
1. Initial state and user request
The bundled RelayDemo defines the visible title Ready for relay in RelayDemoApp.swift and includes a SwiftUI preview. The task is to change that title to Verified on this Mac while preserving everything else.
Save files and a checkpoint, then record the date, macOS / Xcode / Relayard versions, scheme, destination, client model and permissions. Native tool availability, the correct project and image delivery need separate checks.
2. The complete client request
Use Relayard to verify one small change in RelayDemo. Confirm the project, current status, permissions and actual tool catalog. Read RelayDemoApp.swift and confirm the title is "Ready for relay". Preserve existing work; change only the title to "Verified on this Mac". Build with an available tool. Follow any operation_id to a terminal state and keep the logs. Render the existing SwiftUI preview, then receive and inspect the actual image. Check for the new title and whether the image can be tied to this operation. Report the source diff, build result, image evidence and failed or unverified items separately. Do not replace real images with sample logs, paths or imageCount. Do not automatically commit, publish or roll back.
3. Intended change, not an observed diff
- "Ready for relay"
+ "Verified on this Mac"This shows only the requested string change. After execution, export the actual diff and check that existing work was preserved. No modified project or observed diff is attached to this page.
4. Operations and evidence to retain
| Step | Evidence to record | Status here |
|---|---|---|
| Project and read | Actual status, tool catalog and original file contents. | Mac run record not attached |
| Edit | Actual tool name, result and source diff. | Mac run record not attached |
| Build | Terminal state, scheme / destination and original build logs. | Mac run record not attached |
| Preview | The actual image, operation association and whether the new title is visible. | Mac run record not attached |
| Open issues | Failures, unverified items and the state after recovery. | Mac run record not attached |
5. What is known, and what is missing?
Checked: the sample source starting point, target string and acceptance procedure. Not attached: native operation receipts, the actual diff, terminal build logs, returned images and open issues from this run. Source tests and synthetic images are not treated as a complete Mac acceptance run.
6. Recovery and unsuitable environments
If tools are missing, the build fails, only an image path returns or image provenance is unclear, preserve the error and record the actual state. Query existing operations before repeating writes. To restore the title, review the diff locally and restore only this change.
If you have no app build, cannot authorize the tools or require a fully offline workflow, resolve those requirements or choose another approach. This task does not verify Simulator interaction, physical devices or App Store publishing.
How do you begin and complete the record?
Verify a read-only request with the setup guide, then run the small task above. Download the record template and link receipts, the diff, logs and images to the same task. Before publishing, remove tokens, device identifiers, private paths and business content. Never fill in an outcome that did not occur.
Source and procedure reviewed: 2026-10-08. Basis: the bundled RelayDemo and local acceptance guide. This is not the date of a Mac run.
Documentation updated: 2026-10-08