---
name: refactor-state-errors-d53b008ca109
description: Refactor a service crate's state module to use domain-specific error enums instead of constructing end-user-facing error structs (error_type/message/status). Moves error shaping responsibility into the handler layer.
argument-hint: <service-name>
user_invocable: true
---

# Refactor State Errors

Replace the `{Service}Error { error_type, message, status }` anti-pattern in a service crate's `state.rs` with a domain-specific error enum. Move the mapping from domain errors to wire error responses into `handlers.rs`, restoring the separation of concerns described in ARCHITECTURE.md.

## Arguments

- `$0` — Service name matching the winterbaume crate suffix (e.g., `ses`, `guardduty`, `ssm`, `lambda`)

---

## Background

### The anti-pattern (current state)

Nearly every service crate defines this in `state.rs`:

```rust
pub struct SesError {
    pub error_type: String,   // AWS error code, e.g. "NotFoundException"
    pub message: String,      // Human-readable message
    pub status: u16,          // HTTP status code — does NOT belong in state
}
```

State methods construct these structs directly, coupling business logic to HTTP semantics:

```rust
pub fn get_email_identity(&self, name: &str) -> Result<&EmailIdentity, SesError> {
    self.identities.get(name).ok_or_else(|| SesError {
        error_type: "NotFoundException".to_string(),
        message: format!("Identity {name} does not exist."),
        status: 404,
    })
}
```

The handler then has a trivial pass-through function like `ses_error_response(err: &SesError) -> MockResponse` that just copies the three fields into the wire format.

### The target pattern

**`state.rs`** — domain-specific error enum using `thiserror`, with no HTTP knowledge:

```rust
use thiserror::Error;

#[derive(Debug, Error)]
pub enum SesError {
    #[error("Identity {name} does not exist.")]
    IdentityNotFound { name: String },
    #[error("Identity {name} already exists.")]
    IdentityAlreadyExists { name: String },
    #[error("ConfigurationSet {name} does not exist.")]
    ConfigurationSetNotFound { name: String },
    #[error("ConfigurationSet {name} already exists.")]
    ConfigurationSetAlreadyExists { name: String },
    #[error("Contact list {name} does not exist.")]
    ContactListNotFound { name: String },
    // ... more variants as needed
}
```

The `#[error("...")]` attribute generates `Display` with the message template. The message text should match the original message produced by the old code.

**Important:** Do NOT add `error_type()`, `status()`, or any other method on the error enum that returns HTTP status codes or AWS error type strings. These belong exclusively in the handler's error-shaping function. The whole point of this refactoring is to remove HTTP/wire knowledge from `state.rs`.

**`handlers.rs`** — error shaping maps variants to `(status, error_type)` and uses `err.to_string()` for the message:

```rust
fn ses_error_response(err: &SesError) -> MockResponse {
    let (status, error_type) = match err {
        SesError::IdentityNotFound { .. } => (404, "NotFoundException"),
        SesError::IdentityAlreadyExists { .. } => (400, "AlreadyExistsException"),
        SesError::ConfigurationSetNotFound { .. } => (404, "NotFoundException"),
        // ...
    };
    rest_json_error(status, error_type, &err.to_string())
}
```

---

## Step 0: Read the current code

Read all four source files to understand the service's error landscape:

```
crates/winterbaume-{service}/src/state.rs
crates/winterbaume-{service}/src/handlers.rs
crates/winterbaume-{service}/src/types.rs
crates/winterbaume-{service}/src/lib.rs
```

### 0a. Inventory all error constructions in state.rs

For every `{Service}Error { ... }` construction in `state.rs`, record:

| # | Method | error_type | message template | status | Proposed enum variant |
|---|--------|------------|------------------|--------|-----------------------|
| 1 | `get_email_identity` | `NotFoundException` | `"Identity {name} does not exist."` | 404 | `IdentityNotFound { name }` |
| 2 | `create_email_identity` | `AlreadyExistsException` | `"Identity {name} already exists."` | 400 | `IdentityAlreadyExists { name }` |
| ... | ... | ... | ... | ... | ... |

### 0b. Check for error helper functions in state.rs

Some services define helper methods like `fn detector_not_found() -> {Service}Error`. These should be replaced by enum variant constructors.

### 0c. Check for error constructions in handlers.rs

