Content sweep phase 2: remaining Betty Sue references in templates and SOPs #248
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-api#248
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Follow-up from
forgejo_admin/pal-e-api#247(content sweep phase 1). Discovered during execution — 14 notes outside the original 13-note scope still reference Betty Sue.Repo
forgejo_admin/pal-e-apiUser Story
As Lucas,
I want all pal-e-docs references to reflect the current agent name (Ava),
So that the knowledge base is fully consistent.
Context
Phase 1 sweep (pal-e-api#247) updated 13 core notes. Dottie's verification found 14 more notes with Betty Sue references: template-ticket, arch-domain-pal-e-agency, agent-penny, template-issue, template-issue-task, convention-memory-scope, convention-block-first-access, worktree-workflow, enforcement-architecture, platform-maturity-matrix, sop-mcp-server-recovery, template-plan, template-phase, plan-pal-e-pac.
Same mechanical pattern — update_block surgical edits, Dottie task.
File Targets
No file targets — MCP-only.
Notes to update (14, via update_block):
Acceptance Criteria
Test Expectations
Constraints
Checklist
Related