ci: Format code

Author: seambot

NESTED_RESOURCES.md

@@ -3,7 +3,7 @@
 ## Task
 
 Nested properties on generated resource dataclasses have **no types, no docs, and
-no autocomplete**, and the declared annotation *contradicts* the runtime object.
+no autocomplete**, and the declared annotation _contradicts_ the runtime object.
 Fix this by generating a dataclass per nested object, so nested properties get
 real types, real docstrings, and completion — and so the annotation matches what
 `from_dict` actually assigns.
@@ -30,26 +30,26 @@ properties=DeepAttrDict(d.get("properties", None)),
 
 Consequences:
 
-| Expression | Runtime | Type checker |
-|---|---|---|
-| `device.properties.locked` | works | **error** — `Dict[str, Any]` has no attribute `locked` |
-| `device.properties["locked"]` | works | passes, returns `Any` — no completion, no docs |
+| Expression                    | Runtime | Type checker                                           |
+| ----------------------------- | ------- | ------------------------------------------------------ |
+| `device.properties.locked`    | works   | **error** — `Dict[str, Any]` has no attribute `locked` |
+| `device.properties["locked"]` | works   | passes, returns `Any` — no completion, no docs         |
 
 So the access pattern the SDK is designed for does not type-check, and the one
 that type-checks tells you nothing.
 
 **Docs are top-level only.** `codegen/layouts/partials/resource-dataclass.hbs`
 iterates `properties` exactly once and emits a flat `:ivar` list, so nested
 shapes are undocumented. The only mention of any nested field name in all of
-`device.py` is incidental prose inside a *different* field's docstring:
+`device.py` is incidental prose inside a _different_ field's docstring:
 
 ```
 :ivar display_name: Display name of the device, defaults to nickname (if it is
   set) or ``properties.appearance.name``, otherwise.
 ```
 
 **`errors`/`warnings` are worse than nested objects.** They are
-`List[Dict[str, Any]]` and, unlike `properties`, are *not* wrapped at all
+`List[Dict[str, Any]]` and, unlike `properties`, are _not_ wrapped at all
 (`errors=d.get("errors", None)`, line 169). So `device.errors[0].error_code`
 raises `AttributeError` — subscript access is mandatory. Compare Ruby, which
 coerces these into real `ResourceError` objects where `.error_code` works.
@@ -157,8 +157,8 @@ That keeps both access styles working. Only `dict(...)` and
 narrowing.
 
 **One intentional behavior change to call out in the changelog:** today
-`device.properties.typo` silently returns an empty `DeepAttrDict` *and mutates the
-object*, inserting the typo'd path (see `seam/utils/deep_attr_dict.py:19-25`).
+`device.properties.typo` silently returns an empty `DeepAttrDict` _and mutates the
+object_, inserting the typo'd path (see `seam/utils/deep_attr_dict.py:19-25`).
 With dataclasses it raises `AttributeError`. That is strictly better — it matches
 Ruby, and it turns silent typos into errors — but it is a behavior change and
 someone may be relying on the falsy-empty-dict result.