cleveragents/cleveragents-core

Fork 3

spec: update persona `icon` field description to allow unconstrained string (remove emoji/single-character constraint) #8778

New issue

Open

opened 2026-04-13 23:35:35 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-13 23:35:35 +00:00

Owner

Metadata

Commit message: spec: update persona icon field to allow unconstrained string
Branch name: spec/persona-icon-field-unconstrained

Background and Context

In PR #4979 (docs: architecture — clarify TUI session export formats and persona schema fields), @freemo (Founder/CTO) decided that the icon field in the persona schema should remain as an unconstrained str type, rather than being restricted to "emoji or single character" as the current specification states.

The current specification says: "An emoji or single character"
The implementation uses: str = Field(default="")

@freemo's decision (2026-04-09): "You can keep it as a string, just create an issue to update the specification to match this change."

Expected Behavior

The specification for the icon field in the persona schema should be updated to:

Remove the "emoji or single character" constraint
Document it as an unconstrained string (e.g., "A display icon for the persona. Can be an emoji, single character, or short string such as CA for CleverAgents.")
Ensure the spec and implementation agree

Acceptance Criteria

The persona schema specification is updated to describe icon as an unconstrained str
The constraint "emoji or single character" is removed from the spec
The spec notes that common values include emoji, single characters, or short strings
The implementation's str = Field(default="") is confirmed as correct (no validation change needed)

Subtasks

Locate the persona schema specification in the docs (ADR-045 or related spec file)
Update the icon field description to remove the single-character constraint
Add examples of valid values (emoji, single char, short string like "CA")
Verify the implementation matches the updated spec

Definition of Done

All subtasks completed
Specification updated and committed
PR submitted and merged

Automated by CleverAgents Bot
Agent: new-issue-creator

## Metadata - **Commit message**: `spec: update persona icon field to allow unconstrained string` - **Branch name**: `spec/persona-icon-field-unconstrained` ## Background and Context In PR #4979 (docs: architecture — clarify TUI session export formats and persona schema fields), @freemo (Founder/CTO) decided that the `icon` field in the persona schema should remain as an unconstrained `str` type, rather than being restricted to "emoji or single character" as the current specification states. The current specification says: "An emoji or single character" The implementation uses: `str = Field(default="")` @freemo's decision (2026-04-09): "You can keep it as a string, just create an issue to update the specification to match this change." ## Expected Behavior The specification for the `icon` field in the persona schema should be updated to: - Remove the "emoji or single character" constraint - Document it as an unconstrained string (e.g., "A display icon for the persona. Can be an emoji, single character, or short string such as `CA` for CleverAgents.") - Ensure the spec and implementation agree ## Acceptance Criteria - [ ] The persona schema specification is updated to describe `icon` as an unconstrained `str` - [ ] The constraint "emoji or single character" is removed from the spec - [ ] The spec notes that common values include emoji, single characters, or short strings - [ ] The implementation's `str = Field(default="")` is confirmed as correct (no validation change needed) ## Subtasks - [ ] Locate the persona schema specification in the docs (ADR-045 or related spec file) - [ ] Update the `icon` field description to remove the single-character constraint - [ ] Add examples of valid values (emoji, single char, short string like "CA") - [ ] Verify the implementation matches the updated spec ## Definition of Done - All subtasks completed - Specification updated and committed - PR submitted and merged --- **Automated by CleverAgents Bot** Agent: new-issue-creator

HAL9000 added this to the v3.7.0 milestone

2026-04-13 23:35:49 +00:00

HAL9000 added the

labels

2026-04-13 23:37:49 +00:00

HAL9000 referenced this issue

2026-04-13 23:37:51 +00:00

[AUTO-SPEC] Status: Spec Evolution Pool Supervisor — Tracking Issue (Cycle 1) #8784

HAL9000 referenced this issue

2026-04-13 23:38:36 +00:00

[AUTO-HUMAN] Status: Human Liaison Pool Supervisor (Cycle 1) #8771

HAL9000 added the

MoSCoW

Could have

label

2026-04-14 03:17:38 +00:00

HAL9000 commented

2026-04-14 03:17:45 +00:00

Author

Owner

[GROOMED] Quality analysis complete for issue #8778.

Label Added: MoSCoW/Could have (was missing)
Existing Labels: Priority/Low, State/Verified, Type/Task ✓
Milestone: v3.7.0 (already set) ✓

Analysis:

Issue has proper format: Metadata (Commit, Branch) ✓, Background ✓, Acceptance Criteria ✓, Subtasks ✓, Definition of Done ✓
Spec alignment fix for persona icon field — low priority, could have
Founder/CTO decision documented in background ✓
No parent Epic link found — consider linking to the TUI/Persona epic

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor
Worker: [AUTO-GROOM-1]

[GROOMED] Quality analysis complete for issue #8778. **Label Added**: MoSCoW/Could have (was missing) **Existing Labels**: Priority/Low, State/Verified, Type/Task ✓ **Milestone**: v3.7.0 (already set) ✓ **Analysis**: - Issue has proper format: Metadata (Commit, Branch) ✓, Background ✓, Acceptance Criteria ✓, Subtasks ✓, Definition of Done ✓ - Spec alignment fix for persona icon field — low priority, could have - Founder/CTO decision documented in background ✓ - No parent Epic link found — consider linking to the TUI/Persona epic --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-1]

HAL9000 referenced this issue

2026-04-14 03:19:30 +00:00

[AUTO-GROOM] Grooming Pool Supervisor — Cycle 3 Status #8841