K2: 7.000000 - block or expand territory
K2: 0.650000 - influence
Move generation values K2 to 7.650000
Reading the full report we find that the
only pattern matched at K2 is CB241, which
looks like this:

Pattern CB241
.. block off area
.*
OX
:8,XOb,NULL
..
ba
OX
;odefend_against(a,b)
At the very least, a pattern of type C should be matched
here, since K2 establishes a connection between two
dragons. Let's add one. Add the following pattern to
patterns/patterns.db, then recompile GNU Go.

Pattern EC68
# db added (2.7.201)
O.XOo connect underneath
..*.o
.....
-----
:8,CXda
O.Abo
..*.o
.....
-----
; lib(A)<4 && lib(b)>2 && !attack(A)
The significance of the constraint is that if the X stone
has only 3 liberties and the right O stone has at least
three, then the pattern almost guarantees connection. There
are rare cases where it could be cut, and these could be
handled by a more elaborate constraint, but even in such a
case the move at least threatens to connect, and is
probably beneficial, so perhaps we don't need to bother
with this. The last constraint excludes the case where the
X stone can be tactically captured, since if that is true,
there is a better move.

After this change, GNU Go finds the right move K2
with the following move reasons: