plane/testdata: pin to v1.3.1; verbatim work_item_created capture + README#14
Merged
Merged
Conversation
…h verbatim capture
work_item_created.json is now a verbatim webhook delivery from
plane.stern.ca (2026-05-24), exercising object-form state (PFB-24),
past-tense action (PFB-22), the description_*/description_json fields
the bridge ignores, and the full activity.actor object Plane ships
beyond the {id, display_name} subset the bridge models.
The other fixtures (work_item_updated/deleted, comment_*) keep their
synthetic UUIDs but are structurally normalized to match the real
v1.3.1 envelope. README documents which fixtures are verbatim vs
structurally-derived, the capture procedure (psql webhook_logs), and
which event types still need verbatim captures.
Real-Plane-container e2e (the durable fix for testdata drift) tracked
as PFB-28.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
work_item_created.jsonwith a verbatim Plane CE v1.3.1 webhook delivery captured from plane.stern.ca on 2026-05-24. Exercises object-form state (PFB-24), past-tense action verb (PFB-22),description/description_json/description_strippedfields the bridge ignores, and the fullactivity.actorobject (richer than{id, display_name}).work_item_updated/deleted,comment_*) to match the real v1.3.1 envelope while keeping their synthetic UUIDs. They are awaiting verbatim captures; until then the structural pinning catches the same class of bug as PFB-22/24/25.internal/plane/testdata/README.mddocumenting the pinned Plane version, fixture provenance (verbatim vs derived), and thepsql webhook_logs.request_bodycapture procedure for recapture across version bumps.work_item_createdtest assertions to match the verbatim capture's content (name, sequence_id, state.ID/Name, priority, actor.display_name).Why
PFB-22, PFB-24, and PFB-25 were all the same class of bug: hand-written synthetic testdata diverged from real Plane wire shape, CI was happy because both sides agreed on the synthetic shape, the bugs only surfaced when real Plane talked to the deployed bridge. This PR is the data half of the audit.
What's not in this PR (deliberate scope split)
Adding
makeplane/plane-backend:v1.3.1+ dependencies totest/e2e-dockerfor real-Plane round-trip coverage is tracked as PFB-28. It's the durable structural fix (CI fails the next time Plane changes a wire shape, not production), but it's substantial enough — ~5 extra services, seed flow, ~30s of warmup per matrix leg — to warrant its own PR.Test plan
make race— all packages greenmake lint— 0 issuesTestParse_Fixturesexercises all five fixtures end-to-end throughParse; updated assertions forwork_item_createdagainst verbatim capture🤖 Generated with Claude Code