HAP Private Deployment Web Edition (pd-openweb)

The Anonymous Funnel implements a server-first approach to session recovery and plan reconstruction:

Session Recovery Logic

• History Priority: Instead of relying on local snapshots, the system prioritizes server history.
• Resuming Sessions: If the endpoint /agent/sessions/{id}/messages is non-empty, the session is automatically resumed.
• New Sessions: If the history is empty, the system consumes handoff or pending messages to trigger the initial execute/stream call.
• Continued Chat: To continue a conversation, the client reuses the existing sessionId when calling agent/execute/stream with a new message. The current version baseline is then updated using the new completed artifactVersionId.

Plan Reconstruction

When restoring historical data, the system automatically reads assistant artifacts from: /artifacts/{artifactId}/versions/{versionId}/files/{path}. By retrieving the /plan.md and JSON files, the system can reconstruct:

• The Plan Card
• AppBuilder
• Mobile Overview

The regression tests for portalAccount cover critical security boundaries but have specific limitations that developers must account for when modifying request or interaction logic.

What is covered

• Info.test.js: Covers state contracts, refusal to edit without credentials, retry/re-validation, duplicate submission protection, failure recovery, request sequencing (A→B→A), and isolation of old responses after switching credentials or unmounting. It also protects against submission attempts during React.lazy loading when form refs are not yet established.
• restart.test.js: Covers WeChat mobile/PC entry points, PC QR code scanning, standard login, custom path recovery, double-slash fallbacks, and rejection of unauthorized external site/script/old callback redirects. It verifies that successful logins preserve business query/hash while removing only the portal identity callback keys.

Known Limitations and Constraints

• No E2E/Network: Tests are not full browser E2E tests. They do not perform real API calls, file uploads, field association network requests, or OAuth flows.
• WeChat ReturnUrl: Full WeChat mobile/PC authentication round-trips may still lose the ReturnUrl and redirect to the app homepage. Tests only verify clean restarts and re-initiating WeChat authentication.
• Exactly-once Guarantee: If a request/response is lost, the server may have already consumed the State. Re-submission might trigger re-validation; exactly-once delivery is not guaranteed.
• Recovery Scope: Failure recovery is limited to the temporary context owned by the current anonymous form. It will not overwrite other credentials or already logged-in accounts.
• Deployment Requirement: Deployment must be paired with backend GetUserCollect / InfoLogin validation specifically for information collection purposes.
• State/Cache: Existing State solutions remain unchanged. Cache isolation issues are deferred. If an old State lacks information collection permissions, it requires re-validation.

DesktopForm implements a keyboard-friendly navigation system using a publish-subscribe event management system. This allows users to quickly switch between form controls using the Tab key.

Core Architecture

1. WidgetEventManager: A central manager that handles subscriptions (subscribe) and event broadcasting (publish) based on controlId. It also supports cleaning up subscriptions via clear(instanceId).
2. Hooks System:
   • useFormEventManager: Manages form-level events, global keyboard listening, and the logic for calculating the next Tab target.
   • useWidgetEvent: A widget-level hook used by individual controls to subscribe to and respond to Tab enter/leave events.

Event Types

Workflow

1. User presses Tab.
2. handleTabChange captures the event and calls event.preventDefault() to stop default browser behavior.
3. The system queries all .customFormItem elements to build a list of controls.
4. supportTabKeyDown() determines the next valid control.
5. A trigger_tab_leave event is published to the current control.
6. A trigger_tab_enter event is published to the target control.
7. The tabFocusArr state is updated to track the current and previous control IDs.
8. The target control receives the event and executes its focus logic.

A Storage Type component must accept value and onChange props.

• value: The current value of the field.
• onChange: A function to call with the new value to update the field.

Icons: Lucide icons are pre-installed. To use them, use the LucideIcon component. The name prop must be the icon name in PascalCase (e.g., RefreshCcw). Other props follow the standard lucide-react API.

function RandomIdGenerator({ value, onChange }) {
  const [id, setId] = useState(value);

  return (
    <div className="flex items-center">
      <span className="flex-1 text-[#151515] text-[20px] font-bold text-center">{id}</span>
      <button
        onClick={() => {
          const newId = Math.random().toString(36).substr(2, 10);
          setId(newId);
          onChange(newId);
        }}
        className="p-2 bg-[#1677ff] text-white rounded-full"
      >
        <LucideIcon name="RefreshCcw" size={16} />
      </button>
    </div>
  );
}

To integrate the AI application builder into a marketing website (e.g., a Next.js static site) without adding React or ming-ui dependencies, use the standalone JS bundle. The widget provides an input box and example chips for anonymous user interaction.

1. Load the script: Include the generated bundle via a <script> tag.
2. Mount the widget: Call window.MingoEntry.mount() on a target container element.

Configuration Options for mount:

• webUrl: The base URL of the HAP application.
• apiServer: The API server endpoint.
• agentUrl: The agent service endpoint.

Behavior based on login status:

• Logged-in users: The widget redirects to the product version (e.g., /mingo/chat/:sessionId?entry=1 on PC).
• Anonymous users: The widget triggers an anonymous session and redirects to the HAP plan page (/public/mingo/plan).

<!-- 1. Load the bundle -->
<script src="/dist/mingo-entry-widget/mingo-entry-widget.js"></script>

<!-- 2. Target container -->
<div id="mingo-widget-container"></div>

<script>
  // 3. Mount the widget
  window.MingoEntry.mount(document.getElementById('mingo-widget-container'), {
    webUrl: 'https://your-hap-domain.com',
    apiServer: 'https://your-api-domain.com',
    agentUrl: 'https://your-agent-domain.com'
  });
</script>