multi-line spec with comments between tokens confused the preparser

[kumavis]

The multi-line spec with comments between tokens confused the preparser

[hierophantos]

Resolved by #4 (3d7ccb19) — parse-reader now splices indent-grouped continuation lines for spec forms, keeping -> at the top level where decompose-spec-type finds it. Line comments themselves were a red herring (the tokenizer strips them); the actual fix was to the indent-wrapping rule.

(Note on numbering: this is GitHub issue #1, which corresponds to pitfall #6 in the eigentrust memo. The branch name claude/fix-eigentrust-pitfall-1-firstcls from PR #8 refers to pitfall #1 in the eigentrust memo's independent numbering — that one was "primitive operators not first-class," a separate fix.)