fix(mcp): scope the claude web no-curl notice to non-hosted deployments

[pcfreak30]

Scopes the Claude Web "no network egress / no curl" notice to non-hosted (self-hosted/tunnel) deployments. On a hosted deployment the mint/drop endpoints are publicly reachable, so Claude Web gets the same generic curl file/drop guidance (mint PUT upload + sink=drop curl -o download) as other HTTP hosts and is no longer special-cased.

Adds the hostenv.And predicate and GuideSpec.RuleWhenPred for the host-and-deployment conjunction, and updates the Claude Web profile comment to reflect hosted vs non-hosted capability.

---

This pull request fixes the agent guide logic for Claude Web hosts by scoping the "no network egress" notice to only apply to self-hosted (non-hosted) deployments, not hosted (Portal-embedded) ones.

Key changes:

• Scope restriction: Previously, the Claude Web capability notice (warning about no curl/network egress) was shown for all Claude Web connections regardless of deployment type. Now, the notice is only displayed when Claude Web is used in a non-hosted (self-hosted) deployment.

• New gating mechanism: Added a RuleWhenPred method to GuideSpec that accepts custom predicate functions, enabling rules to be gated on complex conditions (like host type AND deployment mode).

• New predicate combinator: Added an And() predicate combinator in the hostenv package that passes only when all provided predicates pass, allowing rules to be gated on multiple conditions simultaneously.

• Hosted deployments behave like other HTTP hosts: When running in a hosted (Portal-embedded) deployment, Claude Web is no longer special-cased—it gets the generic mint/drop guidance (curl-based file upload and download flows) just like Grok and other HTTP hosts, since hosted deployments allow network access.

• Updated documentation: Comments in both agent_guide.go and the profile definitions were updated to explain the new scoping logic.

• Added test coverage: New tests verify that:

  • The Claude Web notice appears for non-hosted deployments
  • The notice is absent for hosted Claude Web deployments
  • Hosted Claude Web retains the generic curl-based upload/download guidance
  • The new And() predicate and RuleWhenPred methods work correctly

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[kody-ai]

The comment above the rule references 'hosted' and 'Portal' but contains no password, API key, secret, or token literals, so no hard-coded secret violation exists in the line itself. No code change required.

Kody rule violation: Ban hard-coded secrets in Go source

Prompt for LLM

File internal/mcp/agent_guide.go:

Line 353:

The comment above the rule references 'hosted' and 'Portal' but contains no password, API key, secret, or token literals, so no hard-coded secret violation exists in the line itself. No code change required.

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​

[github-actions]

Code Coverage Report

Total Coverage: 50.1%

Generated from commit: 8e4f186
Repository: LumeWeb/pinner-cli