Skip to content

docs(skill): list_recent_decisions hardening [skip-runtime-e2e] #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
saurabhjain1592 merged 3 commits into from
May 8, 2026
Merged

docs(skill): list_recent_decisions hardening [skip-runtime-e2e] #61

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1ebbb74
docs(skill): tighten list_recent_decisions agent guidance
saurabhjain1592 May 8, 2026
4210338
chore(changelog): trim 1.4.0 telemetry entry to compact format [skip-…
saurabhjain1592 May 8, 2026
12c4132
chore: re-trigger CI after PR title/body update [skip-runtime-e2e]
saurabhjain1592 May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,11 @@
### Added

- **V1.1 `list-recent-decisions` skill** (axonflow-enterprise#1982). Drives the new `list_recent_decisions` MCP tool from Codex; Free-tier cap-hits render the V1 upgrade envelope verbatim. Plus `runtime-e2e/list-recent-decisions/` and a 7th over-cap scenario in `tests/e2e/runtime-mcp-tools.sh`.
- **v1 telemetry-schema** (axonflow-enterprise#2008): heartbeat now emits `telemetry_type: "plugin"`, `endpoint_type` (`localhost | private_network | remote | unknown`), and `profile` from `AXONFLOW_PROFILE`.
- `AXONFLOW_PROFILE` env var: drives the new `profile` payload field; reports `unknown` when unset.
- `AXONFLOW_TRY=1` env var: forces `deployment_mode=community_saas` for tenants behind custom hostnames proxying try.getaxonflow.com.

### Changed
### Telemetry

- `deployment_mode` allowlist normalised to `self_hosted | community_saas | unknown` (was `production`/`development`/`community-saas`). Detection now derives from endpoint host + `AXONFLOW_TRY=1`. Analytics queries on the legacy values must update.
- v1 schema (axonflow-enterprise#2008): heartbeat now emits `telemetry_type: "plugin"`, `endpoint_type` (`localhost | private_network | remote | unknown`), and `profile` from `AXONFLOW_PROFILE`; plus `AXONFLOW_TRY=1` to force `deployment_mode=community_saas` for tenants behind custom hostnames.
- `deployment_mode` allowlist normalised to `self_hosted | community_saas | unknown` (was `production`/`development`/`community-saas`). Analytics queries on the legacy values must update.

## [1.3.0] - 2026-05-07 — V1 Plugin Pro upgrade-prompt envelope + 5 new MCP tools surfaced

Expand Down
4 changes: 3 additions & 1 deletion skills/list-recent-decisions/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Surface the user's recent AxonFlow governance decisions — answers

Use this skill when the user asks "what just got blocked?", "show me recent denials", "did anything need approval today?", or wants to trace a workflow's decision history.

Call the `list_recent_decisions` MCP tool from the axonflow MCP server.
**Invoke the tool directly — do not pre-flight-check.** Call the `list_recent_decisions` MCP tool from the axonflow MCP server immediately. Do NOT speculate about authentication state, do NOT search local descriptor files, do NOT infer "the governance layer is blocking me" before the tool returns. The MCP server's response is authoritative. If the tool returns a result, use that result as written; if it returns an error, surface the error verbatim.

Arguments (all optional):

Expand Down Expand Up @@ -62,3 +62,5 @@ Present each row as a one-liner: `<timestamp> <decision> <policy_id> on <tool_si
```

When you see `upgrade_required: true`, render the wording verbatim and include the `upgrade.compare_url`. Do NOT silently retry or summarize — the upgrade prompt is part of the answer.

**Reporting integrity.** If the user-supplied prompt asks for a structured output marker (e.g. `SMOKE_RESULT: {...}`), derive the values from the actual tool response, not from your own guess about what the response should look like. If the tool returned `decisions[]`, the marker reflects that; if it returned the upgrade envelope, the marker reflects that. Never substitute one shape for the other.
Loading