-- What each machine did with what it was last sent.
--
-- A node reports back after applying a declaration: everything worked, some of it failed, or the
-- whole thing was refused. Until this, a refusal or a failure moved `last_seen` and the reason
-- went to a log line -- so **which machine is not doing what it was told** had no answer the next
-- morning, and that is the question a mesh exists to answer.
--
-- One row per node, replaced. The question is about the machine's CURRENT state, not its history:
-- "this failed an hour ago and then succeeded" is not a machine anybody needs to look at, and a
-- table of every report would bury the ones that matter under the ones that do not.

create table node_report (
    node     uuid        primary key references node(id) on delete cascade,

    -- applied · failed · refused. Named rather than a boolean, because "some of it failed" and
    -- "none of it was applied" are different situations with different remedies, and collapsing
    -- them would make the report say less than the node did.
    outcome  text        not null,

    -- Why, when the whole declaration was refused. The node's own words: the host says exactly
    -- what it could not accept, and anything this end wrote instead would be a second, worse
    -- explanation of the same thing.
    refused  text        not null default '',

    -- Which resources failed, when some did, as [{id, error}].
    failed   jsonb       not null default '[]',

    -- How many were applied, for the ordinary case where nothing is wrong and the only useful
    -- fact is that the machine did what it was asked.
    applied  int         not null default 0,

    at       timestamptz not null default now()
);