← OloLand DDCONTENT HISTORY

Update to OloLand DD

Snapshot Nov 2, 2026 · 18:12 UTC · version 1.26.7

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save OloLand DD and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Connect OloLand and review available deal tools when the user requests setup or has a connection error.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 329
    }
  ],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Connect OloLand and review available deal tools when the user requests\n  setup or has a connection error.\n---\n# Connect OloLand\n\nThis is an explicit, user-invoked setup workflow. Enable the packaged `ololand`\nMCP connection, complete the client's OAuth sign-in, and inspect the tools\nactually available to the connected account. If authentication fails, ask the\nuser to reconnect. Never request, print, or store account credentials in chat.\nDo not run local setup scripts or claim a session-start hook has run.\nResolve a requested deal using the connected server; do not assume a sample\ndeal or entitlement exists. Report connection or permission gaps explicitly.\n\nOpenAI cannot execute this plugin's local lifecycle hooks. The upload supplies\nan explicit workflow, not an automatic setup gate. Server-side MCP auditing\nremains authoritative. Preserve tool-returned evidence and permission blockers;\nIC approval and other human-only gates stay with authorized people in OloLand.\n\n\n## OpenAI execution requirements\n\nUse the connected MCP server's current tool schemas. Do not invent tool arguments, job-status endpoints, inputs, or outputs. If a referenced tool is unavailable, explain the limitation and request the needed connection or data. Invoke writes only when the user has requested the corresponding action. Do not initiate purchases or payments. An unrun, unsupported, or unavailable procedure is a gap, never a passing result.\n\n\nOpenAI cannot execute local lifecycle hooks. Use the packaged explicit setup/review workflow when requested. Server-side MCP auditing remains authoritative; preserve evidence blockers and human-only approval gates.\n\nClaim-correction submission is unsupported in this OpenAI upload because the current handler records surface=cowork. Do not invoke submit_agent_claim_correction from OpenAI. Explain the limitation and retain proposed correction text for human review without claiming submission. See unsupported-workflows.json for the excluded canonical workflow.\n"
}

SHA-256 of public snapshot: 1debc308a08eb5191ea85e11b78bbc1f85984198e3b537c418ae9d137ccc5cb9