[sheepsteak]

Closes #28.

@blitz/lines-around-comment requires a blank line before a comment at the start of a namespace/module block, and prettier/prettier deletes that blank line, so code like this can't pass both rules:

declare namespace something {
  /** JSDoc describing this */
  export const entry: 1;
}

The @blitz rule only handles comments at the start/end of enums, switches, arrays, objects, and type literals itself (START_END_NODES). Comments in a TSModuleBlock fall through to the wrapped @stylistic/ts/lines-around-comment rule, which already supports allowModuleStart. The recommended config never enabled it, so this PR sets allowModuleStart: true next to the other allow*Start options. TypeScript files get the same options through tsRules(). Comments elsewhere in a namespace still need a blank line before them.

Alternatives considered:

• Adding TSModuleBlock to START_END_NODES. The rule's isStartAllowed/isEndAllowed checks are an OR across every allow*Start/allow*End option, so unrelated options such as allowArrayStart would also exempt namespaces.
• Also setting allowModuleEnd. It has no effect, because the config doesn't enable afterBlockComment/afterLineComment.

Tests

• New spec cases for allowModuleStart cover declare namespace, namespace, declare module 'foo', and the fixer output when the option is off.
• Two cases run the rule with the options from the shipped jsRules. One checks that the issue's snippet is valid, and one checks that a comment in the middle of a namespace still errors. Reverting the config line makes the first one fail.
• I also ran the issue's snippets through the full recommended() config, including prettier/prettier. The snippet without a blank line is now clean for both rules. Comments at the start of namespace A.B and declare module 'foo' blocks are clean too.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if applicable (n/a: allowModuleStart is a base rule option, already covered by the linked @stylistic/ts docs)
• I have added tests for this change

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.