agent-postmortem 0.3.4__tar.gz

agent_postmortem-0.3.4/.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "agent-postmortem",
+  "description": "The agent-postmortem plugin for Claude Code: it reads the Claude Code logs already on your machine and tells you which agent's 'done' you can't trust, and what to run next. Claude Code only.",
+  "owner": {
+    "name": "zeyusuntt"
+  },
+  "plugins": [
+    {
+      "name": "agent-postmortem",
+      "source": "./plugin",
+      "description": "Reads the Claude Code logs already on your machine and tells you which agent's 'done' you can't trust, and what to run next."
+    }
+  ]
+}

agent_postmortem-0.3.4/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,54 @@
+name: Crash or error
+description: agent-postmortem crashed, printed an error, or failed to install. For a wrong verdict or confusing output, use those templates.
+title: "[bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug. The most useful thing you can attach is the
+        redacted bug report for the run that triggered it:
+
+        ```
+        agent-postmortem run <id> --bug-report
+        ```
+
+        Redacted: paths, ids, emails, account names, agent names. Evidence
+        lines are pointers and marker codes only (no transcript text) at
+        the default level. Do not add `--local`, `--raw`, or `--evidence`
+        for a report you post here. Read the whole output before posting
+        it anyway.
+  - type: textarea
+    attributes:
+      label: What happened
+      description: What you expected instead, and what you saw.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Bug report output
+      description: |
+        The output of `agent-postmortem run <id> --bug-report` for the run
+        that shows the problem, at the default level. Paths, ids, emails,
+        account names, and agent names are already redacted, and evidence
+        lines carry no transcript text. Read it before pasting.
+      render: markdown
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: agent-postmortem version
+      description: Output of `agent-postmortem --version`.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Claude Code version
+      description: Output of `claude --version`.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Python version and OS
+    validations:
+      required: true

agent_postmortem-0.3.4/.github/ISSUE_TEMPLATE/confusing_output.yml

