Tiinex Feedback

This package is the VS Code-specific extension surface for the feedback repo.

It intentionally lives under ides/vscode because the repo itself is broader than one IDE package.

Quick Start

After you install the extension in VS Code, the fastest first checks are:

• run Tiinex: Open Feedback Topic Index
• run Tiinex: Open Latest Feedback Topic
• if you use chat tools, type # and pick #getFeedbackTopicIndex

The important operator detail is that chat usually exposes prompt-reference names after #, not the raw internal tool ids. In practice you should expect #getFeedbackTopicIndex, not get_feedback_topic_index.

What To Expect

This package is intentionally small in its current Marketplace form.

• It reads existing topic artifacts.
• It does not yet claim a finished create/edit workflow.
• It is best used when you want a bounded overview of the newest feedback topics without manually traversing repo files.
• In chat, the tool is usually invoked through #getFeedbackTopicIndex.

Current status:

• buildable as a real VS Code extension
• ready for local main-host junction linking on Windows
• now carries a top-level extension icon and marketplace-facing manifest surface
• experimental
• focused on bounded topic-reading surfaces first

Current included surface:

• Tiinex: Open Feedback Topic Index
• Tiinex: Open Feedback Topics Folder
• Tiinex: Open Latest Feedback Topic
• #getFeedbackTopicIndex as the usual chat-facing tool reference

Current bounded reading behavior:

• the topic index renders a compact markdown overview of the newest topic files under topics/
• latest-topic open is a direct file-open convenience surface
• folder-open is a simple navigation surface for the experimental artifact store
• bounded topic index size is now configured under tiinex.feedback.topicIndexMaxItems

What it exposes in VS Code:

• display name: Tiinex Feedback
• LM tool surface: get_feedback_topic_index
• command namespace: tiinex.feedback.*
• settings namespace: tiinex.feedback.*

Local development loop:

• This section is for extension contributors rather than Marketplace-first users.
• npm test builds and runs the current validation slice
• npm run package:vsix produces a local VSIX for install testing
• npm run watch rebuilds during local extension work

Release flow:

• npm test
• npm run package:vsix
• npm run release:check
• npm run release:patch, npm run release:minor, npm run release:major
• npm run publish:vsce

Non-goal for this package scaffold:

• no MCP surface
• no claim that full topic creation/editing is finished