Implement inline code suggestions via InlineCompletionItemProvider

[Copilot]

• Create inline completion provider (src/inline/provider.ts)
• Register provider in extension activation
• Add configuration settings for inline completions
• Add debouncing and cancellation support
• Test inline suggestions functionality
• Update documentation
• Address code review feedback (configurable max length)
• Remove package-lock.json files (use bun for package management)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Flixa: Inline suggestions</issue_title>
<issue_description>Implement inline suggestion functionality for Flixa to enhance user experience and productivity. Users should be able to receive context-aware suggestion prompts while interacting with the application.

Expected outcomes:

• Contextual inline suggestions are displayed where appropriate.
• Suggestions are non-intrusive and can be accepted or ignored by users.
• Simple, clear UI/UX for managing suggestions.

Benefits:

• Improves workflow speed for users.
• Reduces manual input and provides guidance.

Please scope initial implementation details, design, and integration points.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Flixa: Inline suggestions #1

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[raicdev]

@copilot delete package-lock.json and use bun for pm

[Copilot]

@copilot delete package-lock.json and use bun for pm

Done. Removed package-lock.json files and added them to .gitignore. The project uses bun for package management. (f41647c)

[deni-ai-harbor]

Harbor finished work

Target: #2

Review Run Result

Run Result

• Result: Review submitted (1 inline comments).
• Overall summary comment: posted.
• Processing time: ~43s

[deni-ai-harbor]

Inline completions look generally reasonable, but there is at least one high-confidence reliability issue in the new request path that should be guarded before merge.

[deni-ai-harbor]

Guard against missing model/provider configuration before invoking the SDK; otherwise typing can throw repeatedly when the extension is enabled but not fully configured.

Suggested change

	const provider = getAnthropicProvider();
	const provider = getAnthropicProvider();
	const model = getModel();
	if (!provider || !model) {
	return undefined;
	}