## Issue
<!-- Comment-only correction (no runtime behaviour change) — no issue
required per typo-fix policy. -->
No issue — message-text correction only, no behaviour change.
## Change
`TablestoreEmbeddingStoreTest.testj_supported_value_types` is a guard
test: it fails when a new type is added to core
`Metadata#SUPPORTED_VALUE_TYPES`, and its failure message names the two
methods to update. The two method references were swapped:
- `rowToMetadata` was labelled "write logic", but `rowToMetadata(Row)`
reads a stored row into a `Metadata` (read).
- `innerAdd` was labelled "read logic", but `innerAdd(...)` writes
metadata into a `RowPutChange` and calls `putRow` (write).
A developer following the message would edit the wrong method. This
swaps the names to match the code (label order `1. write` / `2. read`
kept):
```java
.as("when Metadata#SUPPORTED_VALUE_TYPES add new types, we should modify:\n"
+ "1. write logic: innerAdd.\n"
+ "2. read logic: rowToMetadata")
```
The assertion (`isEqualTo(10)`) is unchanged.
## General checklist
- [X] There are no breaking changes (API, behaviour)
- [ ] I have added unit and/or integration tests for my change <!-- N/A
— message-text fix, no behaviour to test; the existing assertion is
unchanged -->
- [ ] The tests cover both positive and negative cases <!-- N/A — see
above -->
- [X] I have manually run all the unit and integration tests in the
module I have added/changed, and they are all green <!--
TablestoreEmbeddingStoreTest: 13 passed (JDK 17). *IT gated by
TABLESTORE_* credentials, not run. -->
- [ ] I have manually run all the unit and integration tests in the core
and main modules, and they are all green <!-- N/A — change is confined
to one test-message string; no production/core code touched -->
- [ ] I have added/updated the documentation <!-- N/A -->
- [ ] I have added an example in the examples repo <!-- N/A -->
- [ ] I have added/updated Spring Boot starter(s) <!-- N/A -->
<!-- "new maven module" and "embedding store integration" checklists
omitted — not applicable (test-message fix in an existing module). -->