Nest Facility flows under Facility > Facility

[aravindm4]

What

Follow-up to #48. Nests the Facility flows one level deeper so the sidebar reads Flows > Facility > Facility > …, matching Flows > Clinical > Patient and Flows > Medications > Medication Request.

• Moves flows/facility/*.mdx to flows/facility/facility/*.mdx
• Nests a Facility module category inside the Facility domain category in the 3.1 sidebar
• Updates the relative links in the flows and in the Facility concept to match the new depth

In #48 these flows sat flat under flows/facility/, because the domain and the module have the same name. That made Facility the odd one out next to the other modules.

Route change

The four flow URLs move:

Before	After
/flows/facility/create-facility	/flows/facility/facility/create-facility
/flows/facility/view-facility	/flows/facility/facility/view-facility
/flows/facility/update-facility-details	/flows/facility/facility/update-facility-details
/flows/facility/delete-facility	/flows/facility/facility/delete-facility

Nothing in the site links to the old paths, so the build is clean. Worth deciding whether these need redirects, given #48 is already merged and deployed.

Verification

Docusaurus build passes for both en and ml locales.

[cloudflare-workers-and-pages]

Deploying coredocs with    Cloudflare Pages

Latest commit:	e3e92d3
Status:	✅  Deploy successful!
Preview URL:	https://f698cdbf.coredocs.pages.dev
Branch Preview URL:	https://docs-facility-flow-nesting.coredocs.pages.dev

View logs

[github-actions]

Docs review

The change is sound. It is a pure move plus link/sidebar bookkeeping, and I found no checklist violations in the changed lines.

What I verified:

• Links — every relative link changed here resolves after the move. The four flows go one level deeper, so ../../concepts/... correctly becomes ../../../concepts/...; the sibling ./<slug>.mdx links inside the flows are unaffected by the move and stay correct. The four links in concepts/facility/facility.mdx are updated to the new paths. No link anywhere else in the repo points at the old flows/facility/<slug> paths.
• Flow sidebar (manual) — all four flows are listed in the new nested Facility category in versioned_sidebars/version-3.1-sidebars.json, so none becomes invisible. The nesting matches the shape already used for Clinical > Patient and Medications > Medication Request, and the new flows/facility/facility/_category_.json matches the label/position/key pattern of flows/clinical/patient/_category_.json.
• Corruption / MDX safety — no antml:, tool-call XML, {#...} heading ids or bare braces introduced.
• Layer discipline, labels, permissions — no prose content changed beyond the link paths, so nothing new to flag.

Could not verify

• Mirroring. The conventions require version-3.0 and version-3.1 to be kept identical, but on the base branch versioned_docs/version-3.0 has no flows/facility folder at all and its concepts/facility/facility.mdx is already a different, older page. So the 3.0 divergence pre-dates this pull request (it came in with #48) and is not something this change introduces — I am noting it rather than raising it as a finding here.
• Redirects. The description already raises this. The four URLs move, and #48 is merged and deployed, so any external link to /flows/facility/create-facility and its siblings will 404. That is a product decision, not a docs-rule violation, so I am not blocking on it — but a @docusaurus/plugin-client-redirects entry for the four old paths would be cheap.

One inline nit on a changed line, about a stray double space that was carried over from the original file.> Generated by Docs Reviewer for #76 · opus50 · 65.5 AIC · ⌖ 17.1 AIC · ⊞ 11K

[github-actions]

Small nit on this changed line: there is a double space between the link and in Care. Suggested wording: This flow describes how to create a new [facility](../../../concepts/facility/facility.mdx) in Care.