MotirBuilding in public
MOTIR · moooon
onMotir
You’re viewing a public project. Anyone can view it — no account needed. Sign in to submit, upvote, or comment on requests.View-only — you can’t edit work items
MOTIR-149

bug-finding-47 Workflow settings page has no nav entry point — orphaned route

Done
Description

Type: bug · Parent: Epic 2 · Source: Finding #47.

The /settings/project/workflow route (shipped in subtask 2.2.5) works — page + all six Server-Action writes — but nothing links to it. App navigation points only to /settings/project (which renders just the archive card) and /settings/workspace, so the workflow editor is reachable only by typing the URL (the Playwright spec reaches it via page.goto). Only discoverability is missing.

Root cause / fix: the /settings/project area has no settings sub-nav pattern (no tabs/sidebar) to hang a "Workflow" link on — a cross-cutting app-shell concern. Resolution: add a project-settings sub-nav (Workflow / Archive / …) so every settings sub-page has an entry point. Links: discovered in Story 2.2 (subtask 2.2.5); fix belongs to Story 1.5 (app-shell / settings-nav). Not nested under either — linked.

Resolution (motir-core 4bc4463): the /settings/project page now renders a Workflow navigation card linking to the editor — the minimal fix, reusing the existing Card grammar (a single <Link> wrapping the card, no new settings-nav chrome invented). E2E in tests/e2e/workflow-settings.spec.ts asserts the editor is reachable by clicking through from project settings (no page.goto). The fuller settings sub-nav (tabs / sidebar section across Workflow / Archive / …) remains a separate design decision, deferred — this fix only restores discoverability.