@@ -0,0 +1,55 @@
+name: Confusing output
+description: A line or section you could not understand or act on, even though it may be correct.
+title: "[output]: "
+labels: ["confusing-output"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Output that is right but unclear is still a bug. Copy the confusing part
+        from the default-level output; if the whole run helps, attach:
+
+        ```
+        agent-postmortem run <run-id> --bug-report
+        ```
+
+        It is redacted by default and carries no transcript text. Read it before
+        posting. Do not add `--local`, `--raw` or `--evidence`, and never paste a
+        raw transcript here.
+  - type: textarea
+    attributes:
+      label: The confusing line or section
+      description: Copied from the default-level output of `run`, `scan`, `rescue`, `watch` or a hook message.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What you expected it to tell you
+      description: What you were trying to decide, and what would have made the next step clear.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Bug report output
+      description: The output of `agent-postmortem run <run-id> --bug-report`, at the default level.
+      render: markdown
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: Claude Code version
+      description: Output of `claude --version`.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: agent-postmortem version
+      description: Output of `agent-postmortem --version`.
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: Privacy
+      options:
+        - label: I pasted only default-level output (no `--local`, `--raw` or `--evidence`) and no transcript text.
+          required: true

agent_postmortem-0.3.4/.github/ISSUE_TEMPLATE/detector_request.yml

@@ -0,0 +1,38 @@
+name: Detector request
+description: Propose a new failure pattern for agent-postmortem to detect.
+title: "[detector]: "
+labels: ["detector-request"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A good detector request pins down an observable pattern in the run
+        data (journal, meta, or transcript), not just a symptom you noticed
+        once. See `docs/DESIGN.md` section 4.3 for what an existing detector
+        looks like and section 6 for the fixture format.
+  - type: textarea
+    attributes:
+      label: The failure pattern
+      description: What silently went wrong, and how you'd recognize it from the run data alone.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Evidence
+      description: |
+        The output of `agent-postmortem run <id> --bug-report` for a run
+        that shows the pattern, at the default level (redacted, no
+        transcript text), plus the shape of the evidence in your own words,
+        for example "the last user entry is the interrupt sentence and the
+        journal has a second started event for the same key". Never paste a
+        raw transcript, a `journal.jsonl` line, a real session id or an
+        absolute path.
+      render: markdown
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: What rule would have prevented it
+      description: If this became a suggested rule (docs/DESIGN.md section 9), what should it say?
+    validations:
+      required: false

agent_postmortem-0.3.4/.github/ISSUE_TEMPLATE/run_shape_not_covered.yml

@@ -0,0 +1,70 @@
+name: My run shape isn't covered
+description: You run Claude Code in a way the tool does not read yet (claude -p, background subagents, claude --bg, agent teams, SendMessage, or another shape).
+title: "[run shape]: "
+labels: ["run-shape"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        The README's "What it covers" table lists the shapes the tool handles
+        today. Support for a new shape is built from real runs of that shape,
+        so a report from you is the most useful thing there is. Attach the
+        default-level bug report for one such run:
+
+        ```
+        agent-postmortem run <run-id> --bug-report
+        ```
+
+        It is redacted by default and carries no transcript text. Read it before
+        posting. Do not add `--local`, `--raw` or `--evidence`, and never paste a
+        raw transcript here. If more detail is needed, we will ask for counts or
+        a synthetic reproduction, never for your transcripts.
+  - type: dropdown
+    attributes:
+      label: Run shape
+      options:
+        - claude -p (headless)
+        - Background subagents (run_in_background)
+        - claude --bg session
+        - Agent team
+        - Cross-session messages (SendMessage)
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What went wrong in that run
+      description: What you saw, for example an agent that said "done" but whose work was missing, a killed agent, or a job that never finished, and how you found out.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: How the run was launched
+      description: The command or setup in general terms (flags, hooks, tools). No prompts and no transcript text.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Bug report output
+      description: The output of `agent-postmortem run <run-id> --bug-report`, at the default level.
+      render: markdown
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: Claude Code version
+      description: Output of `claude --version`.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: agent-postmortem version
+      description: Output of `agent-postmortem --version`.
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: Privacy
+      options:
+        - label: I pasted only default-level output (no `--local`, `--raw` or `--evidence`) and no transcript text.
+          required: true

agent_postmortem-0.3.4/.github/ISSUE_TEMPLATE/wrong_verdict.yml

@@ -0,0 +1,70 @@
+name: Wrong verdict
+description: agent-postmortem said something about a run that the run does not show (a kill, a retry, a failure, a "done", or a work-at-risk line).
+title: "[verdict]: "
+labels: ["wrong-verdict"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for checking the tool against what really happened. Attach the
+        default-level bug report for the run:
+
+        ```
+        agent-postmortem run <run-id> --bug-report
+        ```
+
+        It is redacted by default: paths, ids, emails, account names and agent
+        names are replaced, and evidence is pointers and marker codes only, with
+        no transcript text. Read it before posting. Do not add `--local`,
+        `--raw` or `--evidence`, and never paste a raw transcript or a
+        `journal.jsonl` line here.
+  - type: textarea
+    attributes:
+      label: What the tool said
+      description: The verdict, story or line you think is wrong, copied from the default-level output.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What actually happened
+      description: What really happened in that run, and how you know (in your own words, not transcript text).
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Bug report output
+      description: The output of `agent-postmortem run <run-id> --bug-report`, at the default level.
+      render: markdown
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Run shape
+      options:
+        - Workflow tool run
+        - Session with subagents
+        - claude -p (headless)
+        - Background subagents (run_in_background)
+        - claude --bg session
+        - Agent team
+        - Other
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Claude Code version
+      description: Output of `claude --version`.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: agent-postmortem version
+      description: Output of `agent-postmortem --version`.
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: Privacy
+      options:
+        - label: I pasted only default-level output (no `--local`, `--raw` or `--evidence`) and no transcript text.
+          required: true

agent_postmortem-0.3.4/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+## What this changes and why
+
+<!-- One or two sentences. Verdict first: what did not work before, what does now. -->
+
+## Checklist
+
+- [ ] Tests were written first (a failing test, then the code that makes it pass), and `uv run pytest` is green.
+- [ ] `uv run ruff check .` is clean.
+- [ ] Privacy check passes: `uv run pytest tests/test_privacy.py` (and, if this touches git history or ref names, `scripts/check-privacy.sh`).
+- [ ] `docs/DESIGN.md` was updated in this same PR if the code departs from what it currently says.
+- [ ] Any fixture added or changed under `tests/fixtures/` or `src/agent_postmortem/demo/` is fully synthetic (fake session id, fake paths, no real prompt text).

agent_postmortem-0.3.4/.github/workflows/ci.yml

@@ -0,0 +1,48 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ["3.11", "3.12", "3.13"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv sync --extra dev
+
+      - name: Lint
+        run: uv run ruff check .
+
+      - name: Test
+        run: uv run pytest
+
+      - name: Build
+        run: uv build
+
+      - name: Privacy check (tree and built artifacts)
+        run: scripts/check-privacy.sh --tree --artifacts dist/
+
+      - name: Validate Claude Code plugin and marketplace manifests
+        run: |
+          if command -v claude >/dev/null 2>&1; then
+            claude plugin validate --strict ./plugin
+            claude plugin validate --strict .
+          else
+            echo "claude CLI not present on this runner; skipping plugin validation."
+          fi

agent_postmortem-0.3.4/.github/workflows/release.yml

@@ -0,0 +1,83 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          python-version: "3.13"
+
+      - name: Install dependencies
+        run: uv sync --extra dev
+
+      - name: Test
+        run: uv run pytest
+
+      - name: Build
+        run: uv build
+
+      - name: Privacy check (built artifacts)
+        run: scripts/check-privacy.sh --tree --artifacts dist/
+
+      - name: Upload dist
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  github-release:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Download dist
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Release notes from CHANGELOG
+        run: |
+          version="${GITHUB_REF_NAME#v}"
+          awk -v v="$version" 'index($0, "## [" v "]") == 1 {f = 1; next} /^## \[/ {if (f) exit} f' CHANGELOG.md > notes.md
+          test -s notes.md
+
+      - name: Create the GitHub release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh release create "$GITHUB_REF_NAME" dist/* --verify-tag --title "$GITHUB_REF_NAME" --notes-file notes.md
+
+  publish:
+    # PyPI publishing waits for the trusted publisher (CONTRIBUTING.md). Until the repository
+    # variable PUBLISH_PYPI is set to 'true', a tag builds and makes the GitHub release, and
+    # this job is skipped rather than failed.
+    needs: build
+    if: vars.PUBLISH_PYPI == 'true'
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - name: Download dist
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

agent_postmortem-0.3.4/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.DS_Store
+docs/review-*.md.tmp
+
+.reviews/
+tests/privacy-denylist.local