## Summary [//]: # (Summarize the bug encountered concisely) The target SDK emits state messages as `singer.StateMessage` instead of just passing along the state payload from the tap. This causes a bug where the state thats output isnt valid and grows consistently over time. ## Steps to reproduce [//]: # (How one can reproduce the issue - this is very important) Run a `meltano elt` sync using a target built with the SDK. Afterwards check the payload field in the system database. It should look like `{"singer_state": {"bookmarks":...` not `{"singer_state": {"type": "STATE", "value":...` ## What is the current bug behavior? [//]: # (What actually happens) State messages are emitted from the target. ## What is the expected correct behavior? [//]: # (What you should see instead) State payloads should be emitted from the target. ## Relevant logs and/or screenshots [//]: # (Paste any relevant logs.) [//]: # (Please use code blocks ``` to format console output, logs, and code, as it's very hard to read otherwise.) ## Possible fixes [//]: # (If you can, link to the line of code that might be responsible for the problem) https://gitlab.com/meltano/sdk/-/blob/main/singer_sdk/target_base.py#L323