Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/modules/ee/feedback-record-directory/actions.ts`:
- Around line 16-19: The schema ZCreateFeedbackRecordDirectoryAction uses
z.cuid() for organizationId which is inconsistent with other ID fields that use
the shared ZId schema (see directoryId usage); change organizationId to use ZId
instead of z.cuid() and ensure ZId is imported/available in this file so all ID
validations reuse the same shared logic (update the
ZCreateFeedbackRecordDirectoryAction definition to reference ZId for
organizationId).

In
`@apps/web/modules/ee/feedback-record-directory/components/feedback-record-directory-table.tsx`:
- Around line 60-69: The unarchive flow in handleUnarchiveDirectory lacks a
loading state, so wrap the async call to updateFeedbackRecordDirectoryAction in
a boolean state (e.g., isUnarchiving) that you set to true before the await and
false in a finally block; use that state to disable the unarchive button(s) and
optionally show a spinner while the request runs. Update the component state and
the JSX for the unarchive button(s) (also apply same pattern to the manage
action buttons referenced around lines 129-136) so they read
disabled={isUnarchiving} (or similar) and prevent duplicate submissions, keeping
existing toast.success/toast.error and router.refresh behavior. Ensure the state
variable name and the function handleUnarchiveDirectory and
updateFeedbackRecordDirectoryAction are referenced so it's easy to locate and
change.
- Around line 48-58: The Manage handler (handleManageDirectory) issues async
requests without a loading flag, allowing duplicate clicks; add a piece of
component state e.g. loadingDirectoryId: string | null with setter
setLoadingDirectoryId, set it to directoryId before calling
getFeedbackRecordDirectoryDetailsAction and clear it in a finally block so it is
always reset, and use loadingDirectoryId === directory.id to disable the Manage
button and optionally show a spinner while fetching; apply the same pattern to
the other directory-details fetch handler in this file that follows the same
logic (the second occurrence of the fetch/response/setSelectedDirectory flow).

In
`@apps/web/modules/ee/feedback-record-directory/lib/feedback-record-directory.ts`:
- Around line 196-199: The code redundantly fetches the same directory in
buildProjectAssignmentPayload and updateFeedbackRecordDirectory; refactor by
changing buildProjectAssignmentPayload to accept the already-fetched
directory/details (from getFeedbackRecordDirectoryDetails) instead of calling
getFeedbackRecordDirectoryDetails itself, then update
updateFeedbackRecordDirectory to pass the fetched directory (and its projects if
needed) into buildProjectAssignmentPayload and remove the second
fetch/ResourceNotFoundError there; alternatively, if you prefer minimal change,
remove the existence check and getFeedbackRecordDirectoryDetails call inside
buildProjectAssignmentPayload and rely on updateFeedbackRecordDirectory's
validation before calling it.

In
`@apps/web/modules/ee/feedback-record-directory/types/feedback-record-directory.ts`:
- Around line 28-38: The zod schemas ZFeedbackRecordDirectoryCreateInput and
ZFeedbackRecordDirectoryUpdateInput currently use hardcoded user-facing messages
("Directory name is required" and "Directory name must be at least 1 character
long"); replace those literal messages with translatable error keys or codes
(e.g., "error.directory.name_required" / "error.directory.name_too_short") or
remove the custom message and supply a code via the message object so the UI can
look up translations in FormError; update the z.string().min(...) calls in
ZFeedbackRecordDirectoryCreateInput and ZFeedbackRecordDirectoryUpdateInput to
emit those keys instead of English text so the FormError/translation layer can
render localized strings.

In `@apps/web/modules/ui/components/multi-select/index.tsx`:
- Line 33: The default placeholder in the MultiSelect component is a hardcoded
English string; remove the raw string and use react-i18next instead: import
useTranslation from 'react-i18next', call const { t } = useTranslation() inside
the MultiSelect component, and replace the default placeholder = "Select
options..." with placeholder = t('multiSelect.placeholder') (use that
translation key or the project’s agreed key) so all user-facing text goes
through t().

In `@packages/database/schema.prisma`:
- Around line 1037-1048: The FeedbackRecordDirectory model lacks a standalone
index on organizationId which can improve queries like
getFeedbackRecordDirectories that filter solely by organizationId; add a
dedicated index to the model (e.g., using @@index([organizationId])) so database
query planners can efficiently use that column even though
@@unique([organizationId, name]) creates a composite index.