feat: adds reusable actions by baywet · Pull Request #296 · OAI/Overlay-Specification

baywet · 2026-02-18T18:36:24Z

This pull request adds action templates.

fixes #33
fixes #136
fixes #270

closes #238

This is another attempt to solve a scale limitation in the current specification. Action templates are better than the previous parameters proposal because:

They do not introduce a matrix projection, people may use the template multiple times.
They do not require "declaring" which environment variables to read in advance.
They limit the string literal replacement to the templates, which does not impact how actions currently work.
The template reference mechanism works like OpenAPI references.
The template resolution mechanism can be isolated as a pre-processing step, and the resolved actions can then be fed to the existing code processing actions.
It introduces a string literal replacement syntax which can be expanded upon for other sources or used at other places in the future.

The pull request is incomplete as it is, it's a draft, I want to collect feedback on the approach before making any further investments.

ralfhandl · 2026-02-18T19:04:23Z

I like the general direction.

baywet · 2026-02-24T16:35:26Z

Feedback from the meeting from both @lornajane and @ralfhandl :

add a peer block to parameters for the environment variables, this allows to set defaults and "declare" which variables are used. But this declaration is optional.
add a peer "actions" in the components, that's defined as everything except for the target. So people can specify the target on reference. Reusable actions may use action templates in turns.

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

ralfhandl

Mostly wording and capitalization

versions/1.2.0-dev.md

Co-authored-by: Ralf Handl <ralf.handl@gmail.com>

versions/1.2.0-dev.md

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

…rlay-Specification into feat/action-templates Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet · 2026-03-03T13:46:27Z

@ralfhandl @lornajane I pushed another update a couple of minutes ago. I wasn't happy about the whole reusable actions vs action templates kind of thing. After chatting with @mikekistler internally I realized we could simply define a an action template reference object as "you can override anything from the resolved template in the reference" like JSON schema does to some extent. And keep things extra simple.

Let me know what you think!

…ferences Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet · 2026-03-31T19:38:03Z

Update, I've had some more time to spend on this. I believe I've addressed all the feedback and got this to a place much closer to a finalized version/ready for a formal vote.
I suggest we go through another round of review/update before we move to a formal vote.

Noteable changes:

updated the terminology to "reusable actions"
moved to a single concept (no more template vs component actions divide)
stuck with local references only for now, we can always open this up in a subsequent release, as per other authors' feedback
added the schema changes
added the schema tests
triple checked the examples
updated additional wording based on @mikekistler excellent suggestions

Let me know if you have any additional comments or questions.

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

…r versions of the specification Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet · 2026-03-31T20:01:33Z

Note: I've just added a lot of tests to improve the coverage. This is going to temporarily make the review more difficult. I've extracted the tests for the current schema (not the changes in this pull request) in #317 in the hope that we merge that one first, making the diff here smaller.

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet · 2026-04-01T14:15:41Z

versions/1.2.0-dev.md

+| Field Name | Type | Description |
+| ---- | :----: | ---- |
+| <a name="reusable-action-parameter-name"></a>name | `string` | **REQUIRED** The name of the parameter, MUST match the key for the string literal replacement expression. |
+| <a name="reusable-action-parameter-default>default | Any | A default value for the parameter to use when no value is provided by the reference. Optional. |


collecting notes from my implementation work: it might be better to restrain this to string instead of any json value. Having any json value poses a couple of issues:

string interpolation is not "just string interpolation" anymore (you need to consider the object tree), and that brings a higher chance of ending up with an invalid resolved value in the end

environment variables would never be able to support that.

So both in the name of simplicity and uniformity I suggest we change this, and the parameter value field to string types instead of json values.

baywet · 2026-04-02T14:53:28Z

versions/1.2.0-dev.md

