Content sweep: rename Betty Sue → Ava across pal-e-docs notes

forgejo_admin commented

2026-03-29 03:44:58 +00:00

Contributor

Type

Feature

Lineage

Follow-up from forgejo_admin/claude-custom#224 (Betty Sue → Ava personality evolution). Discovered during scope review of board item #643. Depends on #224 merging first.

Repo

forgejo_admin/pal-e-api

User Story

As Lucas,
I want all pal-e-docs knowledge base references to reflect the current agent name (Ava),
So that the knowledge base is consistent with the running system and doesn't confuse future sessions.

Context

After claude-custom#224 merges, the running agent will be Ava but pal-e-docs notes will still reference Betty Sue. This is a Dottie-class task — surgical block updates across multiple notes using update_block. No full note rewrites.

File Targets

No file targets — this is a pal-e-docs content operation via MCP tools.

Notes to update (13 total, via update_block):

agent-workflow — role descriptions
project-pal-e-agency — user stories table (PM role row), architecture diagram (management layer)
convention-agent-autonomy-levels — autonomy level references
convention-escalation-triggers — escalation references
convention-validation-checkpoints — checkpoint references
sop-index — agent name references
agent-spawn-conventions — spawn context references
pr-lifecycle — workflow references
decision-agent-dottie — decision context
sop-board-workflow — board workflow references
agent-dottie — references to main session agent
convention-cross-pillar-triggers — trigger matrix references
plan-pal-e-agency — plan content references

Notes to explicitly EXCLUDE:

agent-betty-sue — archived by claude-custom#224, keep as historical record
Review notes (e.g. review-643-*, review-646-*) — historical records, don't rewrite
Completed phase notes with "Owner: Betty Sue" — historical records of who owned the work at that time

Files the agent should NOT touch:

Any repo files — this is MCP-only work

Acceptance Criteria

search_notes(query="Betty Sue") returns only archived/historical/completed notes
All 13 active notes listed above reference "Ava" where they previously said "Betty Sue"
Block-level updates only — no full note rewrites
Completed phase notes left untouched (historical accuracy)

Test Expectations

Manual: search_notes(query="Betty Sue") filtered to active notes returns 0 non-excluded results
Manual: search_notes(query="Ava") returns the expected updated notes
Run command: N/A (MCP operations, not file changes)

Constraints

Use update_block for surgical edits, not update_note
Do not touch archived notes or completed phase notes
Do not rewrite content beyond the name change — preserve existing wording
Dottie agent task — no code changes
Depends on claude-custom#224 merging first — don't rename in docs until the agent is actually renamed

Checklist

All 13 active notes updated
Search verification passes
No unrelated content changes

pal-e-agency — project
forgejo_admin/claude-custom#224 — parent ticket (personality evolution)
Board item #643 — parent board item (depends on)

### Type Feature ### Lineage Follow-up from `forgejo_admin/claude-custom#224` (Betty Sue → Ava personality evolution). Discovered during scope review of board item #643. Depends on #224 merging first. ### Repo `forgejo_admin/pal-e-api` ### User Story As Lucas, I want all pal-e-docs knowledge base references to reflect the current agent name (Ava), So that the knowledge base is consistent with the running system and doesn't confuse future sessions. ### Context After claude-custom#224 merges, the running agent will be Ava but pal-e-docs notes will still reference Betty Sue. This is a Dottie-class task — surgical block updates across multiple notes using `update_block`. No full note rewrites. ### File Targets No file targets — this is a pal-e-docs content operation via MCP tools. **Notes to update (13 total, via `update_block`):** - `agent-workflow` — role descriptions - `project-pal-e-agency` — user stories table (PM role row), architecture diagram (management layer) - `convention-agent-autonomy-levels` — autonomy level references - `convention-escalation-triggers` — escalation references - `convention-validation-checkpoints` — checkpoint references - `sop-index` — agent name references - `agent-spawn-conventions` — spawn context references - `pr-lifecycle` — workflow references - `decision-agent-dottie` — decision context - `sop-board-workflow` — board workflow references - `agent-dottie` — references to main session agent - `convention-cross-pillar-triggers` — trigger matrix references - `plan-pal-e-agency` — plan content references **Notes to explicitly EXCLUDE:** - `agent-betty-sue` — archived by claude-custom#224, keep as historical record - Review notes (e.g. `review-643-*`, `review-646-*`) — historical records, don't rewrite - Completed phase notes with "Owner: Betty Sue" — historical records of who owned the work at that time Files the agent should NOT touch: - Any repo files — this is MCP-only work ### Acceptance Criteria - [ ] `search_notes(query="Betty Sue")` returns only archived/historical/completed notes - [ ] All 13 active notes listed above reference "Ava" where they previously said "Betty Sue" - [ ] Block-level updates only — no full note rewrites - [ ] Completed phase notes left untouched (historical accuracy) ### Test Expectations - [ ] Manual: `search_notes(query="Betty Sue")` filtered to active notes returns 0 non-excluded results - [ ] Manual: `search_notes(query="Ava")` returns the expected updated notes - Run command: N/A (MCP operations, not file changes) ### Constraints - Use `update_block` for surgical edits, not `update_note` - Do not touch archived notes or completed phase notes - Do not rewrite content beyond the name change — preserve existing wording - Dottie agent task — no code changes - **Depends on claude-custom#224 merging first** — don't rename in docs until the agent is actually renamed ### Checklist - [ ] All 13 active notes updated - [ ] Search verification passes - [ ] No unrelated content changes ### Related - `pal-e-agency` — project - `forgejo_admin/claude-custom#224` — parent ticket (personality evolution) - Board item #643 — parent board item (depends on)

