Disable vernacular field when word or sense is protected

[Copilot]

• Understand the current code structure and protection model
• Simplify protection check to use accessibility property
• Update isDisabled condition to check accessibility === Status.Protected
• Update tests to use Status.Protected/Active instead of protectReasons
• Move protection tests into vernacular describe block
• Remove redundant test for enabled state (implicit in first test)
• Run tests to validate changes - all tests pass (9/9 RecentEntry tests, 76/76 DataEntry suite tests)
• Lint the code - linter passes with no warnings

Summary

Updated the implementation based on code review feedback to use the simpler accessibility property instead of checking the protectReasons array. The vernacular field is now disabled when either the word or sense has accessibility === Status.Protected. Test organization improved by moving protection tests into the vernacular describe block and removing the redundant test that checked the enabled state (already implicit in the first vernacular test).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[DataEntry] Evaluate what entries are changable</issue_title>
<issue_description>When you select an existing word's sense, the current domain is added to the sense and it appear in the table. If the word has multiple senses, the vernacular is locked from editing. However, in all other cases (even with a protected word), the vernacular and gloss are both editable.

Todo:

• In src/components/DataEntry/DataEntryTable/RecentEntry.tsx, Also make vernacular isDisabled if the word or sense is protected.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [DataEntry] Evaluate what entries are changable #3961

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

This change is 

[imnasnainaec]

@copilot

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.40%. Comparing base (0298e39) to head (3e9cd2b).
⚠️ Report is 36 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3972   +/-   ##
=======================================
  Coverage   74.40%   74.40%           
=======================================
  Files         291      291           
  Lines       10790    10790           
  Branches     1351     1351           
=======================================
  Hits         8028     8028           
  Misses       2373     2373           
  Partials      389      389           

Flag	Coverage Δ
backend	85.45% <ø> (ø)
frontend	65.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[imnasnainaec]

@copilot

[imnasnainaec]

@imnasnainaec reviewed 1 of 2 files at r2, 1 of 1 files at r5, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @copilot)

[jasonleenaylor]

@jasonleenaylor reviewed 1 of 2 files at r2, 1 of 1 files at r5, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @copilot)