Skip to content

fix(desktop): rename 30617 create-menu action Project → Repository - #88

Merged
oscarlehuu merged 2 commits into
mainfrom
fix/issue-66-repository-label
Aug 6, 2026
Merged

fix(desktop): rename 30617 create-menu action Project → Repository#88
oscarlehuu merged 2 commits into
mainfrom
fix/issue-66-repository-label

Conversation

@oscarlehuu

Copy link
Copy Markdown

Summary

  • The create menu labeled the local-folder add action Project, but that flow publishes kind 30617 — a repository in upstream vocabulary (AGENTS.md: 30617 = repository, 30621 = project; Crew has no 30621 surface yet — D-014 folder-first remains the add path).
  • Renamed user-visible copy across the whole 30617 add chain: create-menu item, add dialog (Add this Repository? / Repository name / Add Repository), flow toasts, lib validation + duplicate-name errors, runtime timeout/failure messages, folder-picker title (Select Repository workspace), and the menu aria-label (AT no longer hears "project" for the 30617 action).
  • Explicitly untouched: Projects screen/nav/routes, internal identifiers, and the test(e2e): skip upstream create-project dialog cases on Crew #65-skipped upstream 30621 CreateProjectDialog tests (they keep clicking menuitem "Project" — correct once a real 30621 surface exists).
  • Non-skipped e2e assertion updated: project-commit-detail.spec.ts now expects menuitem Repository.
  • Vocabulary-rule comment added at the menu item.

Tests

  • Contract suite extended: dialog copy, lib/runtime error strings, picker title each pinned; plus a sweep assert — any user-visible string calling the 30617 entity a Project in dialog/lib/runtime/picker fails the suite (prevents one-string-at-a-time regressions).
  • Relay contract updated to the new duplicate-name phrasing.

Verify

  • pnpm run check green (biome + guards, all packages).
  • Contract tests: 10/10 pass (project-add-local-workspace-ui-contract + relay-contract).
  • Repo-wide desktop pnpm run test has pre-existing unrelated failures on main (React.act in TerminalSubstrate) — verified identical on origin/main, not introduced here.

Built by gpt-5.6-luna xhigh (Hermes); reviewed by grok-4.5 (Hermes) — REQUEST_CHANGES: both required findings (remaining add-path strings incl. picker title + aria-label; contract coverage for dialog/lib/runtime/relay) addressed in this PR. Finding 3 (skipped-test split) confirmed as-is.

Fixes #66

oscarlehuu and others added 2 commits August 7, 2026 00:43
Crew's create menu labeled the local-folder add action 'Project', but
that flow publishes kind 30617 — a repository in upstream vocabulary.
Upstream reserves 'Project' for kind 30621 (multi-repo grouping),
which Crew has no surface for yet (folder-first D-014 remains the add
path).

User-visible copy renamed across the whole 30617 add chain: create-menu
item, add dialog (title/label/submit), flow toasts, lib validation and
duplicate-name errors, runtime timeout/failure messages, folder-picker
title, and the create-menu aria-label no longer says 'project'.
Internal identifiers, the Projects screen/nav, routes, and the #65
skipped 30621 upstream dialog tests are deliberately untouched.

Contract tests now pin the full chain: any user-visible string calling
the 30617 entity a Project in dialog/lib/runtime/picker fails the
suite, so the vocabulary cannot regress one string at a time.

Fixes #66

Signed-off-by: oscarlehuu <oscar.lehuu@gmail.com>
@oscarlehuu
oscarlehuu merged commit af8517a into main Aug 6, 2026
11 of 12 checks passed
@oscarlehuu
oscarlehuu deleted the fix/issue-66-repository-label branch August 6, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename Crew Projects menu "Project" → "Repository" (30617 vs 30621)

1 participant