## Implementation Plan

### Objective
Remove all character‑limit enforcement on the AI correction and AI modifier prompt fields across the full stack. Six enforcement points and two documentation strings must be updated. The database schema is already unlimited and needs no change.

### Changes Required (8 files, 8 modifications)

1. **`devplacepy/models.py`** – Lines 256 and 262  
   Remove the `max_length=2000` argument from both `AiModifierForm.prompt` and its correction counterpart (likely `AiCorrectionForm.prompt`). The field will become `Field()`, accepting any length.

2. **`devplacepy/templates/profile.html`** – Lines 225 and 250  
   Remove the `maxlength="2000"` attribute from both `<textarea data-ai-correction-prompt>` and `<textarea data-ai-modifier-prompt>`. After removal, the browser will not enforce a client‑side length cap.

3. **`devplacepy/services/devii/ai_correction/controller.py`** – Line 73  
   Change `str(prompt_raw).strip()[:2000]` to `str(prompt_raw).strip()`. The hard slice is the final enforcement point for the Devii agent path; removing it passes the entire prompt.

4. **`devplacepy/services/devii/ai_modifier/controller.py`** – Line 73  
   Same change as above: remove the `[:2000]` slice.

5. **`devplacepy/services/devii/actions/ai_correction_actions.py`** – Line 64  
   Update the docstring from `"The correction instruction (max 2000 chars)."` to `"The correction instruction."` or `"The correction instruction (no length limit)."`. The important part is removing the misleading “max 2000 chars” claim.

6. **`devplacepy/services/devii/actions/ai_modifier_actions.py`** – Line 67  
   Same docstring change as above for the modifier action.

### No Changes Required
- Database schema (`devplacepy/database/schema.py`) – already unlimited `TEXT`.
- All layers marked as “bypassed” in the investigation (routes, JSON schemas, services, JS, config, account defaults).
- Existing tests – they use short prompts; no test code needs modification.

### Verification and Definition of Done

After implementing all eight changes locally, run the following checks:

- [ ] **Grep confirmation** – No remaining references to the old 2000‑character limit in any changed file:
  ```bash
  grep -n 'max_length=2000\|maxlength="2000"\|\[:2000\]' \
    devplacepy/models.py \
    devplacepy/templates/profile.html \
    devplacepy/services/devii/ai_correction/controller.py \
    devplacepy/services/devii/ai_modifier/controller.py
  ```
  Expected output: *no matches*.

- [ ] **Docstring grep** – Ensure both action files no longer contain “max 2000 chars”:
  ```bash
  grep -n 'max 2000 chars' \
    devplacepy/services/devii/actions/ai_correction_actions.py \
    devplacepy/services/devii/actions/ai_modifier_actions.py
  ```
  Expected output: *no matches*.

- [ ] **Unit tests pass** – Run the project’s standard test command:
  ```bash
  pip install -e '.[dev]' -q && make test-unit
  ```
  Expected: all tests pass (existing tests are unaffected by the removal).

- [ ] **Lint passes** – Run Ruff on the changed files (or whole project):
  ```bash
  pip install -q ruff && ruff check .
  ```
  Expected: no new linting errors.

- [ ] **Manual smoke test (optional but recommended)** – Open the profile settings page in a browser, paste a prompt longer than 2000 characters, and verify it saves and loads completely. This confirms the HTML `maxlength` removal and server‑side validation change work end‑to‑end.

All checks above must pass for the change to be considered complete. No new tests need to be written; the existing test suite will continue to validate the core functionality with short prompts.