fix(globals): Globals methods operate on this-> not global g

[TimD1]

Root cause

Several Globals member functions in src/globals.cpp read and wrote configuration fields through the global instance g (e.g. g.cmd, g.verbosity, g.max_size) rather than this->. This is a latent defect: those methods only behave correctly when invoked on the global instance g. Called on any other Globals instance, they would read from and mutate g instead of that instance.

Affected methods:

• init_timers() — appended to g.timers
• parse_args() — read/wrote g.cmd, g.verbosity, g.write, and the final validation checks (g.max_qual, g.min_qual, g.max_size, g.sv_threshold, g.max_supercluster_size)
• print_usage() — printed defaults from g.verbosity, g.max_size, g.sv_threshold, g.min_qual, g.max_qual, g.max_supercluster_size, g.credit_threshold, g.max_dist, g.max_threads, g.max_ram

Fix

Converted every active g.<member> reference inside Globals member functions to this-><member> — 25 references across the three methods. Commented-out dead code (the disabled --max-iterations, --mismatch-penalty, etc. usage lines) is left untouched.

Behavior impact

Unchanged in production, since these methods are always invoked on the global g. The class is now correct for any instance.

Verification

Compiles clean:

g++ -c -g -O1 -Wall -Wextra -std=c++17 globals.cpp

No warnings or errors.

---

Fixes #69
Sub-issue of #45 (D2 §6 defect #11).