New version: Peven v0.2.0

[JuliaRegistrator]

• Registering package: Peven
• Repository: https://github.com/jammy-eggs/Peven.jl
• Created by: @jammy-eggs
• Version: v0.2.0
• Commit: 2b36e824f34037571340e11eacff8a88bb87cab8
• Reviewed by: @jammy-eggs
• Reference: jammy-eggs/Peven.jl@2b36e82#commitcomment-182959453
• Release notes:

- Allow overlapping firings of the same `(transition, run_key)` when enough input tokens exist.
- Add vector executor outputs for transitions with exactly one output arc of weight `1`.
- Track `firing_id` and `attempt` across events and terminal trace records.
- Keep retry inputs reserved across attempts, while restoring the marking if fuse exhaustion blocks a retry.
- Clarify fuse semantics: it now counts launches, including retries, while letting in-flight work drain.

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines which are not met ❌

• This is a breaking change, but the release notes do not mention it. Please add a mention of the breaking change to the release notes (use the words "breaking" or "changelog").

  Example of adding release notes with breaking notice

  If you are using the comment bot @JuliaRegistrator, you can add release notes to this registration by re-triggering registration while specifying release notes:

  @JuliaRegistrator register
  
  Release notes:
  
  ## Breaking changes
  
  - Explanation of breaking change, ideally with upgrade tips
  - ...
  

  If you are using JuliaHub, trigger registration the same way you did the first time, but enter release notes that specify the breaking changes.

  Either way, you need to mention the words "breaking" or "changelog", even if it is just to say "there are no breaking changes", or "see the changelog".

2. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.