flowstate-dojo-community-epicdm-flowstate-tunnel

Use this skill when a task touches packages/flowstate-tunnel, imports @epicdm/flowstate-tunnel, or needs to teach humans/agents how this package works.

Package identity:

• Package: @epicdm/flowstate-tunnel
• Repository: epic-flowstate-community
• Version authority: package.json (0.1.0)
• Dojo course: flowstate-dojo-community-epicdm-flowstate-tunnel

How to use the package:

• Purpose: Shared types and constants for FlowState Tunnel Service
• Start with package-local docs when present.
• Verify details against source and tests before changing behavior.
• Use the Dojo course lessons as the teaching path: setup, mental model, core workflow, integration, feature labs, maintenance.

Public surfaces discovered:

• HEARTBEAT_INTERVAL_MS
• STALE_TUNNEL_THRESHOLD_MS
• CLOUDFLARED_STARTUP_DELAY_MS
• CLOUDFLARED_SHUTDOWN_TIMEOUT_MS
• TUNNEL_DOMAIN
• CF_API_BASE
• MAX_SLUG_LENGTH
• SLUG_PATTERN
• TunnelConfig
• TunnelProvisionResponse
• TunnelStatus
• TunnelHeartbeat
• TunnelRegisterRequest
• TunnelProvisionRequest
• TunnelTeardownRequest
• TunnelKVRecord
• TunnelResult
• TunnelManagerState
• SlugValidationResult
• validateOrgSlug

Composable feature skilllets:

• CF_API_BASE: use feature labs for workflow, source anchor, and regression risk.
• CLOUDFLARED_SHUTDOWN_TIMEOUT_MS: use feature labs for workflow, source anchor, and regression risk.
• CLOUDFLARED_STARTUP_DELAY_MS: use feature labs for workflow, source anchor, and regression risk.
• HEARTBEAT_INTERVAL_MS: use feature labs for workflow, source anchor, and regression risk.
• MAX_SLUG_LENGTH: use feature labs for workflow, source anchor, and regression risk.
• SLUG_PATTERN: use feature labs for workflow, source anchor, and regression risk.
• STALE_TUNNEL_THRESHOLD_MS: use feature labs for workflow, source anchor, and regression risk.
• TUNNEL_DOMAIN: use feature labs for workflow, source anchor, and regression risk.
• Validate Org Slug: use feature labs for workflow, source anchor, and regression risk.

Agent operating rules:

• Treat package.json as the Dojo version authority.
• Do not turn feature inventory into user-facing lessons without workflow context.
• Update this Dojo package when package behavior, docs, examples, or feature inventory changes.
• Verify downstream packages when package use and connection metadata shows inbound dependencies or references.
• Never mark publish status passed without successful cloud publish and catalog lookup.

Use this Dojo skill with package human docs, package-local feature inventory, agent-skillset.md, and the generated course.json in this folder. Keep this manifest version aligned with package.json.