plan_my_stuff 0.1.0 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 03731d4c3b552639604aa37465eb9f2246eb6077ec40144b218b4afa2aefdc01
-  data.tar.gz: 0277ebbdc6a0f783c90cb1bcf2d73c6dfd79447ad52f1df8d547d217cf80e1bf
+  metadata.gz: 3993e1306f27793791833787c546d81a42ed7bdf23d1420a658ec3877acf284b
+  data.tar.gz: 4593de2a00ea81ad22d0d951e1a97eb858a3d26071510c42e2e1aab9b99ae0f8
 SHA512:
-  metadata.gz: 3897dad435fd7b13780d3ac6ac3e25f9d15e49f58e8517c05ff6b28b78b7efd16216e4c9dbf0275afadf842821a9a006dd0e1c86b862e10927e197f190029f6a
-  data.tar.gz: 1a973153e39fc469580eac16dca37debb9780416b1cc7b50f9dffd440a6f64f4383fca30f24e72fdc02173c5875938c9181febd0226de8ecc8023c9907ac10db
+  metadata.gz: a9e140d9c6371186961903c5251143a63f4bedb3c238fc2d2b69e25ef3263824bdeacf767494c46473a5c7e9560c50b057e9b82136505b3615bcacdc742b3b6c
+  data.tar.gz: f73cb36b19ced07d713ae6e1aee02ab314292b3410d8b14d160e2156ceedd4a202f2fcecff7f67b61d25c93887bbc7e694f4415b89bab1203faa1e8bf7d7566c

data/CHANGELOG.md

