Showing only one statement during HALTING instead of the whole list

Instead of showing only, now a more complete output shows how statements could or would have been resolved. Per example:

[INV] ---- [DIGEST] started ----
[INV] ---- [DIGEST] #1 (state=RUNNING) ----
[INV] [my-server] => [BROADCAST] [Server] my-server-id
my-server-id has been broadcast
[INV] ---- [DIGEST] #2 (state=RUNNING) ----
[INV] [my-webservice] => [REQUIRE] [Server] my-server-id
[INV] [my-webservice] => [BROADCAST] [Endpoint] my-webservice-id
my-webservice-id has been broadcast
[INV] ---- [DIGEST] #3 (state=RUNNING) ----
[INV] nothing done
[INV] ---- [DIGEST] #4 (state=UNBLOATING) ----
[INV] nothing unbloated
[DEBUG] executor is shutting down
[INV] Completed INV(s): 2
[INV] Incompleted INV(s): 3
[WARN] INV(s): 
- my-app has 2 statement(s) left:
    1 requirement(s):
        [NOT MATCHED] [my-app] => [REQUIRE] [Endpoint] my-webservice-id-not-existing
    1 broadcast(s):
        [REQUIRED BY 2] [my-app] => [BROADCAST] [App] my-app-id
- my-app-2 has 4 statement(s) left:
    3 requirement(s):
        [NOT MATCHED] [my-app-2] => [REQUIRE] [Endpoint] my-webservice-id-not-existing
        [COULD MATCH] [my-app-2] => [REQUIRE] [App] my-app-id
        [UNBLOATABLE] [my-app-2] => [REQUIRE] [Endpoint] my-unbloatable-endpoint
    1 broadcast(s):
        [REQUIRED BY 1] [my-app-2] => [BROADCAST] [App] my-app-id-2
- my-app-3 has 5 statement(s) left:
    4 requirement(s):
        [NOT MATCHED] [my-app-3] => [REQUIRE] [Endpoint] my-webservice-id-not-existing
        [COULD MATCH] [my-app-3] => [REQUIRE] [App] my-app-id
        [COULD MATCH] [my-app-3] => [REQUIRE] [App] my-app-id-2
        [WOULD MATCH] [my-app-3] => [REQUIRE] [Endpoint] my-webservice-id
    1 broadcast(s):
        [REQUIRED BY 0] [my-app-3] => [BROADCAST] [App] my-app-id-3

[INV] ---- [DIGEST] completed ----

Will be documented in Wiki, but in summary:

REQUIRED BY #: Shows how many require statements would have consumed this broadcast statement
NOT MATCHED: A require statement that CAN'T be matched with the remaining INV's as it is when reported.
WOULD MATCH: A require statement matching an available broadcast statement. The later was made available during a RUNNING or UNBLOATING cycle
COULD MATCH: A require statement matching a non-available broadcast statement. The later was found in the remaining INV's broadcast statements during this reporting.
UNBLOATABLE: A require statement that would have unbloatable

peasoupio / inv

Showing only one statement during HALTING instead of the whole list #12