## Context

Implementation is split into two phases:

**Phase 1 (this change): Infrastructure stub**
- Create the npm package with minimal `{ router, startApp }` skeleton (all routes return 200 placeholders)
- Register server pubmodule in `pubModulesManager.js`
- Add Dashboard UI: channel type constants, Integrations page entry, channel badges, assets
- Instagram appears in the Dashboard Apps page as an installable channel immediately

**Phase 2 (future): Full integration**
- Implement Instagram OAuth flow (based on lab `instagram-oauth.js`)
- Implement webhook handlers for inbound/outbound messages
- Create translator and API client
- Wire up real configuration form

The Messenger connector is the blueprint because it shares the Meta Graph API platform with Instagram.

## Goals / Non-Goals

**Goals (Phase 1):**
- Create stub npm package with `{ router, startApp }` skeleton
- Register server pubmodule at `/modules/instagram`
- Add Instagram channel type constants in Dashboard and Design Studio
- Add Instagram to Integrations page with icon
- Add Instagram channel badge to conversation list templates

**Non-Goals (Phase 1):**
- Real Instagram OAuth or API integration (Phase 2)
- Webhook handling
- Message sending/receiving
- Lab code integration

## Decisions

### Decision: Stub connector returns 200 for all routes
The stub `index.js` will have placeholder handlers for all standard connector routes (`/`, `/detail`, `/configure`, `/install`, `/uninstall`, `/update`, `/disconnect`, inbound, outbound). Each returns a simple JSON response indicating the connector is not yet configured.

### Decision: Use `@resultcrafter/aimanager-instagram-connector` npm scope
Package will be published under `@resultcrafter` scope on npm.

## Risks / Trade-offs

- **[No real functionality]** → Phase 1 is purely cosmetic. The Integrations page will show Instagram, but clicking it will show a placeholder. No risk to existing channels.