@@ -0,0 +1,595 @@
+# Changelog
+
+## 1.0.0
+
+Official release.
+
+### Breaking
+
+- `MetadataParser.parse` no longer recognizes the legacy `<!-- pms-metadata:... -->` HTML-comment format.
+  Bodies written before 0.17.0 that have not been re-saved will now be returned as plain body text with
+  empty metadata. The deprecation warning emitted by 0.17.0+ has been removed along with the legacy
+  pattern.
+- Removed the deprecated `IssueMetadata#priority_list`, `#priority_list=`, `#priority_list?`,
+  `#priority_list_priority`, and `#priority_list_priority=` accessors, along with the legacy-write forwarding
+  that turned `metadata.priority_list = true` into `Priority List` / `Priority List Priority` issue-field writes
+  on `save!` / `update!` / `create!`. Use `Issue#priority_list?` / `#priority_list_priority` for reads and
+  `Issue#add_to_priority_list!(priority: N)` / `#remove_from_priority_list!` for writes (closes #57).
+- `CommentMetadata` no longer parses the legacy `{filename, url}` attachment shape into structured fields.
+  Entries must now carry the `{filename, owner, repo, sha, path}` shape; legacy entries that were never
+  re-saved are dropped as malformed. The `LEGACY_URL_REGEXES` / `LEGACY_ATTACHMENT_DEPRECATION_MESSAGE`
+  constants and the migrate-on-write deprecation warning have been removed.
+
+## 0.30.0
+
+### Added
+
+- The AWS deployment-completed webhook now fires a single `pipeline_deployment_completed.plan_my_stuff` batch event
+  after the per-item sweep, carrying every item that actually transitioned (payload: `:project_items`, `:issue_numbers`,
+  `:commit_sha`). Per-item `pipeline_completed.plan_my_stuff` events still fire. The batch event is skipped when nothing
+  transitioned, giving subscribers (release-notes mailer, Slack summary, changelog generator) one clean
+  "deployment finished" signal without debouncing N per-item events (closes #97).
+
+### Changed
+
+- `PlanMyStuff::Notifications.instrument` now accepts an `Array` resource. The payload key is the pluralized element
+  key (a batch of project items keys as `:project_items`, a batch of issues as `:issues`), so batch events carry a full
+  set under one key.
+- `PlanMyStuff::Pipeline.instrument` now accepts an `Array` of items for a batch event; the payload carries
+  `:issue_numbers` (the linked number of every item) in place of the single-item `:issue_number`.
+
+## 0.29.0
+
+### Changed
+
+- `Pipeline.complete_deployment!` now sets the linked issue's `Issue Status` field to `Fixed` on the auto-complete
+  success path (alongside moving the item to `Completed`). Gated on `config.issue_fields_enabled`, so completion still
+  succeeds when issue fields are disabled. The auto-complete-off early return is unchanged (closes #96).
+
+## 0.28.0
+
+### Added
+
+- `Issue.list_page_info(...)` returns a `PlanMyStuff::Issue::PageInfo` value object exposing `.issues`, `.page`,
+  `.per_page`, `.has_next?`, and `.has_prev?`. `Issue.list` now delegates to it; return type unchanged
+  (`Array<Issue>`). Closes #63.
+
+## 0.27.0
+
+### Added
+
+- `PlanMyStuff::Issue#mark_responded!(user)` - stamps `metadata.responded_at` on the first support-user engagement of
+  any kind. No-ops when the user is blank, not a support user, the issue isn't a PMS issue, or `responded_at` is
+  already set.
+
+### Changed
+
+- `Pipeline.take!` and the `issues.assigned` webhook now stamp `metadata.responded_at` on first support engagement
+  (was previously only set by the first support comment) (closes #60).
+
+## 0.26.0
+
+### Added
+
+- `PlanMyStuff::Issue#awaiting_reply?` - returns `true` when the issue's `Issue Status` field is `Waiting on Reply`.
+- `config.issue_field_names` (canonical field name => consumer field name) and `config.issue_field_values` (canonical
+  field name => `{ canonical value => consumer value }`) let a consuming org rename the native Issue Fields / option
+  labels the gem refers to internally. Translation runs via the new `PlanMyStuff::IssueFieldTranslation` module:
+  canonical => consumer on writes and filters (`set_issue_fields!`, `Issue.list` / `.count` `issue_fields:` +
+  `priority_list:`), consumer => canonical on reads (`Issue#issue_fields`), so internal comparisons like
+  `awaiting_reply?` / `priority_list?` keep working regardless of the org's naming. Unmapped names / values pass
+  through unchanged (identity fallback, mirroring `config.pipeline_statuses`).
+
+### Changed
+
+- The waiting/inactivity lifecycle methods now write the native `Issue Status` issue field alongside their existing
+  label/metadata changes (gated on `config.issue_fields_enabled`): `enter_waiting_on_user!` sets `Waiting on Reply`,
+  `clear_waiting_on_user!` sets `Open`, and `reopen_by_reply!` sets `Reopened`. No-op when `issue_fields_enabled` is
+  `false`.
+
+## 0.25.0
+
+### Added
+
+- `PlanMyStuff::Pipeline.clear_testing!(project_item, user: nil)` - reverses `request_testing!` by writing the
+  `:inactive` Testing field value. Fires `pipeline_testing_cleared.plan_my_stuff` with `field_name`, `value`,
+  `user` payload.
+- `PlanMyStuff::Issues::TestingsController` + `POST/DELETE /issues/:issue_id/testing` route (gated on
+  `config.pipeline_enabled`). Backs new "Request testing" / "Clear testing" buttons on the issue show view
+  (closes #52).
+
+## 0.24.0
+
+### Added
+
+- `PlanMyStuff::Issue.list` and `PlanMyStuff::Issue.count` now accept `issue_type:` (String / Symbol) and
+  `issue_fields:` (Hash keyed by display name) filter kwargs. `issue_type:` resolves symbol nicknames through
+  `ISSUE_TYPE_NICKNAMES` and `config.issue_types`; Arrays raise `ArgumentError` since GitHub's REST `type` param
+  and Search `type:` qualifier each accept only one value. `issue_fields:` accepts scalar (equality) or `Range`
+  (date / numeric bounds -- inclusive
+  `..` -> `>=`/`<=`, exclusive `...` -> `>=`/`<`, beginless / endless ranges drop the unbounded side) values and ANDs
+  multiple constraints together. Composes with the existing `priority_list:` filter into the same
+  `issue_field_values` (REST) / `field.<slug>:` (Search) qualifier list. Search-API calls flip
+  `advanced_search=true` when any field qualifier is present. `issue_fields:` raises
+  `IssueFieldsNotEnabledError` when `config.issue_fields_enabled` is `false` (closes #54).
+
+## 0.23.1
+
+### Added
+
+- `PlanMyStuff::UserResolver.from_github_login(login)` - inverse of `config.github_login_for`. Returns the
+  resolved user object whose configured GitHub login matches `login`, or `nil` when `login` is blank or
+  unmapped.
+
+### Changed
+
+- `Webhooks::GithubController` now forwards the actor through to `Pipeline.take!`'s `user:` kwarg from
+  `handle_issue_assigned` (using `assignee.login`) and `handle_draft_opened` (using the PR author). The
+  resolved user lands on the `pipeline_started.plan_my_stuff` notification payload.
+- `Issues::TakesController#create` now forwards `pms_current_user` to `Pipeline.take!`'s `user:` kwarg.
+
+## 0.23.0
+
+### Added
+
+- `PlanMyStuff::Pipeline.take!` and `PlanMyStuff::Pipeline.request_testing!` now accept a `user:` kwarg
+  that is forwarded onto the `pipeline_started.plan_my_stuff` / `pipeline_testing.plan_my_stuff`
+  `ActiveSupport::Notifications` payload. Defaults to `nil`, falling back to
+  `config.current_user` via `PlanMyStuff::Notifications.resolve_current_user`.
+
+## 0.22.0
+
+### Added
+
+- `Issue#add_to_priority_list!(priority:)` and `Issue#remove_from_priority_list!` - first-class setters that
+  mirror the `#priority_list?` / `#priority_list_priority` readers. Each writes both `Priority List` and
+  `Priority List Priority` in a single mutation so the two fields cannot drift apart (closes #80).
+
+### Changed
+
+- `IssueMetadata#priority_list` / `#priority_list_priority` deprecation message now points callers at the new
+  `Issue#add_to_priority_list!` / `#remove_from_priority_list!` pair instead of raw `set_issue_fields!`.
+
+## 0.21.1
+
+### Added
+
+- `config.eager_load_controllers_on_boot` (default `false`). When `true`, the engine eager-loads
+  `app/controllers/` in `after_initialize` so consuming apps with `eager_load = false` (dev mode) see
+  `PlanMyStuff::*Controller` constants without having to reference them first. Opt in if the host app
+  probes engine controllers via `defined?`, e.g. `defined?(PlanMyStuff::Issues::TakesController)` would
+  otherwise return `nil` until something triggered Zeitwerk autoload. Falls back to `Kernel#require` on
+  Zeitwerk < 2.6.2 (which lacks `eager_load_dir`).
+
+## 0.21.0
+
+### Breaking
+
+- `PMS::Attachment` no longer accepts/stores a single `url:` attribute. Construct with explicit
+  `filename:`, `owner:`, `repo:`, `sha:`, `path:` instead; `#url` is now a derived method that returns the
+  GitHub blob viewer URL (`https://github.com/{owner}/{repo}/blob/{sha}/{path}`) rather than the
+  `raw.githubusercontent.com` URL. `#to_h` emits the structured fields and no longer includes a `url` key.
+  Persisted comment metadata in the legacy `{filename, url}` shape is migrated on read and rewritten in the
+  new shape on next save (closes #70).
+
+### Added
+
+- Comment bodies now render a visible `<details><summary>attachments (N)</summary>` block listing each
+  attachment as a markdown link to its blob URL, between the `pms-metadata` block and the user body. The
+  parser strips this block on read so round-trips stay clean.
+
+## 0.20.0
+
+### Breaking
+
+- `priority_list` and `priority_list_priority` keys removed from `IssueMetadata` serialization. Existing issues
+  migrate to the GitHub Issue Field equivalents (`Priority List`, `Priority List Priority`) on their next save.
+
+### Added
+
+- `Issue#priority_list?` and `Issue#priority_list_priority` read the corresponding issue field values directly.
+- `Issue.priority_list(repo:, state:, labels:, page:, per_page:)` convenience method delegates to
+  `Issue.list(priority_list: true, ...)`.
+- `Issue.list` and `Issue.count` accept `priority_list:` for server-side filtering via the GitHub issue fields
+  API (passes `priority_list: false` raises `ArgumentError` -- the API has no negation qualifier).
+
+### Deprecated
+
+- `IssueMetadata#priority_list`, `#priority_list=`, `#priority_list?`, `#priority_list_priority`, and
+  `#priority_list_priority=` emit deprecation warnings on each read/write. Legacy writes forward to the issue
+  field on `Issue#save!` / `#update!` / `Issue.create!`. The accessors will be removed in 1.0.0.
+
+## 0.19.0
+
+### Added
+
+- Every controller action now yields its primary object to a block when subclassed, so consumers can do
+  `super do |obj| ... end` to wedge in audit-log / instrumentation without rewriting the action. Webhook
+  controllers yield `(payload, result)`. See [CONFIGURATION.md](CONFIGURATION.md).
+
+## 0.18.0
+
+### Breaking
+
+- `PMS::Issue#to_param` now returns `"Nickname-number"` (e.g. `"Rawr-1234"`) instead of the default ActiveModel id.
+  Single-issue URLs change from `/issues/1234?repo=rawr` to `/issues/Rawr-1234`. Consuming apps using
+  `youtrack_issue_path(@issue)` work natively; any hand-rolled URLs that passed `@issue.number` plus a `repo:`
+  query param must switch to `@issue` (or `@issue.to_param`). The mounted engine's controllers and views have
+  been updated to the new shape, as has the markdown link embedded in the GitHub issue body via
+  `Issue#user_link`.
+
+### Added
+
+- `config.repo_nicknames` (default `{}`) -- Symbol-keyed map from repo key to the human-readable label used as
+  the `Issue#to_param` prefix. Missing keys fall back to `key.to_s.titleize`, so `:rawr` -> `"Rawr"` is free;
+  only divergent ones (e.g. `safety: 'Compliance'`) need an entry.
+- `Configuration#repo_nickname_for(key)` accessor, `Repo#nickname`, and `Repo.from_nickname!` for the inverse
+  lookup used by `Issue.from_param`.
+- `Issue#to_param` and `Issue.from_param` -- the latter parses `"Nickname-1234"` back into `[Repo, Integer]`.
+- `Issue.find` first arg now accepts a nickname-id String (e.g. `"Rawr-1234"`) in addition to Integer / digit-
+  String + `repo:` kwarg. The nickname form ignores `repo:`.
+
+## 0.17.0
+
+### Added
+
+- `PlanMyStuff.deprecator` returns a gem-scoped `ActiveSupport::Deprecation` instance.
+  Consuming apps can silence, filter, or re-route PMS deprecation warnings independently
+  of Rails' own deprecator.
+
+### Changed
+
+- Issue, comment, and project-readme metadata is now stored in a visible `<details>` block
+  with a JSON code fence instead of a hidden HTML comment. GitHub renders the block in-page
+  so the metadata is inspectable without opening the body editor (closes #58).
+  `MetadataParser.parse` still accepts the legacy `<!-- pms-metadata:... -->` format and
+  emits a deprecation warning when it sees one; pre-0.17.0 bodies keep parsing and
+  re-serialize to the new format on their next write. Legacy detection will be removed
+  in 1.0.0.
+
+## 0.16.0
+
+### Added
+
+- `PlanMyStuff::Issue.count(repo:, state:, labels:)` returns the total count of matching issues via the
+  GitHub Search API in a single request, without paginating full issue payloads. Mirrors `Issue.list`
+  kwargs (minus `page`/`per_page`); returns an `Integer`. Excludes PRs server-side via the `is:issue`
+  qualifier.
+
+## 0.15.0
+
+### Breaking
+
+- `ActiveSupport::Notifications` events renamed to follow Rails' convention (event first, library
+  last). Subscribers matching the old `plan_my_stuff.*` prefix must switch to `*.plan_my_stuff`.
+
+  | Old                                          | New                                          |
+  |----------------------------------------------|----------------------------------------------|
+  | `plan_my_stuff.issue.created`                | `issue_created.plan_my_stuff`                |
+  | `plan_my_stuff.issue.updated`                | `issue_updated.plan_my_stuff`                |
+  | `plan_my_stuff.issue.closed`                 | `issue_closed.plan_my_stuff`                 |
+  | `plan_my_stuff.issue.reopened`               | `issue_reopened.plan_my_stuff`               |
+  | `plan_my_stuff.issue.archived`               | `issue_archived.plan_my_stuff`               |
+  | `plan_my_stuff.issue.closed_inactive`        | `issue_closed_inactive.plan_my_stuff`        |
+  | `plan_my_stuff.issue.reopened_by_reply`      | `issue_reopened_by_reply.plan_my_stuff`      |
+  | `plan_my_stuff.issue.marked_duplicate`       | `issue_marked_duplicate.plan_my_stuff`       |
+  | `plan_my_stuff.issue.viewers_added`          | `issue_viewers_added.plan_my_stuff`          |
+  | `plan_my_stuff.issue.viewers_removed`        | `issue_viewers_removed.plan_my_stuff`        |
+  | `plan_my_stuff.issue.approval_requested`     | `issue_approval_requested.plan_my_stuff`     |
+  | `plan_my_stuff.issue.approval_granted`       | `issue_approval_granted.plan_my_stuff`       |
+  | `plan_my_stuff.issue.approval_revoked`       | `issue_approval_revoked.plan_my_stuff`       |
+  | `plan_my_stuff.issue.approval_rejected`      | `issue_approval_rejected.plan_my_stuff`      |
+  | `plan_my_stuff.issue.rejection_revoked`      | `issue_rejection_revoked.plan_my_stuff`      |
+  | `plan_my_stuff.issue.all_approved`           | `issue_all_approved.plan_my_stuff`           |
+  | `plan_my_stuff.issue.approvals_invalidated`  | `issue_approvals_invalidated.plan_my_stuff`  |
+  | `plan_my_stuff.issue.reminder_due`           | `issue_reminder_due.plan_my_stuff`           |
+  | `plan_my_stuff.issue.link_reciprocal_failed` | `issue_link_reciprocal_failed.plan_my_stuff` |
+  | `plan_my_stuff.comment.created`              | `comment_created.plan_my_stuff`              |
+  | `plan_my_stuff.comment.updated`              | `comment_updated.plan_my_stuff`              |
+  | `plan_my_stuff.label.added`                  | `label_added.plan_my_stuff`                  |
+  | `plan_my_stuff.label.removed`                | `label_removed.plan_my_stuff`                |
+  | `plan_my_stuff.project_item.added`           | `project_item_added.plan_my_stuff`           |
+  | `plan_my_stuff.project_item.removed`         | `project_item_removed.plan_my_stuff`         |
+  | `plan_my_stuff.project_item.assigned`        | `project_item_assigned.plan_my_stuff`        |
+  | `plan_my_stuff.project_item.status_changed`  | `project_item_status_changed.plan_my_stuff`  |
+  | `plan_my_stuff.pipeline.<status>`            | `pipeline_<status>.plan_my_stuff`            |
+
+  Rationale: aligns with `sql.active_record`, `process_action.action_controller`, etc. and lets
+  subscribers match "everything from PMS" via the standard suffix-regex (`/\.plan_my_stuff$/`).
+
+## 0.14.0
+
+### Added
+
+- `Repo.resolve!` now treats a String matching a configured repo key (e.g. `"dummy"` when
+  `config.repos[:dummy]` is set) as that key, returning a Repo with `key:` populated.
+  Previously only Symbols hit the key lookup; strings always went through `"Org/Repo"`
+  parsing and raised on names without a slash. This prevents the need to call `to_sym` from the consuming app
+
+## 0.13.0
+
+### Changed
+
+- Internal: gem now autoloads `lib/plan_my_stuff/**` via Zeitwerk
+  (already shipped by railties - no new dep). All `require_relative`
+  boilerplate in the gem's lib tree is gone. The gem entry retains two
+  explicit `require_relative`s for files that fall outside the autoload
+  model: `errors.rb` (defines several sibling error classes) and
+  `engine.rb` (must register with Rails at load time).
+
+## 0.12.0
+
+### Added
+
+- `PlanMyStuff::IssueField` for org-level GitHub Issue Field definitions (public preview).
+  Exposes `.list`, `.find` (case-insensitive), and `#option_id_for!` for resolving
+  single-select option names.
+- `PlanMyStuff::Issue#issue_fields` returns a hash-like `IssueFieldValueSet` view of the
+  field values on an issue. Values are coerced to native types (`Date` for date fields,
+  `Float` for numbers, the option name `String` for single-selects).
+- `PlanMyStuff::Issue#set_issue_fields!(updates)` writes one or more field values in a
+  single GraphQL mutation; passing `nil` as a value clears the field.
+- `issue_fields:` kwarg on `Issue.create!`, `Issue.update!`, `Issue#save!`, and
+  `Issue#update!` so callers can set field values inline with create/update instead of
+  following up with an explicit `set_issue_fields!` call.
+- `Configuration#issue_fields_enabled` (default `true`, opt-out). Set to `false` if your
+  org has not been admitted to the Issue Fields preview - with the flag off,
+  `Issue#issue_fields` returns an empty set and the write paths raise
+  `IssueFieldsNotEnabledError` instead of letting a raw GraphQL error surface.
+
+## 0.11.0
+
+### Added
+
+- `PlanMyStuff::Attachment` value object (`filename`, `url`) and
+  `CommentMetadata#attachments`. PMS now owns attachment storage:
+  `Comment.create!` accepts an `attachments:` kwarg of uploaded-file
+  objects responding to `#path` and `#original_filename` (e.g.
+  Rails `ActionDispatch::Http::UploadedFile`), `String`/`Pathname`
+  paths to local files, or pre-built `PlanMyStuff::Attachment`
+  instances. Each file is committed to the shared attachment repo
+  (`config.attachment_repo`, default `'pms-attachments'`, under
+  `config.organization`) on `config.main_branch` at
+  `<repo_key>/issue-<N>/<uuid>.<ext>`; the resulting SHA-pinned
+  `raw.githubusercontent.com` permalink is stored in metadata as a
+  `PlanMyStuff::Attachment(filename:, url:)`. The attachment repo
+  must exist; the uploader does not create it. Malformed metadata
+  entries are silently dropped on parse, matching existing `links`
+  / `approvals` behavior on `IssueMetadata`.
+- `config.attachment_repo` (default `'pms-attachments'`) names the
+  bare repo under `config.organization` that stores uploaded
+  attachment binaries.
+- `PlanMyStuff::AttachmentUploader.upload_all!(repo:,
+  issue_number:, files:)` is the underlying uploader; called
+  internally by `Comment.create!` but also usable directly by apps
+  that want to upload before constructing a comment. Pre-built
+  `Attachment` instances pass through without re-uploading.
+- `Issue.create!` accepts an `attachments:` kwarg, forwarded to the
+  body-comment `Comment.create!` call so attachments posted with a
+  new issue are recorded on (and uploaded for) the body comment.
+- `PlanMyStuff::Attachment#download_to(path = nil)` fetches the file
+  via the GitHub Contents API (so it works on private repos) and
+  writes the bytes to disk. Defaults `path` to
+  `File.join(Dir.tmpdir, filename)` and returns the path written to.
+
+### Documented
+
+- `designs/g9/` documents the design pivot from inline-base64 (body
+  size capped) through sibling-repo (rejected) to the chosen
+  side-branch approach.
+
+## 0.10.5
+
+### Added
+
+- `config.parent_controller` (default `'::ApplicationController'`) lets consuming apps that don't use the
+  `ApplicationController` name (e.g. `ActionController::Base`, `RawrApplicationController`) tell the engine
+  what to inherit from. The `plan_my_stuff:verify` rake task now reports whether the configured class
+  resolves.
+
+### Fixed
+
+- Example config option showed `url_options = Rails.application.config.action_mailer.default_url_options`. Now it shows
+`url_options = Rails.application.routes.default_url_options`
+
+## 0.10.4
+
+### Changed
+
+- Internal: unit specs now use VCR cassettes against `BrandsInsurance/ubiquitous-adventure` instead of
+  `instance_double(Octokit::Client)`. No effect on consuming apps.
+
+### Removed
+
+- ETag caching on `Issue.list`. The cache key included `state`, `labels`, `page`, and `per_page`,
+  so an etag stored under one combo never matched a request with different params - the cache wrote
+  on every call and effectively never hit. `Issue.list` now always issues a fresh GitHub request.
+  `Comment.list` keeps ETag caching (param surface is just `issue` + `pms_only`).
+  `PlanMyStuff::Cache.read_list` / `write_list` remain available for `Comment.list`.
+
+## 0.10.3
+
+### Added
+
+- `BaseProjectItem#assignees` returns the GitHub logins of users assigned to the underlying Issue,
+  PullRequest, or DraftIssue. Populated from the `FIND_PROJECT` GraphQL response (the query was extended
+  with `assignees(first: 10)` on each content fragment).
+
+## 0.10.2
+
+### Changed
+
+- Nothing, just a version bump
+
+## 0.10.1
+
+### Changed
+
+- Nothing, just a version bump
+
+## 0.10.0
+
+### Changed
+
+- `Issue` slimmed from 1791 to 911 lines by extracting feature clusters into per-feature modules under a sibling
+  `PlanMyStuff::IssueExtractions::*` namespace, included into `Issue`. Public API unchanged (`issue.approve!`,
+  `issue.add_related!`, `issue.enter_waiting_on_user!`, `issue.add_viewers!`, etc. still resolve to the same methods).
+  - `PlanMyStuff::IssueExtractions::Approvals` - `lib/plan_my_stuff/issue_extractions/approvals.rb`
+  - `PlanMyStuff::IssueExtractions::Links` - `lib/plan_my_stuff/issue_extractions/links.rb`
+  - `PlanMyStuff::IssueExtractions::Waiting` - `lib/plan_my_stuff/issue_extractions/waiting.rb`
+  - `PlanMyStuff::IssueExtractions::Viewers` - `lib/plan_my_stuff/issue_extractions/viewers.rb`
+- `BaseProject` slimmed from 661 to 504 lines by extracting GraphQL hydration helpers into
+  `PlanMyStuff::BaseProjectExtractions::GraphqlHydration` (`lib/plan_my_stuff/base_project_extractions/graphql_hydration.rb`),
+  included into `BaseProject`'s singleton class. `BaseProject.find` / `BaseProject.list` remain public entry points.
+- Specs for `Issue` features now live alongside the modules at `spec/plan_my_stuff/issue_extractions/<feature>_spec.rb`.
+
+## 0.9.0
+
+### Breaking
+
+- `config.should_send_request` and `config.job_classes` accessors — declared but never wired up. The request gateway that would honor them is deferred (see `requirements/09_request_gateway.md` and `designs/init/gem_mvp_deferred_notes.md`); they will return when the gateway lands
+
+### Added
+
+- `CONFIGURATION.md` is now available bundled with the gem
+
+### Changed
+
+- `config.repos` is now assignable as a whole hash (`config.repos = { atlas: 'Org/Atlas', autofill: 'Org/atlas-autofill-moz' }`) in addition to the existing `config.repos[:key] = '...'` form
+- `Issue.create!` / `Issue.update!` `issue_type:` kwarg now accepts the Symbol nicknames (`'bug'`, `'feature'`, `'it_issue'`, `'other'`, `'performance'`, `'question'`, `'task'`) as Strings too, resolving them to the same canonical name
+
+## 0.8.0
+
+### Breaking
+
+- Issue show "Take" button is now hidden when the issue already has assignees, and `Issues::TakesController#create` rejects the request with a flash error naming the existing assignee. Best-effort race guard for two users clicking Take simultaneously — without it, GitHub silently piles the second user on as a co-assignee.
+  - Guard lives in the controller, not `Pipeline.take!` itself, because webhook paths (`handle_issue_assigned`, `handle_projects_v2_item`, `handle_draft_opened`, `handle_converted_to_draft`) legitimately call `take!` on already-assigned issues
+- `Issue#add_viewers` / `Issue#remove_viewers` renamed to `Issue#add_viewers!` / `Issue#remove_viewers!` for consistency with other mutating instance methods (`approve!`, `close!`, etc.)
+- `Approval#status` extended to a 3-state model (`pending`, `approved`, `rejected`); `Approval` gains a `rejected_at` attribute serialized in `to_h` and the metadata blob. Existing approvals deserialize unchanged (`rejected_at` defaults to `nil`)
+- `Issue#fully_approved?` now requires every approver to be `approved` — a single rejection blocks the gate until revoked. Previously equivalent to `pending_approvals.empty?`, which silently treated rejections as "done"
+- `Issue#revoke_approval!` accepts either an `approved` or `rejected` source state (previously only `approved`); raises `ValidationError` when the target is still `pending`. Authorization error message updated to "another user's response"
+
+### Added
+
+- `CONFIGURATION.md` documents every `PlanMyStuff::Configuration` option grouped by concern; `README.md` Configuration section trimmed to the two required options plus a link
+- Install generator's initializer template now includes the four pipeline options previously missing from it: `pipeline_testing_field_name`, `pipeline_testing_values`, `pipeline_completion_purge_enabled`, `pipeline_completion_ttl_hours`
+- Project show "Remove from project" button (and `DELETE /projects/:project_id/items/:id` route on `ProjectItemsController`) lets the user remove an item from a project board without bouncing out to GitHub. Calls `ProjectItem#destroy!` which fires `plan_my_stuff.project_item.removed`
+- Issue show "Release" button (and `DELETE /issues/:issue_id/take` route on `Issues::TakesController`) lets a dev who took an issue undo their assignment from the same view, without bouncing out to GitHub or the project board. When the current user is the sole assignee the issue's GitHub assignees are cleared and the project item is removed from the pipeline (`project_item.destroy!`); when other assignees remain the current user is unassigned via `project_item.assign!(remaining)` and the item stays on the project
+- `config.import_access_token` classic PAT (requires `repo` scope) used exclusively for the Issues Import API (`golden-comet-preview`); fine-grained tokens are not supported by that endpoint. Optional — defaults to `nil`
+- `Issue.import!(payloads)` POSTs an `Array<Hash>` (one POST per payload) to GitHub's "Import Issues" preview endpoint and returns one status hash per input. Each payload must include `:repo` plus the GitHub-shaped `:issue` / `:comments` keys; payloads are passed through unchanged otherwise
+- `Issue.check_import!(import_id, repo:)` polls a previously-submitted import for its status
+- `Issue#created_at` / `Comment#created_at` attributes hydrated from GitHub's `created_at` field
+- `Issue#issue_type` reader hydrated from GitHub's native `type.name`. `Issue.create!` and `Issue.update!` accept an `issue_type:` kwarg as a String (passed through), Symbol shortcut (`:bug`, `:feature`, `:it_issue`, `:other`, `:performance`, `:question`, `:task`), or `nil`. On `update!`, omitting the kwarg leaves the type untouched; passing `nil` clears it
+- `config.issue_types` Hash{String => String} maps canonical type names to org-specific display names so consuming apps can rename without touching call sites (e.g. `{ 'Feature' => 'Enhancement' }`); missing keys pass through unchanged
+- `config.controller_rescue` Proc invoked from every user-facing controller `rescue` block (after the gem logs the error and stack trace) so consuming apps can forward swallowed errors to their monitoring service
+- `Issue#reject!(user:)` symmetric with `approve!`; accepts either `pending` or `approved` source state and raises `ValidationError` when already rejected. Fires `plan_my_stuff.issue.approval_rejected` and, when the flip drops the issue out of `fully_approved?`, `approvals_invalidated(trigger: :rejected)`
+- `Issue#approve!` now accepts either `pending` or `rejected` source state; raises `ValidationError` only on `approved -> approved`. Clears `rejected_at` on the rejected -> approved transition
+- `Issue#rejected_approvals` reader returns the subset of approvers with `status == 'rejected'`
+- New events: `plan_my_stuff.issue.approval_rejected` and `plan_my_stuff.issue.rejection_revoked` (the latter fires when revoking a rejection back to pending)
+- Approvals partial renders a `Reject` button alongside `Approve` for pending approvers, a `rejected at <ts>` row, a parenthetical rejected count in the header, and a `Revoke` button for either non-pending state
+
+## 0.7.0
+
+### Added
+
+- `Issue#user_link` returns the per-issue URL in the consuming app, computed from `config.issues_url_prefix` + issue number
+
+### Changed
+
+- GitHub issues created/updated by PMS now render a markdown link `[Org/Repo#number](user_link)` as the visible body (previously empty); skipped when `issues_url_prefix` is unset
+
+## 0.6.0
+
+### Breaking
+
+- `Pipeline.submit!` removed; consuming apps that called it directly should switch to `ProjectItem.create!` + `Pipeline.take!`
+- `Pipeline::Status::SUBMITTED` and `Pipeline::Status::TESTING` constants removed; `Status::ALL` no longer includes them
+- `Pipeline.request_testing!` no longer moves the `Status` field — it now writes to a separate `Testing` single-select custom field on the pipeline project. The pipeline project must have a `Testing` field with `Testing` / `Not testing` options
+- Active pipeline status set is now `Started -> In Review -> Ready for Release -> Release in Progress -> Completed`
+
+### Added
+
+- `Pipeline::Testing` module (`FIELD_NAME`, `VALUES`)
+- `Pipeline::CompletedSweep` removes items from `Completed` after the configured TTL; driven by `RemindersSweepJob`
+- `BaseProjectItem#update_single_select_field!` instance method
+- `BaseProjectItem#updated_at` populated from GitHub's `updatedAt`
+- `Issue#assignees` public reader
+- `Pipeline.release_cycle_locked?` helper
+- New config: `pipeline_testing_field_name`, `pipeline_testing_values`, `pipeline_completion_purge_enabled` (default `true`), `pipeline_completion_ttl_hours` (default `24`)
+
+### Changed
+
+- Assigning a dev to an issue now creates the project item and lands it at `Started` (was `Submitted`)
+- Opening a PR as a draft adds the linked issue to the pipeline at `Started` and assigns the PR author when the issue has no assignees; already-pipelined items are not moved
+- The assignment webhook no longer calls `assign!` on the project item — GitHub already records the assignment, and `assign!` could clobber co-assignees
+
+### Removed
+
+- `Pipeline.submit!` (see Breaking)
+- `Pipeline::Status::SUBMITTED`, `Pipeline::Status::TESTING` (see Breaking)
+
+### Fixed
+
+- Closed issues no longer alter the pipeline on assign/unassign webhook events
+- Items at `Ready for Release`, `Release in Progress`, or `Completed` are no longer removed when an unassign webhook fires
+- Pending-approvals guard runs before `ProjectItem.create!` in the assignment flow so the webhook no longer leaves orphan items when `Pipeline.take!`'s approval guard would otherwise raise
+
+### Documented
+
+- `designs/pipeline_cleanup/plan.md` — full design + bug-to-fix mapping
+- `requirements/08_release_pipeline.md` updated to reflect the new flow
+- `requirements/tasks.md` — T-PC-001 added under Phase 14
+
+## 0.5.1
+
+### Fixed
+
+- AWS webhook rejected SNS `SubscriptionConfirmation` and `UnsubscribeConfirmation` messages with 401; now signature-verified, logged, and acked with 200
+
+## 0.5.0
+
+### Added
+
+- `post_install_message` in gemspec listing available rake tasks and generators
+- `rake plan_my_stuff:install` and `rake plan_my_stuff:views` aliases for the Rails generators
+
+### Fixed
+
+- `TestingProjectItem.create!` left new items with a blank Test Status; now defaults to `Todo`
+- `TestingProjectItem.create!` left new items with no Pass Mode; now defaults to `all`
+
+## 0.4.0
+
+- Full feature set release before PR
+
+## 0.3.0
+
+### Added
+
+- Add `new`/`create`/`edit`/`update` routes for Projects
+
+## 0.2.0
+
+### Added
+
+- Validate `config.custom_fields` on `create!`/`update!` actions
+
+### Changes
+
+- CodeRabbit improvements
+
+## 0.1.2
+
+### Fixed
+
+- Issues' links were looking for the issue in the default repo with the same number
+
+## 0.1.1
+
+### Fixed
+
+- Wrong changelog included in publish
+
+## 0.1.0
+
+- Initial Setup