Skip to content

Address surface cache orphaning risk #352

@davidpoblador

Description

@davidpoblador

Context

The architecture & security review (Section 5 - State Management) flagged a medium-severity concern:

Surface cache orphaning: If the projects array is modified without notification, orphaned Ghostty surfaces remain cached in memory. Currently mitigated through notification-based cleanup in ContentView, but direct mutation could bypass this.

Suggested action

Add a cleanup listener on project removal that explicitly evicts cached surfaces for deleted workstreams, rather than relying solely on NotificationCenter-based cleanup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions