Filing Bugs

import { Aside } from ‘@astrojs/starlight/components’;

Bugs are tracked on GitHub: https://github.com/ptah-extensions/ptah-extension/issues.

Before you file

1. Search existing issues — yours may already be known.
2. Reproduce on the latest version. Each release fixes a handful of regressions.
3. Try an isolated workspace. Some problems are workspace-specific.

What to include

A useful issue answers these questions:

Section	What to include
What happened	One-sentence summary. Not a stack trace — the story.
Expected	What you expected to happen instead.
Steps	Numbered, minimal reproduction. Start from “launch Ptah”.
Diagnostics	Paste the output of Help → Copy diagnostics.
Logs	Attach ptah-YYYY-MM-DD.log if the problem produces one.
Screenshot / recording	Especially useful for UI glitches.

Template

### What happened

<one-sentence summary>

### Expected

<what should have happened>

### Steps to reproduce

1.
2.
3.

### Diagnostics

<paste from Help → Copy diagnostics>

### Logs / screenshots

<attach files>

Severity labels we care about

• crash — Ptah quits unexpectedly.
• data-loss — Work disappeared without warning.
• security — Credential leakage or sandbox escape. Do not file publicly — email [email protected] instead.
• regression — Worked in a previous version, broken in the current one.

Security issues should never go into the public tracker. Use the private disclosure email above. We coordinate a fix before any public write-up.

Feature requests

Feature requests are welcome on the same tracker, tagged enhancement. Include the problem you’re trying to solve, not only the feature you have in mind — there’s often a simpler path that gets you there.