So, that was my (bad, as it turns out) advice. There are some clicks in your tree expansion that are not maximal, i.e. {2, 0, 1}, {0, 1} and {1}. Candidate click list
{4, 5, 6} (maximal) {3, 2} (maximal) {5, 6, 2, 0} (maximal) {7, 2, 1} (maximal) {6, 2, 0, 1} (maximal) {2, 0, 1} (not maximal: subset of {6, 2, 0, 1}) {0, 1} (not maximal: subset of {6, 2, 0, 1}) {1} (not maximal: subset of {6, 2, 0, 1})
Then the decomposition should look like
{3, 2} | {4, 5, 6}----{5, 6, 2, 0} | {7, 2, 1} | {6, 2, 0, 1},
which is also incorrect, since 0 vertices are not connected. Excuse me.
What I had to do was to postpone the maximality condition for the moment and connect each clique K to the next candidate, seeded with a vertex belonging to K. This ensures that every vertex in K existing in at least one other subsequent a click also appears at the connection target. Then the decomposition looks like this:
{4, 5, 6}----{5, 6, 2, 0} | {6, 2, 0, 1} | {3, 2}----{2, 0, 1}----{7, 2, 1} | {0, 1} | {1}
and you can splicing non-maximal clicks by checking for each click in reverse order whether this is a superset of your parent, and if so, re-educating its parent children.
{4, 5, 6}----{5, 6, 2, 0} | {3, 2}----{6, 2, 0, 1}----{7, 2, 1}