Handlers may also construct `{Service}Error` structs directly (e.g., for input validation in the handler before calling state). Those should either:
- Stay as direct `rest_json_error()` / `error_response()` calls (for pure request-parsing errors), or
- Be converted to enum variants if they represent domain logic.

### 0d. Check for external usage

```bash
grep -rn '{Service}Error' crates/winterbaume-{service}/src/
```

Confirm `{Service}Error` is only used in `state.rs` and `handlers.rs`. If `views.rs` or `lib.rs` reference it, plan accordingly.

---

## Step 1: Design the error enum

### Naming guidelines

- **Group by semantics, not by AWS error code.** Multiple AWS error codes that mean the same thing at the domain level (e.g., `NotFoundException` for identities vs configuration sets) should be separate variants if they carry different data, but can share a variant if they're truly identical.
- **Carry the minimum data needed to reconstruct the message.** Usually just a name/ID string.
- **Use descriptive variant names.** Prefer `IdentityNotFound` over `NotFound` when the service has multiple resource types. For services with a single primary resource type, `NotFound { id }` is fine.
- **Each variant gets an `#[error("...")]` attribute** that produces the exact message the old code generated. Use `thiserror`'s interpolation: `#[error("Identity {name} does not exist.")]`.
- **Include a generic `Validation` variant** for validation errors that don't fit a specific category:
  ```rust
  #[error("{message}")]
  Validation { message: String },
  ```
  This covers ad-hoc validation checks where defining a specific variant would be excessive.

### Deduplication

If the same `(error_type, status)` pair is used for multiple resources with the same message template (just different resource names), consider:
- Separate variants if the resource type is clear from context (preferred for clarity)
- A parameterised variant like `#[error("{resource_type} {name} does not exist.")] NotFound { resource_type: &'static str, name: String }` if there are many (5+) resource types with identical semantics

---

## Step 2: Implement the error enum in state.rs

### 2a. Add `thiserror` to the crate's `Cargo.toml`

`thiserror` is already a workspace dependency. Add it to the service crate's `[dependencies]`:

```toml
thiserror = { workspace = true }
```

### 2b. Replace the struct with an enum

Remove:

```rust
#[derive(Debug)]
pub struct {Service}Error {
    pub error_type: String,
    pub message: String,
    pub status: u16,
}
```

Add:

```rust
use thiserror::Error;

#[derive(Debug, Error)]
pub enum {Service}Error {
    #[error("Identity {name} does not exist.")]
    IdentityNotFound { name: String },
    #[error("Identity {name} already exists.")]
    IdentityAlreadyExists { name: String },
    // ... all variants from the inventory
}
```

Each `#[error("...")]` attribute must produce the **exact same message** as the old `format!(...)` / string literal in the original `{Service}Error` struct construction.

### 2c. Update all error constructions

Replace every `{Service}Error { error_type: ..., message: ..., status: ... }` with the appropriate enum variant.

**Before:**
```rust
Err(SesError {
    error_type: "NotFoundException".to_string(),
    message: format!("Identity {name} does not exist."),
    status: 404,
})
```

**After:**
```rust
Err(SesError::IdentityNotFound { name: name.to_string() })
```

### 2d. Remove error helper methods

Replace helper methods like `fn detector_not_found() -> {Service}Error` with direct enum variant usage. The enum variant is already as concise as a helper.

### 2e. Handle the `Validation` variant

For ad-hoc validation errors that construct messages inline, use the `Validation` variant:

**Before:**
```rust
return Err(SesError {
    error_type: "BadRequestException".to_string(),
    message: format!("Invalid email address: {addr}"),
    status: 400,
});
```

**After:**
```rust
return Err(SesError::Validation {
    message: format!("Invalid email address: {addr}"),
});
```

Only use `Validation` as a catch-all. If a specific validation failure is common enough to warrant its own variant (appears 3+ times), give it one.

---

## Step 3: Update the handler error-shaping function

### 3a. Replace the pass-through function with a match

**Before (pass-through):**
```rust
fn ses_error_response(err: &SesError) -> MockResponse {
    let body = json!({ "Type": "User", "Message": err.message });
    let mut resp = MockResponse::rest_json(err.status, body.to_string());
    resp.headers.insert(X_AMZN_ERRORTYPE, err.error_type.parse().unwrap());
    resp
}
```

