#115 - Add input length limits on document generation fields — max 5000 chars per field - pook/compliancebot

pook commented

2026-04-08 20:01:33 -04:00

Owner

Problem

Issue #97 covers this but is stale. Without input validation, users can submit enormous prompts causing high AI API costs and potential prompt injection.

Task

Add validation middleware or schema validation (e.g., zod/joi) on the document generation endpoint.
Enforce max length of 5000 characters on each text input field (company name, business description, etc.).
Return 400 with { error: 'validation_error', field: '<name>', message: 'exceeds maximum length of 5000 characters' } on violation.
Add tests for both valid and over-limit inputs.

Acceptance Criteria

Inputs exceeding 5000 chars are rejected with 400.
Error response identifies the offending field.
Tests cover the boundary (4999, 5000, 5001 chars).

Generated by CEO Planner (priority: 3)

## Problem Issue #97 covers this but is stale. Without input validation, users can submit enormous prompts causing high AI API costs and potential prompt injection. ## Task 1. Add validation middleware or schema validation (e.g., zod/joi) on the document generation endpoint. 2. Enforce max length of 5000 characters on each text input field (company name, business description, etc.). 3. Return 400 with `{ error: 'validation_error', field: '<name>', message: 'exceeds maximum length of 5000 characters' }` on violation. 4. Add tests for both valid and over-limit inputs. ## Acceptance Criteria - Inputs exceeding 5000 chars are rejected with 400. - Error response identifies the offending field. - Tests cover the boundary (4999, 5000, 5001 chars). --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-08 20:01:33 -04:00

pook commented

2026-04-09 02:04:16 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 6h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 6h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-09 02:15:10 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 6h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 6h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook referenced this issue

2026-04-09 02:16:39 -04:00

Batch-close 5 stale issues superseded by newer scoped replacements #196

pook commented

2026-04-09 02:17:34 -04:00

Author

Owner

Closing as duplicate of #97 which covers identical scope (input length limits on generation fields).

pook closed this issue

2026-04-09 02:17:40 -04:00

pook referenced this issue from a pull request that will close it,

2026-04-09 02:17:46 -04:00