forgejo_admin commented

2026-03-29 04:18:24 +00:00

Author

Contributor

Scope Review: NEEDS_REFINEMENT

Review note: review-646-2026-03-28

Issue template is complete and traceability is solid, but the note target list is incomplete — search reveals 8 additional active notes with Betty Sue references not enumerated in the spec.

[BODY] Add 8 missing notes to targets: sop-index, agent-spawn-conventions, pr-lifecycle, decision-agent-dottie, sop-board-workflow, agent-dottie, convention-cross-pillar-triggers, plan-pal-e-agency
[BODY] Add explicit exclusion for completed phase notes (historical records)
[BODY] Add AC: "Completed phase notes are NOT modified"
[LABEL] Add depends:643 label to board item #646 — hard dependency on personality evolution merging first

## Scope Review: NEEDS_REFINEMENT Review note: `review-646-2026-03-28` Issue template is complete and traceability is solid, but the note target list is incomplete — search reveals 8 additional active notes with Betty Sue references not enumerated in the spec. - **[BODY]** Add 8 missing notes to targets: `sop-index`, `agent-spawn-conventions`, `pr-lifecycle`, `decision-agent-dottie`, `sop-board-workflow`, `agent-dottie`, `convention-cross-pillar-triggers`, `plan-pal-e-agency` - **[BODY]** Add explicit exclusion for completed phase notes (historical records) - **[BODY]** Add AC: "Completed phase notes are NOT modified" - **[LABEL]** Add `depends:643` label to board item #646 — hard dependency on personality evolution merging first

forgejo_admin commented

2026-03-29 04:21:59 +00:00

Author

Contributor

Scope refinement (review-646-2026-03-28):

Expanded note target list from 5 → 13 (added: sop-index, agent-spawn-conventions, pr-lifecycle, decision-agent-dottie, sop-board-workflow, agent-dottie, convention-cross-pillar-triggers, plan-pal-e-agency)
Added explicit exclusions: completed phase notes with "Owner: Betty Sue" (historical accuracy)
Added dependency on claude-custom#224 — docs rename happens after agent rename ships
Board item #646 needs depends:643 label

**Scope refinement (review-646-2026-03-28):** 1. Expanded note target list from 5 → 13 (added: sop-index, agent-spawn-conventions, pr-lifecycle, decision-agent-dottie, sop-board-workflow, agent-dottie, convention-cross-pillar-triggers, plan-pal-e-agency) 2. Added explicit exclusions: completed phase notes with "Owner: Betty Sue" (historical accuracy) 3. Added dependency on claude-custom#224 — docs rename happens after agent rename ships 4. Board item #646 needs depends:643 label

forgejo_admin commented

2026-03-29 04:24:17 +00:00

Author

Contributor

Scope Review: APPROVED (re-review)

Review note: review-646-2026-03-28-r2
Previous review: review-646-2026-03-28 (NEEDS_REFINEMENT)

All 4 refinement recommendations resolved:

Note target list expanded 5 → 13 (all active notes with Betty Sue references enumerated)
Explicit exclusions added for completed phase notes (historical accuracy)
AC added for completed phase notes left untouched
depends:643 label added to board item

Ticket is ready for execution once dependency #643 (Betty Sue → Ava personality evolution) merges.

## Scope Review: APPROVED (re-review) Review note: `review-646-2026-03-28-r2` Previous review: `review-646-2026-03-28` (NEEDS_REFINEMENT) All 4 refinement recommendations resolved: - Note target list expanded 5 → 13 (all active notes with Betty Sue references enumerated) - Explicit exclusions added for completed phase notes (historical accuracy) - AC added for completed phase notes left untouched - `depends:643` label added to board item Ticket is ready for execution once dependency #643 (Betty Sue → Ava personality evolution) merges.

forgejo_admin commented

2026-03-29 04:33:50 +00:00

Author

Contributor

Discovered scope from QA review of PR #225:

QA nit: agents/ava.md Constraints section retains "above your pay grade" language that conflicts with the new partnership personality. Add to this sweep — update the constraint wording in the agent-ava pal-e-docs note to match the JARVIS voice (e.g., "decisions that require Lucas's explicit input" instead of "above your pay grade").

**Discovered scope from QA review of PR #225:** QA nit: `agents/ava.md` Constraints section retains "above your pay grade" language that conflicts with the new partnership personality. Add to this sweep — update the constraint wording in the `agent-ava` pal-e-docs note to match the JARVIS voice (e.g., "decisions that require Lucas's explicit input" instead of "above your pay grade").