parseGoals: positional goal IDs collide with explicit IDs, corrupting PRINCIPAL_TELOS.md every session

[vichong]

parseGoals() assigns positional IDs to goal bullets lacking explicit ones, and the counter can collide with real explicit IDs elsewhere in the file.

On a live v7.x install the @-imported PRINCIPAL_TELOS.md rendered:

• G4 as an active goal and as the deferred entry (two different goals, same ID)
• The real completed goal G3 relabelled as G5, G6

Since PRINCIPAL_TELOS.md is imported at every session start, this corrupts the model's context silently and persistently.

Workaround: give every bullet an explicit ID in GOALS.md.

Suggested fix: seed the positional counter above the highest explicit ID found in the file, or refuse mixed implicit/explicit numbering with a loud error.

[danielmiessler]

Fixed — the positional counter now seeds above the highest explicit G<n> found across all buckets, so an auto-assigned ID can never collide with an explicit one (GenerateTelosSummary.ts, credit comment cites you). ID-less files are unaffected — verified byte-identical regeneration. Ships in the next release.