+
+| Field Name | Type | Description |
+| ---- | :----: | ---- |
+| <a name="reusable-action-reference-ref"></a>$ref | `string` | **REQUIRED** A [same-document](https://www.rfc-editor.org/rfc/rfc3986.html#section-4.4) (or fragment-only) relative URI reference, per RFC3986 §4.4, and that the fragment syntax is JSON Pointer, with the pointer prefix restricted to `/components/actions/`. |


@handrews I think that also effectively means that any reusable action (entries under components/actions) MUST have / and ~ encoded according to the JSON pointer semantics. I think we should call this out explicitly in the components section, what do you think?

baywet · 2026-04-02T17:51:36Z

versions/1.2.0-dev.md

+| ---- | :----: | ---- |
+| <a name="reusable-action-parameters"></a>parameters | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of parameters to be used during  string literal replacement. Optional. |
+| <a name="reusable-action-environment-variables"></a>environmentVariables | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of environment variables to be used during  string literal replacement. Optional. |
+| <a name="reusable-action-action-fields"></a>Any field defined in the [action object](#action-object) | mixed | The [string literal replacement syntax](#string-literal-replacement-syntax) MAY be used for any of the fields, and the replacements MUST be evaluated as the reusable action reference is being resolved. |


Here we need to restrict the interpolation syntax to apply only to string fields (Target, Copy, Description), because for others (Remove) it breaks the JSON schema validation of the document).

And for Update, it poses a lot of additional questions (env vs params, what happens if the resulting JSON doesn't match the structure we expect (requirement for this field), etc...

baywet · 2026-04-02T18:58:38Z

Finalized the implementation of the current version of the spec over here BinkyLabs/openapi-overlays-dotnet#276

(some LLMs were hurt in the process)

ralfhandl

Only reviewed the examples.

tests/v1.2-dev/fail/action-parameters-invalid.yaml

schemas/v1.2-dev/schema.yaml

tests/v1.2-dev/fail/action-with-environment-variables-invalid.yaml

tests/v1.2-dev/fail/reusable-action-parameter-values-not-allowed.yaml

tests/v1.2-dev/pass/reusable-action-environment-variables.yaml

tests/v1.2-dev/pass/reusable-action-reference-without-target.yaml

Co-authored-by: Ralf Handl <ralf.handl@gmail.com>

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

mikekistler

I think this is very close now. I left a few more comments about possible improvements.

versions/1.2.0-dev.md

mikekistler · 2026-04-06T15:09:26Z

versions/1.2.0-dev.md

+| Field Name | Type | Description |
+| ---- | :----: | ---- |
+| <a name="reusable-action-parameters"></a>parameters | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of parameters to be used during  string literal replacement. Optional. |
+| <a name="reusable-action-environment-variables"></a>environmentVariables | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of environment variables to be used during  string literal replacement. Optional. |


I wonder if environmentVariables should be defined under components rather than in each Reusable Action Object. Unlike parameters, the names of these variables are fixed in the enviroment. I suppose different actions could use different default values for an environment variable, but that seem very unlikely and a poor practice.

I briefly considered that approach, and quickly realized that it's probably not the one that's going to get consensus:

we've already tried root level "variables" in feat: adds a parameter object for the action object #238

multiple levels references resolutions have an implementation cost and add to the cognitive load, the feedback has been overwhelmingly in favour of "keep things as simple as possible"

there are benefits from having a consistent approach between parameters and environment variables. In my implementation, the same code handles both. The only difference being where the values come from. I suspect most implementers will appreciate that.

not doing this now does not prevent us from adding support for "root level parameter definitions" in a future minor version. (a little similar to external references support) and we could base this on popular demand.

Let me know if you have any additional comments or questions.

mikekistler · 2026-04-06T15:11:57Z

versions/1.2.0-dev.md


+#### Reusable Action Object
+
+This object is a component that can be reused by Reusable Action Reference Objects, it represents one or more changes to be applied to the target document at the locations defined by the target JSONPath expression and reused in one of more action references.


I think this needs a little more wordsmithing. Right now it feels like two sentences joined by a comma rather than a period. But that is not quite right either, since it is the composition of a Reusable Action Object and Action Reference that "represents one or more changes ..."

coerced the LLM into coming up with something more intelligible in c04856d, let me know what you think.

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

ralfhandl

Only minor suggestions

ralfhandl · 2026-04-06T19:09:36Z

tests/v1.2-dev/fail/action-with-environment-variables-invalid.yaml

@@ -0,0 +1,10 @@
+overlay: 1.2.0
+info:
+  title: Reusable action environment variables must be an array


Non-reusable action objects can't have environment variables

ralfhandl · 2026-04-06T19:10:10Z

tests/v1.2-dev/fail/action-with-environment-variables-invalid.yaml

+actions:
+  - target: '$.info'
+    environmentVariables:
+      name: stageName


Suggested change

name: stageName

- name: stageName

Make the forbidden construct syntactically valid

ralfhandl · 2026-04-06T19:13:46Z

tests/v1.2-dev/fail/action-with-parameter-invalid.yaml

This seems to be a duplicate of tests/v1.2-dev/fail/action-parameters-invalid.yaml.

ralfhandl · 2026-04-06T19:17:49Z

versions/1.2.0-dev.md

+
+| Field Name | Type | Description |
+| ---- | :----: | ---- |
+| <a name="reusable-action-parameters"></a>parameters | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of parameters to be used during  string literal replacement. Optional. |


Suggested change

| <a name="reusable-action-parameters"></a>parameters | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of parameters to be used during string literal replacement. Optional. |

| <a name="reusable-action-parameters"></a>parameters | [[Reusable Action Parameter Object](#reusable-action-parameter-object)] | A list of parameters to be used during string literal replacement. Optional. |

ralfhandl · 2026-04-06T19:19:20Z

versions/1.2.0-dev.md

+| Field Name | Type | Description |
+| ---- | :----: | ---- |
+| <a name="reusable-action-parameters"></a>parameters | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of parameters to be used during  string literal replacement. Optional. |
+| <a name="reusable-action-environment-variables"></a>environmentVariables | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of environment variables to be used during  string literal replacement. Optional. |


Suggested change

| <a name="reusable-action-environment-variables"></a>environmentVariables | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of environment variables to be used during string literal replacement. Optional. |

| <a name="reusable-action-environment-variables"></a>environmentVariables | [[Reusable Action Parameter Object](#reusable-action-parameter-object)] | A list of environment variables to be used during string literal replacement. Optional. |

ralfhandl · 2026-04-06T19:20:02Z

versions/1.2.0-dev.md

+| ---- | :----: | ---- |
+| <a name="reusable-action-parameters"></a>parameters | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of parameters to be used during  string literal replacement. Optional. |
+| <a name="reusable-action-environment-variables"></a>environmentVariables | [[Reusable action parameter object](#reusable-action-parameter-object)] | A list of environment variables to be used during  string literal replacement. Optional. |
+| <a name="reusable-action-action-fields"></a>Any field defined in the [action object](#action-object) | mixed | The [string literal replacement syntax](#string-literal-replacement-syntax) MAY be used for any of the fields, and the replacements MUST be evaluated as the reusable action reference is being resolved. |


Suggested change

| <a name="reusable-action-action-fields"></a>Any field defined in the [action object](#action-object) | mixed | The [string literal replacement syntax](#string-literal-replacement-syntax) MAY be used for any of the fields, and the replacements MUST be evaluated as the reusable action reference is being resolved. |

| <a name="reusable-action-action-fields"></a>Any field defined in the [Action Object](#action-object) | mixed | The [string literal replacement syntax](#string-literal-replacement-syntax) MAY be used for any of the fields, and the replacements MUST be evaluated as the reusable action reference is being resolved. |

ralfhandl · 2026-04-06T19:23:44Z

versions/1.2.0-dev.md

+
+A reusable action is similar to an action but differs in important ways:
+
+1. It may omit any action field, in particular the `target` field, as these may be supplied by the Reusable Action Reference Object.


Suggested change

1. It may omit any action field, in particular the `target` field, as these may be supplied by the Reusable Action Reference Object.

1. It may omit any action field, in particular the `target` field, as these may be supplied by the [Reusable Action Reference Object](#reusable-action-reference-object).

ralfhandl · 2026-04-06T19:24:24Z

versions/1.2.0-dev.md

+A reusable action is similar to an action but differs in important ways:
+
+1. It may omit any action field, in particular the `target` field, as these may be supplied by the Reusable Action Reference Object.
+1. Any action field in the Reusable Action may employ string interpolation using variables specified in the `parameters` or `environmentVariables` fields.


Suggested change

1. Any action field in the Reusable Action may employ string interpolation using variables specified in the `parameters` or `environmentVariables` fields.

1. Any action field in the Reusable Action Object may employ string interpolation using variables specified in the `parameters` or `environmentVariables` fields.

ralfhandl · 2026-04-06T19:25:01Z

versions/1.2.0-dev.md

+
+1. It may omit any action field, in particular the `target` field, as these may be supplied by the Reusable Action Reference Object.
+1. Any action field in the Reusable Action may employ string interpolation using variables specified in the `parameters` or `environmentVariables` fields.
+1. A Reusable Action MUST be referenced by a Reusable Action Reference Object to have any effect on the OpenAPI description.


Suggested change

1. A Reusable Action MUST be referenced by a Reusable Action Reference Object to have any effect on the OpenAPI description.

1. A Reusable Action Object has to be referenced by a Reusable Action Reference Object to have any effect on the OpenAPI description.

Don't use MUST as this might be misunderstood as "a Reusable Action Object MUST be referenced at least once".

ralfhandl · 2026-04-06T19:28:49Z

versions/1.2.0-dev.md

+| ---- | :----: | ---- |
+| <a name="reusable-action-reference-ref"></a>$ref | `string` | **REQUIRED** A [same-document](https://www.rfc-editor.org/rfc/rfc3986.html#section-4.4) (or fragment-only) relative URI reference, per RFC3986 §4.4, and that the fragment syntax is JSON Pointer, with the pointer prefix restricted to `/components/actions/`. |
+| <a name="reusable-action-reference-parameter-values></a>parameterValues | `Map(string, Any)` | A set of values to use for the reusable action parameters, the key MUST match the parameter name. Optional. |
+| <a name="reusable-action-reference-action-fields"></a>Any field defined in the [action object](#action-object) | mixed | Any field defined in the [Action Object](#action-object) to be used as an override to the value resolved in the reusable action. The [string literal replacement syntax](#string-literal-replacement-syntax) MAY NOT be used for any of the fields. Optional. |


Suggested change

| <a name="reusable-action-reference-action-fields"></a>Any field defined in the [action object](#action-object) | mixed | Any field defined in the [Action Object](#action-object) to be used as an override to the value resolved in the reusable action. The [string literal replacement syntax](#string-literal-replacement-syntax) MAY NOT be used for any of the fields. Optional. |

| <a name="reusable-action-reference-action-fields"></a>Any field defined in the [Action Object](#action-object) | mixed | Any field defined in the [Action Object](#action-object) to be used as an override to the value resolved in the reusable action. The [string literal replacement syntax](#string-literal-replacement-syntax) MAY NOT be used for any of the fields. Optional. |

baywet added this to the Release 1.2 milestone Feb 18, 2026

baywet requested review from handrews, karenetheridge, lornajane, mikekistler, mkistler and ralfhandl and removed request for mkistler February 18, 2026 18:37

baywet added 6 commits February 25, 2026 09:53

feat: adds string literal replacement syntax

38198c9

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

feat: adds high level definitions for templates and templates parameters

74f3a40

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

feat: adds the action template reference object

2f2fbcc

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

docs: adds an example for the action templates

77d9e4f

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

feat: adds reusable actions to the components

5633f57

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

feat: adds environment variables template

06a21c9

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet force-pushed the feat/action-templates branch from e709bde to 06a21c9 Compare February 25, 2026 15:19

baywet changed the title ~~feat: adds action templates~~ feat: adds action templates and reusable actions Feb 25, 2026

ralfhandl reviewed Feb 25, 2026

View reviewed changes

baywet and others added 3 commits February 25, 2026 11:37

chore: capitalization fixes

553fca8

Co-authored-by: Ralf Handl <ralf.handl@gmail.com>

chore: typo fixes

9329227

Co-authored-by: Ralf Handl <ralf.handl@gmail.com>

fix: case sensitive environment variable

d01be1e

Co-authored-by: Ralf Handl <ralf.handl@gmail.com>

handrews suggested changes Feb 25, 2026

View reviewed changes

versions/1.2.0-dev.md Outdated Show resolved Hide resolved

baywet requested a review from ralfhandl February 25, 2026 18:56

baywet added 3 commits March 3, 2026 08:33

feat: merges reusable actions

0b71e07

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

Merge branch 'feat/action-templates' of https://github.com/baywet/Ove…

beeeab0

…rlay-Specification into feat/action-templates Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

fix: updates wording for references definition

e64846a

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet added 2 commits March 3, 2026 08:46

Merge branch 'main' into feat/action-templates

e5be862

fix: aligns wording for the action fields in template and template re…

3a58335

…ferences Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

tests: additional pass tests for extensions

1cb9539

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet requested a review from mikekistler March 31, 2026 19:30

baywet marked this pull request as ready for review March 31, 2026 19:30

baywet requested a review from a team as a code owner March 31, 2026 19:30

baywet requested a review from handrews March 31, 2026 19:30

baywet added 4 commits March 31, 2026 15:43

fix: pattern validation in the schema

ccc453a

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

tests: adds missing tests for unescaped characters

2ba09b6

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

tests: increases coverage through additional fail tests

b05ab45

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

tests: duplicates additional tests that would be beneficial to earlie…

f0d5536

…r versions of the specification Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

handrews mentioned this pull request Mar 31, 2026

Add $self if external references are supported. #316

Open

baywet mentioned this pull request Mar 31, 2026

tests: improves coverage of the schema #317

Merged

Merge branch 'main' into feat/action-templates

6842b95

baywet mentioned this pull request Apr 1, 2026

add preview support for the resuable actions proposal BinkyLabs/openapi-overlays-dotnet#270

Closed

Merge branch 'main' into feat/action-templates

f9f5ffa

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet commented Apr 1, 2026

View reviewed changes

baywet mentioned this pull request Apr 1, 2026

feat: adds a parameter object for the action object #238

Closed

baywet commented Apr 2, 2026

View reviewed changes

ralfhandl reviewed Apr 5, 2026

View reviewed changes

baywet and others added 2 commits April 6, 2026 07:56

Apply suggestions from code review

f57ce30

Co-authored-by: Ralf Handl <ralf.handl@gmail.com>

chore: feedback updates for a number of tests

e03b60d

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

baywet requested a review from ralfhandl April 6, 2026 13:24

fix: allow underscores in parameter names

ad8f5e8

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

mikekistler reviewed Apr 6, 2026

View reviewed changes

baywet added 2 commits April 6, 2026 12:50

fix: removes outdated note about optional fields

569cff0

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

docs: better representation of the reusable action object

c04856d

Signed-off-by: Vincent Biret <vincentbiret@hotmail.com>

ralfhandl reviewed Apr 6, 2026

View reviewed changes


		#### Reusable Action Object

		This object is a component that can be reused by Reusable Action Reference Objects, it represents one or more changes to be applied to the target document at the locations defined by the target JSONPath expression and reused in one of more action references.

	\| <a name="reusable-action-parameters"></a>parameters \| [[Reusable action parameter object](#reusable-action-parameter-object)] \| A list of parameters to be used during string literal replacement. Optional. \|
	\| <a name="reusable-action-parameters"></a>parameters \| [[Reusable Action Parameter Object](#reusable-action-parameter-object)] \| A list of parameters to be used during string literal replacement. Optional. \|

	\| <a name="reusable-action-environment-variables"></a>environmentVariables \| [[Reusable action parameter object](#reusable-action-parameter-object)] \| A list of environment variables to be used during string literal replacement. Optional. \|
	\| <a name="reusable-action-environment-variables"></a>environmentVariables \| [[Reusable Action Parameter Object](#reusable-action-parameter-object)] \| A list of environment variables to be used during string literal replacement. Optional. \|

	\| <a name="reusable-action-action-fields"></a>Any field defined in the [action object](#action-object) \| mixed \| The [string literal replacement syntax](#string-literal-replacement-syntax) MAY be used for any of the fields, and the replacements MUST be evaluated as the reusable action reference is being resolved. \|
	\| <a name="reusable-action-action-fields"></a>Any field defined in the [Action Object](#action-object) \| mixed \| The [string literal replacement syntax](#string-literal-replacement-syntax) MAY be used for any of the fields, and the replacements MUST be evaluated as the reusable action reference is being resolved. \|


		A reusable action is similar to an action but differs in important ways:

		1. It may omit any action field, in particular the `target` field, as these may be supplied by the Reusable Action Reference Object.

	1. Any action field in the Reusable Action may employ string interpolation using variables specified in the `parameters` or `environmentVariables` fields.
	1. Any action field in the Reusable Action Object may employ string interpolation using variables specified in the `parameters` or `environmentVariables` fields.

	1. A Reusable Action MUST be referenced by a Reusable Action Reference Object to have any effect on the OpenAPI description.
	1. A Reusable Action Object has to be referenced by a Reusable Action Reference Object to have any effect on the OpenAPI description.

	\| <a name="reusable-action-reference-action-fields"></a>Any field defined in the [action object](#action-object) \| mixed \| Any field defined in the [Action Object](#action-object) to be used as an override to the value resolved in the reusable action. The [string literal replacement syntax](#string-literal-replacement-syntax) MAY NOT be used for any of the fields. Optional. \|
	\| <a name="reusable-action-reference-action-fields"></a>Any field defined in the [Action Object](#action-object) \| mixed \| Any field defined in the [Action Object](#action-object) to be used as an override to the value resolved in the reusable action. The [string literal replacement syntax](#string-literal-replacement-syntax) MAY NOT be used for any of the fields. Optional. \|

Conversation

baywet commented Feb 18, 2026

Uh oh!

ralfhandl commented Feb 18, 2026

Uh oh!

baywet commented Feb 24, 2026

Uh oh!

ralfhandl left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

baywet commented Mar 3, 2026

Uh oh!

baywet commented Mar 31, 2026

Uh oh!

baywet commented Mar 31, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

baywet commented Apr 2, 2026

Uh oh!

ralfhandl left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mikekistler left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ralfhandl left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment