Task: Carry the host on the heartbeat

Every service heartbeat carries the service name, the instance id and the release, and no host. The compute side is the mirror: each node sample carries the host id, and no instance id. Nothing joins an instance to the machine it runs on, or a compute wrapper to its node (The service heartbeat carries no host). This task adds host_id to service_heartbeat_message and stores it on service_sample beside instance_id, so the grid's wrapper panel and the services roster can name the machine behind an instance.

• service_heartbeat_message carries a host_id, and service_sample stores it beside instance_id.
• The publishing side fills it wherever it already holds the id, the compute wrapper first: the wrapper already stamps its node samples with it.
• The capture The service heartbeat carries no host moves out of the inbox with this task's evidence.
• The change regenerates cleanly, and the telemetry and compute tests pass.

The field travels one way: a publisher stamps it, the telemetry service copies it, and the database stores it. The work follows that path. Both messages keep one field order — service_name, instance_id, host_id, version — so the model, the entity and the stored row agree.

1. Add host_id to service_heartbeat_message and service_sample in projects/ores.telemetry/modeling/ores.telemetry.service_samples.org. The field sits beside instance_id, and it is empty when the publisher does not know the host.
2. Regenerate the protocol from the model, and check the C++ and TypeScript diffs carry the new field and nothing else.
3. Fill the field where the value exists. heartbeat_publisher takes host_id as a trailing defaulted constructor argument and stamps every message with it, and the compute wrapper passes cfg.host_id — the value it already stamps on its node samples. Every other service holds no host id, so its beats carry the empty string.
4. Copy the field at the receiving end: telemetry_handler::service_heartbeat writes hb->host_id onto the service_sample it builds.
5. Store it. service_sample_entity gains std::string host_id;, the mapper carries it both ways, and the create script adds host_id text not null default ''.
6. Prove it. Add a repository test that inserts a sample with a host id and reads it back through list_service_samples, then build and run the telemetry and compute tests against a recreated database.
7. Close the loop. Move capture A1D7FC12 out of the inbox with the evidence, and record the measurements on this task.

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

The design is settled on The service heartbeat carries no host: one field, not a new entity. The alternative — a release and an instance id on the node sample — answers the grid's join only, and leaves the services screen blind.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

service_heartbeat_message and service_sample carry host_id, and the one field answers both joins the capture named: a wrapper's row can name its node, and an instance's row its host.

The field travels the whole path. The model carries it on both messages, the regenerated C++ and TypeScript protocols carry it, and heartbeat_publisher takes it as a trailing defaulted argument and stamps every beat. The compute wrapper passes cfg.host_id, the value it already stamps on its node samples; every other service sends the empty string. telemetry_handler copies it onto the sample, and the entity, the mapper and the host_id text not null default '' column store it.

Verification. The repository test create_and_list_service_sample writes a sample with a host id and reads it back through list_service_samples. The telemetry suites (3/3) and the compute suites (3/3) pass against a recreated database. See the measurements above.