feat: Update behavior rules and documentation for workspace maintenance and flow references

This commit is contained in:
2026-04-16 07:50:07 -06:00
parent a375b3c3b1
commit 1f57597ca3
21 changed files with 146 additions and 15 deletions

View File

@@ -16,6 +16,8 @@ These rules keep standups, Jira notes, and Mattermost messages aligned with the
- Distinguish clearly between the current issue, unrelated preexisting bugs, workarounds, and follow-up work
- Prefer evidence-backed statements over intuition when communicating status
- Include branch, build, environment, account, flow, or entry-point details when they materially affect reproduction or ownership
- When reporting several updates for the same Jira item, group them under one top-level `JIRA-ID - Title` bullet with indented markdown sub-bullets
- Use real flow identifiers and page names when shorthand could be ambiguous
- Route ownership explicitly when the issue belongs to a consumer app, service/configuration, or another framework instead of XFlow
- Do not present a fix as ready if it introduces a new bug or unresolved regression
- Administrative/project-tracking updates should be prompt when others are visibly waiting on them