**After (error shaping):**
```rust
fn ses_error_response(err: &SesError) -> MockResponse {
    let (status, error_type) = match err {
        SesError::IdentityNotFound { .. } => (404, "NotFoundException"),
        SesError::IdentityAlreadyExists { .. } => (400, "AlreadyExistsException"),
        SesError::ConfigurationSetNotFound { .. } => (404, "NotFoundException"),
        SesError::Validation { .. } => (400, "BadRequestException"),
        // ... all variants — NO wildcard arm
    };
    // Message comes from thiserror's Display impl via .to_string()
    rest_json_error(status, error_type, &err.to_string())
}
```

### 3b. Use `err.to_string()` for the message — do NOT duplicate message text

The message in the error response MUST come from `err.to_string()`, which delegates to the `#[error("...")]` attribute on the enum variant. Do NOT construct message strings inline in the match arms — this duplicates the message text and creates a maintenance risk. The match arms should only determine `(status, error_type)`.

**Wrong** (message duplicated in two places):
```rust
TimestreamWriteError::DatabaseNotFound { database_name } => (
    "ResourceNotFoundException", 404,
    format!("The database {database_name} does not exist."),  // BAD: duplicates #[error]
),
```

**Right** (single source of truth):
```rust
let (status, error_type) = match err {
    TimestreamWriteError::DatabaseNotFound { .. } => (404, "ResourceNotFoundException"),
    // ...
};
json_error_response(status, error_type, &err.to_string())  // message from #[error]
```

### 3c. Protocol-specific response format

The response format depends on the service's protocol. Use the existing `rest_json_error` / `error_response` helper that the handler already has.

| Protocol | Error body format | Header |
|----------|------------------|--------|
| restJson1 | `{"Type": "User", "Message": "..."}` | `x-amzn-errortype: ErrorCode` |
| awsJson1.x | `{"__type": "ErrorCode", "message": "..."}` | (none) |
| awsQuery | XML `<ErrorResponse><Error><Code>...</Code><Message>...</Message></Error></ErrorResponse>` | (none) |
| restXml | XML error body | (none) |

### 3d. Keep the match exhaustive

The match in the error-shaping function must be exhaustive (no wildcard `_` arm). This ensures that adding a new error variant in `state.rs` forces an update to the handler's error shaping — a compile-time guarantee that all domain errors have a defined wire representation.

---

## Step 4: Handle handler-originated errors

Some handlers construct `{Service}Error` for input-validation errors before calling state methods. Decide for each:

1. **Pure request-parsing errors** (missing JSON field, invalid JSON, unknown route) — keep as direct `rest_json_error()` calls; these are not domain errors.
2. **Domain validation errors** (invalid resource name format, conflicting parameters) — convert to enum variants and route through state, or use `{Service}Error::Validation { message }` at the handler level.

If the handler constructs `{Service}Error` structs directly (not calling state), update those to use enum variants too.

---

## Step 5: Update lib.rs exports

If `{Service}Error` is `pub` in `lib.rs` (for use in tests or views), ensure the enum is still exported. The type name stays the same, so this is usually a no-op.

---

## Step 6: Build and test

```bash
cargo build -p winterbaume-{service}
cargo clippy -p winterbaume-{service}
cargo test -p winterbaume-{service}
```

### Common issues

- **Non-exhaustive match**: add missing arms to the error-shaping function.
- **Field access on enum**: code that previously did `err.error_type` or `err.status` must use the match-based error-shaping function instead.
- **Type mismatch in tests**: if tests construct `{Service}Error` directly, update them to use enum variants.

### Verify correctness

Run the integration tests. The wire-level behaviour must not change — the same HTTP status codes, error type strings, and messages must be produced for the same inputs. This is a pure refactor.

```bash
cargo test -p winterbaume-{service} -- --test-threads=1
```

---

## Step 7: Verify no regressions

Compare the error-shaping match arms against the original inventory (Step 0a). Every `(error_type, message template, status)` triple must appear in the new match. Missing entries mean the refactor changed behaviour.

---

## Checklist

