OrionIQ docs sync: Integrations nav, invocation feedback, one AI gate (ORIONIQ-1585, ORIONIQ-1613, ORIONIQ-1625) - #967
Merged
Conversation
…ORIONIQ-1613) - integrations.md: "Used by" is now a clickable button (agent list + links), connect/configure dialogs show the full description, sub-accounts count and roll up attention status as one connection. - agents-hub.md: feedback moves to the invocation drawer footer (all tabs, not just Output), documents the note flow and Skip action, adds the new Agent definition / Agent invocations / View invocations navigation. - agents.md: run log entry for this scan.
✅ Deploy Preview for deluxe-empanada-3ebf3b ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The bot's instructions say to edit the Slack notification once the Netlify preview link lands, but no message-edit tool is exposed — record that so a future run doesn't waste a cycle searching for one.
…eeds no doc update
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjpPVC3JXK4KmDSLNE7QRW
Reviewed Artemis #255 (ORIONIQ-1626 vendor sync, already assessed as internal-only), OIQ-AI-service #467 (ORIONIQ-1623 step-budget/recursion_limit SSE contract bump, not yet consumed by gaia/Artemis), and oiq-resources #92 (Azure Operator Nexus integration, catalog-depth addition with no new category or auth method). None require a documentation change this cycle. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JCzz6q1b5pBngihbksx9W2
… (ORIONIQ-1625) The two were never independently toggleable in a way that mattered to a customer, and after ORIONIQ-1625 collapsed them into a single "Enable AI usage" gate account-wide, describing them as separate entitlements is actively wrong: an account with only one of the two previously-separate settings on now gets both AI chat and agent invocations.
The create_or_update_file call already base64-encodes internally; passing pre-encoded content double-encoded the file. Restoring plain text.
…nt (ORIONIQ-1625) Run an agent and Send a follow-up now sit behind the account's AI usage gate, added in gaia-hermes-ws#17047 as part of collapsing AI entitlement to one check. Polling, enable/disable, and feedback stay reachable when AI is off, so those are left alone.
Records the AI-entitlement doc corrections made this cycle, the Slack optional-secret revert audited as no-doc-change (catalog-depth precedent), the ORIONIQ-1480 analytics prep deferred as not-yet-shippable, and an escalation: PR #17045 deleted the legacy AI chat this repo's assistantiq.md still walks through, which is worse than the pre-existing "no OrionIQ chat page" gap and belongs to the already-scoped AI docs refactor, not a piecemeal patch.
galangel
changed the title
Scanned Artemis, OIQ-AI-service, gaia-hermes-ws, and oiq-resources for the last 24h. The one notable merge is Artemis#278 (ORIONIQ-1393/1480), completing the composer "next question" ghost-text suggestion end to end - the feature this log has been carrying as "recheck once it ships" since 2026-09-09/10. It still has nowhere to be documented: OrionIQ chat has no page in this repo, and this is now the second shipped chat feature stacked on that same standing blocker. Escalated in "Known gaps" rather than patched piecemeal into assistantiq.md, consistent with the review feedback already on record for that mistake. Everything else in the window (a smoke-test fix, a CI script change, version-bump commits, and seven gaia-hermes-ws commits that are AI Observability / dashboard work outside OrionIQ scope) needed no doc change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JL4Stp5BKTPDdozRc9enzM
Artemis#285 (ORIONIQ-1625) fixes usage-cap enforcement to return 429/CAP_EXCEEDED instead of a bare 500 on Run an agent and Send a follow-up. Add a note next to the existing AI-disabled 403 note.
gaia-hermes-ws#17039 (ORIONIQ-1633) reduces app-ai to a pure redirect shim; Artemis's orioniq-be is now the canonical OrionIQ backend and route authority. Update the "Where the code lives" table and the "Canonical source for the public API" section accordingly, and log today's scan across all four source repos.
RoyiSitbon
approved these changes
Sep 15, 2026
Resolves an agents.md conflict: the 2026-09-14 run-log entry landed directly on master (a separate cycle's session apparently pushed to master instead of this PR's branch) while this branch kept going with its own 2026-09-13/15 entries. Both entries are kept, in chronological order — the run log is append-only and this is exactly the same 'session doesn't share branch continuity' failure mode already noted in the 2026-09-01 entry, just landing on master this time instead of a stray branch.
yotamloe
reviewed
Sep 15, 2026
yotamloe
reviewed
Sep 15, 2026
Per review feedback on #967: gaia-hermes-ws#17039 (ORIONIQ-1633) made app-ai answer every /v2/* request with a 307 to its orioniq-be equivalent, and its own PR description flags 'public-API customers using curl without -L' as a caller that silently breaks on this. Add a note so integrators know to follow it rather than treat the redirect response as the result. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The new redirect note tells readers to follow redirects, but the copy-paste curl samples didn't demonstrate it — fix that so the samples actually work as-is against the current 307 behavior. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Scanned commits merged since 2026-09-15 across Artemis, OIQ-AI-service, gaia-hermes-ws, and oiq-resources. Only Artemis#304 (agent-runs/search field projection) falls in OrionIQ scope; it's an internal BFF optimization with no customer-facing route/schema change, so no doc content changes are needed this cycle. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X3KX7UpE8uaV8z1yVXB3aS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OrionIQ docs sync
Automated sync of OrionIQ's public-facing documentation against recent changes in
Artemis,OIQ-AI-service,gaia-hermes-ws, andoiq-resources.Changes in this PR
ORIONIQ-1585 — Integrations page
integrations.md: the Management tab's "Used by" count is now a clickable button opening a modal listing the agents using a connection; connect/configure dialogs show the full integration description; Logz.io sub-accounts roll up into a single connection row.ORIONIQ-1613 — Invocation feedback
agents-hub.md: feedback moves to a footer rail visible on every tab, with optimistic rating and a note composer; new Agent definition / Agent invocations navigation links from a run; rating a running invocation is now blocked.ORIONIQ-1625 — Single AI entitlement gate
ai-settings.md: replaced the "separate entitlements for chat and invocations" description with the single account-wide AI usage setting.api.md: added a403note (AI disabled for the account) and a429/CAP_EXCEEDEDnote (account has reached its AI usage cap) on Run an agent and Send a follow-up.Audited, no doc change needed
gaia-hermes-ws#17039 (ORIONIQ-1633) —app-aireduced to a pure redirect shim toArtemis'sorioniq-be; internal architecture only, no customer-visible surface change. Logged inagents.md.Artemis,gaia-hermes-ws, andOIQ-AI-service— internal/BFF surfaces never documented here.AgentRequestBody.agentType/AIDataSourceenum narrowing — doesn't touch any field this repo documents.agents.md's run log.Known gap (flagged for the team, not fixed here)
docs/open360/observability/assistantiq.mddescribes a legacy AI chat UI that has since been deleted; the OrionIQ chat itself has no page in this repo yet. This needs the agreed AI-docs section refactor (seeagents.md), not a piecemeal patch.No approved screenshots were found to embed in this cycle.
🤖 Generated by the OrionIQ API Documentation Sync Bot