What Studio needs
A way to take a person from a built page in the plan to that page in the running app, so "check this against its wireframe" is one click.
What exists today
Nothing, and the absence is deliberate in at least three places:
skills/e2e-harness-base.md says never use /p/ deep links after login, because Mendix invalidates the context.
skills/ui-loop.md says open the page through real navigation, as a real user role, not a direct URL.
project-tests/e2e/helpers.js navigates by clicking real nav anchors. The only page.goto calls are login and a reset to the base URL.
A search for pageUrl, page_url and page-url across bin/, project-bin/, project-tests/ and skills/ returns nothing. project-bin/page-scope.sh writes inScope as Module.Page, with no url field.
Blast radius
Rating: needs care, and not ready for a PR.
Additive as data. Not additive as a rule: "every built page must have a URL" is a modelling change on every project, and it contradicts the harness rule above.
The user visible failure is the sharp one. A page opened by URL, when that page needs a context object, renders without it. The person then reviews a broken screen and records a false finding. That is precisely the case the harness rule documents.
Suggested alternative: record a nav path, the nav group and item that navTo already uses, in .claude/loop/page-scope.json, leaving the harness rule intact. Studio then says "Home, then Practice, then Listening" instead of offering a link that may mislead. A /p/ URL only for pages that are genuinely direct nav targets, marked as for humans and not for the harness.
Decision needed
- Is the ask "record the URL where a page already has one", which is additive and safe, or "every built page must have a URL", which is a modelling rule?
- If URLs are wanted, what is the position on the deep link rule, and on which pages may be deep linked at all?
- Would a nav path serve the actual goal better than a URL?
What Studio needs
A way to take a person from a built page in the plan to that page in the running app, so "check this against its wireframe" is one click.
What exists today
Nothing, and the absence is deliberate in at least three places:
skills/e2e-harness-base.mdsays never use/p/deep links after login, because Mendix invalidates the context.skills/ui-loop.mdsays open the page through real navigation, as a real user role, not a direct URL.project-tests/e2e/helpers.jsnavigates by clicking real nav anchors. The onlypage.gotocalls are login and a reset to the base URL.A search for
pageUrl,page_urlandpage-urlacrossbin/,project-bin/,project-tests/andskills/returns nothing.project-bin/page-scope.shwritesinScopeasModule.Page, with no url field.Blast radius
Rating: needs care, and not ready for a PR.
Additive as data. Not additive as a rule: "every built page must have a URL" is a modelling change on every project, and it contradicts the harness rule above.
The user visible failure is the sharp one. A page opened by URL, when that page needs a context object, renders without it. The person then reviews a broken screen and records a false finding. That is precisely the case the harness rule documents.
Suggested alternative: record a nav path, the nav group and item that
navToalready uses, in.claude/loop/page-scope.json, leaving the harness rule intact. Studio then says "Home, then Practice, then Listening" instead of offering a link that may mislead. A/p/URL only for pages that are genuinely direct nav targets, marked as for humans and not for the harness.Decision needed