Apps
MILLWORK BRANDS
Access is limited to authenticated Millwork Brands users.
Launcher
Your apps
Feedback
Security Training
Apps
Apps
Signed In
Launcher
No apps are currently assigned to this account. If that is wrong, add this user to the matching Azure app group.
Feedback
Security Training
Admin
Ticket
Admin
Admin
Use this as the admin runbook for directing Codex. The goal is not for you to memorize repo internals. The goal is to know what to ask for and what a correct workflow looks like.
Ask for quick verify for routine app work, bug fixes, and ordinary estate context.
cd /mnt/c/MBI\ Apps/MBI\ Apps\ Portal
pwsh -NoProfile -File ./scripts/estate-verify.ps1 -Mode quickQuick verify is the normal fast path. It checks estate state and now includes the standard test browser smoke pass unless explicitly skipped.
Ask for full verify before release, after broad migration work, after cleanup across many repos, or when you want a stronger confidence pass.
cd /mnt/c/MBI\ Apps/MBI\ Apps\ Portal
pwsh -NoProfile -File ./scripts/estate-verify.ps1 -Mode full-SkipBrowserSmoke: use only when test browser smoke is intentionally being bypassed.-IncludeBrowserSmoke: force browser smoke when you want it outside the usual quick path.-IncludeLiveBrowserSmoke: use when you explicitly want live read-only browser smoke.-PreferRegularAccount: use when the behavior should be tested as a normal user instead of an admin.These app families are currently included in the estate browser smoke gate.
The app status dots on the launcher are admin-only and are generated from the current estate status export.
Current checks come from the portal manifest metadata and include:
Tooltip text shows the current issue summary plus the last checked time. For auth-style health endpoints such as Org Chart, 200, 401, and 403 are treated as healthy because they still prove the route is responding.
Ask Codex to scaffold the family, set up the estate mapping, create the test harness, and refresh the estate outputs.
node ./scripts/scaffold-family.js --family-id <id> --title "<Title>" --repo "C:\MBI Apps\MBI <Title>" --live-url "https://<id>.millworkbrands.com" --test-url "https://<id>-test.millworkbrands.com"Expected family shape:
PWA/LivePWA/TestAPI/LiveAPI/Testsharedproject/testTell Codex to replace the placeholder test assets, add the portal app entries, update the manifest/service-map generators, and then run quick verify.
pwsh and pointed at the real live/test runtime path..auth, playwright-report, or test-results.Completed families are expected to carry these standard contract files.
family.jsondeploy/run-live-runtime.ps1deploy/run-test-runtime.ps1project/test/check-prereqs.ps1project/test/run-full.ps1Deploy verification checks family contracts, IIS physical paths, Windows service image paths, and optional health endpoints in full mode.
cd /mnt/c/MBI\ Apps/MBI\ Apps\ Portal
pwsh -NoProfile -File ./scripts/estate-deploy-verify.ps1 -Mode quickAsk Codex for estate refresh after portal metadata changes, manifest-affecting changes, or repo hygiene work that changes generated state.
cd /mnt/c/MBI\ Apps/MBI\ Apps\ Portal
pwsh -NoProfile -File ./scripts/estate-refresh.ps1 -Mode quickUse full refresh when the work touched many repos or involved broader cleanup.
Start with quick estate verify, fix this in test first, then prove it in live before committing.Run full verify before you close this out.Add this as a new app family and wire it into the estate manifest, browser smoke, and portal metadata.Do not guess. Verify the served asset path and the actual live runtime.Keep commits separated by logical boundary.The deeper engineering reference still lives in docs/codex-operator-guide.md in the Apps Portal repo.
Admin