ccopeland/red
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(phase-12.1): add per-field text editing gap phase to roadmap and requirements

Browse Source
This commit is contained in:
Chandler Copeland
2026-03-21 16:03:37 -06:00
parent db8a63f6a3
commit 974574e561
2 changed files with 23 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
.planning/REQUIREMENTS.md
View File

@@ -94,6 +94,12 @@
- [x] **PREV-01**: Agent sees a live filled preview of the fully-prepared document (text filled, signatures embedded) before sending to client - [x] **PREV-01**: Agent sees a live filled preview of the fully-prepared document (text filled, signatures embedded) before sending to client
### Per-Field Text Editing
- [ ] **TXTF-01**: Agent can click a placed text field box on the PDF to select it and type a value for that specific field — each text field holds its own independent value (keyed by field ID)
- [ ] **TXTF-02**: When a text field is selected, PreparePanel shows quick-fill suggestion buttons (Client Name, Property Address, Client Email) that insert the corresponding value into the selected field
- [ ] **TXTF-03**: Text fill values entered per-field appear correctly embedded in the preview PDF and the final prepared PDF; the staleness token resets on any text field value change
## v2 Requirements ## v2 Requirements
### MLS Integration ### MLS Integration
@@ -189,6 +195,9 @@ Which phases cover which requirements. Updated during roadmap creation.
| INIT-03 | Phase 11.1 | Complete | | INIT-03 | Phase 11.1 | Complete |
| INIT-04 | Phase 11.1 | Complete | | INIT-04 | Phase 11.1 | Complete |
| PREV-01 | Phase 12 | Complete | | PREV-01 | Phase 12 | Complete |
| TXTF-01 | Phase 12.1 | Pending |
| TXTF-02 | Phase 12.1 | Pending |
| TXTF-03 | Phase 12.1 | Pending |
| AI-01 | Phase 13 | Pending | | AI-01 | Phase 13 | Pending |
| AI-02 | Phase 13 | Pending | | AI-02 | Phase 13 | Pending |

15
.planning/ROADMAP.md
View File

@@ -164,6 +164,7 @@ Plans:
- [x] **Phase 11: Agent Saved Signature and Signing Workflow** - Draw once, save, apply to agent signature fields during document preparation before sending to client (completed 2026-03-21) - [x] **Phase 11: Agent Saved Signature and Signing Workflow** - Draw once, save, apply to agent signature fields during document preparation before sending to client (completed 2026-03-21)
- [x] **Phase 11.1: Agent and Client Initials (INSERTED)** - Agent draws initials once, saves to profile, places agent-initials fields (embedded at prepare time); client-initials fields already wired via existing 'initials' type (completed 2026-03-21) - [x] **Phase 11.1: Agent and Client Initials (INSERTED)** - Agent draws initials once, saves to profile, places agent-initials fields (embedded at prepare time); client-initials fields already wired via existing 'initials' type (completed 2026-03-21)
- [x] **Phase 12: Filled Document Preview** - Agent sees a live filled preview of the fully-prepared document before the Send button is available (completed 2026-03-21) - [x] **Phase 12: Filled Document Preview** - Agent sees a live filled preview of the fully-prepared document before the Send button is available (completed 2026-03-21)
- [ ] **Phase 12.1: Per-Field Text Editing and Quick-Fill (INSERTED)** - Agent clicks a text field box to edit its value inline; PreparePanel shows quick-fill suggestions (client name, address, etc.) when a field is selected; text fill data is keyed by field ID
- [ ] **Phase 13: AI Field Placement and Pre-fill** - One-click AI auto-placement of all field types plus pre-fill of text fields from client profile data - [ ] **Phase 13: AI Field Placement and Pre-fill** - One-click AI auto-placement of all field types plus pre-fill of text fields from client profile data
## Phase Details ## Phase Details
@@ -261,9 +262,21 @@ Plans:
- [ ] 12-01-PLAN.md — POST /api/documents/[id]/preview route (reuses preparePdf in preview mode, versioned path, staleness token), PreviewModal component with react-pdf rendering + ArrayBuffer copy - [ ] 12-01-PLAN.md — POST /api/documents/[id]/preview route (reuses preparePdf in preview mode, versioned path, staleness token), PreviewModal component with react-pdf rendering + ArrayBuffer copy
- [x] 12-02-PLAN.md — Send button gating logic (disabled until preview generated, re-disabled on field change) + full Phase 12 human verification checkpoint (completed 2026-03-21) - [x] 12-02-PLAN.md — Send button gating logic (disabled until preview generated, re-disabled on field change) + full Phase 12 human verification checkpoint (completed 2026-03-21)
### Phase 12.1: Per-Field Text Editing and Quick-Fill (INSERTED)
**Goal**: Agent clicks a text field box on the PDF to select it, types a value directly (or clicks a quick-fill suggestion from the PreparePanel), and each text field holds its own independent value keyed by field ID — replacing the broken positional text fill approach from Phase 12
**Depends on**: Phase 12
**Requirements**: TXTF-01, TXTF-02, TXTF-03
**Success Criteria** (what must be TRUE):
1. Clicking a text field box on the PDF selects it and allows the agent to type a value for that specific field
2. Each text field box independently holds its own value (keyed by field ID) — changing one field does not affect others
3. When a text field is selected, PreparePanel shows quick-fill suggestion buttons (Client Name, Property Address, Client Email) that insert the corresponding value into the selected field
4. Text fill values entered per-field appear correctly embedded in the preview PDF and the final prepared PDF
5. The staleness token (previewToken) is reset when any text field value changes
**Plans**: TBD
### Phase 13: AI Field Placement and Pre-fill ### Phase 13: AI Field Placement and Pre-fill
**Goal**: Agent clicks one button and AI auto-places all field types on the PDF in correct positions and pre-fills text fields with known client and property data **Goal**: Agent clicks one button and AI auto-places all field types on the PDF in correct positions and pre-fills text fields with known client and property data
**Depends on**: Phase 12 **Depends on**: Phase 12.1
**Requirements**: AI-01, AI-02 **Requirements**: AI-01, AI-02
**Success Criteria** (what must be TRUE): **Success Criteria** (what must be TRUE):
1. Agent can click "AI Auto-place" and the system extracts text from the PDF, classifies field labels via GPT-4o-mini, and populates the FieldPlacer with placed fields — no manual drag required 1. Agent can click "AI Auto-place" and the system extracts text from the PDF, classifies field labels via GPT-4o-mini, and populates the FieldPlacer with placed fields — no manual drag required