- [ ] `thiserror = { workspace = true }` added to the crate's `Cargo.toml`
- [ ] `{Service}Error` is now a `#[derive(Debug, Error)]` enum in `state.rs` with no HTTP status codes or AWS error type strings
- [ ] Every variant has an `#[error("...")]` attribute producing the original message text
- [ ] Every error construction in `state.rs` uses an enum variant
- [ ] The error-shaping function in `handlers.rs` has an exhaustive match (no wildcard arm)
- [ ] Every original `(error_type, message, status)` triple is preserved in the handler match
- [ ] No error helper methods remain in `state.rs` (replaced by enum variants)
- [ ] `./.agents/bin/cargo.sh build -p winterbaume-{service}` — no errors
- [ ] **Lint gate (mandatory before reporting)**: `./.agents/bin/cargo.sh clippy -p winterbaume-{service} --all-targets --all-features -- -D warnings` — passes. Fix any violations introduced by the refactor before finishing.
- [ ] **Fmt gate (mandatory before reporting)**: `./.agents/bin/cargo.sh fmt -p winterbaume-{service} -- --check` — passes.
- [ ] `./.agents/bin/cargo.sh test -p winterbaume-{service}` — all tests pass
- [ ] Wire-level behaviour is unchanged (same status codes, error codes, messages)


---
Source attribution: moriyoshi
Original project: https://github.com/moriyoshi/winterbaume/blob/69fed1d7fb0eb9a2738ff3274197c7591129c4cb/.agents/skills/refactor-state-errors/SKILL.md
License: Apache-2.0
License information: https://www.apache.org/licenses/LICENSE-2.0
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


## Additional upstream notices

refactor-state-errors-d53b008ca109/DAVEAI-UPSTREAM-NOTICE

Winterbaume
Copyright 2025 Winterbaume contributors

This product includes software developed at
https://github.com/getmoto/moto

=======================================================================
Moto - Mock AWS Services
=======================================================================

Copyright 2012 Steve Pulec

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Winterbaume used moto as a reference implementation for AWS service
mock behaviour and ported many of its Python test cases into Rust
integration tests. The moto source is available at
https://github.com/getmoto/moto.

Moto is written by Steve Pulec with contributions from:

  Zach Smith, Dilshod Tadjibaev, Dan Berglund, Lincoln de Sousa,
  mhock, Ilya Sukhanov, Lucian Branescu Mihaila,
  Konstantinos Koukopoulos, attili, JJ Zeng, Jon Haddad,
  Andres Riancho, Michael Ossareh, JeffMGreg, Hugo Lopes Tavares,
  Chris St. Pierre, Frank Mata, Clint Ecker, Richard Eames,
  Kevin Glisson, Shawn Falkner-Horine, David Baumgold,
  Rory-Finnegan, Bobby Impollonia, Ralfas, Omer Katz,
  Joseph Lawson, Trey Tacon, Peter, Tyler Sanders, Gary Dalton,
  Chris Henry, Mike Fuller, Andy, Mike Grima, Marco Rucci,
  Zack Kourouma, Pior Bastida, Dustin J. Mitchell,
  Jean-Baptiste Barth, Tom Viner, Justin Wiley, Adam Stauffer,
  Guy Templeton, Michael van Tellingen, Jessie Nadler,
  Alex Morken, Clive Li, Jim Shields, William Richard,
  Alex Casalboni, Jon Beilke, Bendeguz Acs, Craig Anderson,
  Robert Lewis, Kyle Jones, Mickaël Schoentgen, Ariel Beck,
  Roman Rader, Bryan Chen, Jonas Bulik, Rita Cheung,
  David Acevedo, Damon Williams

The full contributor list is available at
https://github.com/getmoto/moto/blob/master/AUTHORS.md.

=======================================================================
AWS API Models
=======================================================================

Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Winterbaume vendors a snapshot of the official AWS API Smithy models
under vendor/api-models-aws/ to drive its in-tree wire-type and
serialiser code generation. The upstream LICENSE and NOTICE files are
preserved alongside the vendored models. The upstream source is
available at https://github.com/aws/api-models-aws.


# Mega AI Hub resource metadata

Creator / publisher: moriyoshi
Original project: https://github.com/moriyoshi/winterbaume/blob/69fed1d7fb0eb9a2738ff3274197c7591129c4cb/.agents/skills/refactor-state-errors/SKILL.md
Attribution basis: Source repository record

Fields of work: Development & Engineering
Roles: Backend Developer, Data Engineer, DevOps / SRE
Specialties: Backend
Tools: Rust
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: bbd833f19caf3927112e4df17a8aad70ad704caf68b204b59d8294c33ef9acb8