fix(apps): treat accessible-link requests as publish intent

[raistlin042]

Summary

When a user asks for an accessible / online / shareable URL after a cloud session completes, the lark-apps skill did not make explicit that this is a publish intent. The model could return the dev-mode /app/{app_id} link or a historical published URL instead of running the release flow. This gap surfaced in eval cases S4-06 / S4-07. This PR adds a publish-intent trigger rule and guardrails so "give me an accessible link" routes to the publish flow.

Changes

• Add a publish-intent trigger bullet at the top of the "发布态与链接交付" section in skills/lark-apps/SKILL.md (app_type-agnostic: covers both html and full_stack)
• Add a guardrail to the dev-mode-link bullet in skills/lark-apps/SKILL.md (dev link is for entering edit mode only, must not substitute for publishing)
• Add the same guardrail to the dev-mode-link bullet in skills/lark-apps/references/lark-apps-cloud-dev.md

Test Plan

• validate passed (build / vet / unit / integration)
• skipped: sandbox E2E — lite mode, no CLI behavior change
• skipped: skillave — S4-06/07 require a real cloud app and a real deploy; verified out-of-band against the Base eval set
• acceptance-reviewer passed (2/2 scenarios)
• manual verification: grep -rnE '\+publish(-status)?\b' skills/lark-apps/ returns no match (no dead command-name regression)

Related Issues

N/A