Create Incident Postmortem Template and Linking Flow

[edehvictor]

Summary

Incidents should have a consistent postmortem template linked from incident records and transparency views.

Drips Metadata

• Drips Complexity: High
• Expected Drips Points: 200
• Maintainer note: add this issue to the Stellar Wave from the Drips maintainer dashboard and set complexity to High. Adding the Stellar Wave label directly from GitHub may default to 100 points.

Acceptance Criteria

• Add a postmortem markdown template.
• Document required sections such as impact, root cause, timeline, and prevention.
• Add linking guidance for incident records.
• Keep template suitable for public transparency.

Technical Area

docs/, server/src/services/incidentService.ts, client/src/routes/incidents optional

[artylobos]

Submitted PR #535 for this issue: #535

Scope:

• adds docs/postmortems/TEMPLATE.md with required impact, root cause, timeline, resolution, prevention, and public transparency sections
• documents the postmortemUrl linking flow for incident records and transparency views
• adds an IncidentService guidance helper plus regression coverage for the canonical postmortem path/label

Validation:

• targeted IncidentService Jest: 5 passed
• touched-file ESLint passed
• touched-file TypeScript check passed
• docs link smoke check passed
• git diff --check passed

No secrets, private logs, keys, or private/system context included.

[TheDEV111]

@TheDEV111 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hican I work on your product postmortem pls

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheDEV111 to this issue.

[AbelOsaretin]

@AbelOsaretin has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AbelOsaretin to this issue.

[IbrahimIjai]

@IbrahimIjai has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Can I work on this sir...?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @IbrahimIjai to this issue.

[drips-wave]

Congratulations, @AbelOsaretin! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @AbelOsaretin: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @AbelOsaretin as part of the Stellar Wave Program's 5th Wave 🥳

😎 @AbelOsaretin: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.