chore(commitlint): enforce stricter validation

[iamfj]

What does this PR do?

• enforce stricter validation

Type of change

• internal

Checklist

• npm test

Testing

• npm test

Notes for reviewers

• CONTRIBUTING.md
• commitlint.config.js

Related issues

• Closes chore: Strengthen commitlint validation rules #97

[chatgpt-codex-connector]

💡 Codex Review

linearis/src/commands/comments.ts

Lines 159 to 162 in 4cd611f

	const result = await replyToDiscussion(ctx.gql, {
	threadId: thread,
	body: options.body,
	});

Enforce issue-only scope in comments reply command

The comments domain is documented as an issue-only compatibility facade, but this call omits entityKind: "issue", so any valid root thread UUID (including project/initiative discussions) can be replied to through comments reply. In practice, that means legacy issue-comment automation can mutate non-issue discussions if IDs are mixed, which violates the command contract and can target unintended entities.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[iamfj]

Addressed the review feedback by passing entityKind: "issue" from comments reply to replyToDiscussion, so the deprecated compatibility facade only accepts issue discussion threads. Added/updated command coverage for that delegation.\n\nValidation:\n- npm run check:ci\n- npx tsc --noEmit\n- npx vitest run tests/unit/commands/comments.test.ts\n- npm test