Skip to content

Scope ambient policy to supported surfaces - #1042

Open
time-attack wants to merge 1 commit into
yc-software:mainfrom
time-attack:fix/web-project-ambient-applicability
Open

Scope ambient policy to supported surfaces#1042
time-attack wants to merge 1 commit into
yc-software:mainfrom
time-attack:fix/web-project-ambient-applicability

Conversation

@time-attack

@time-attack time-attack commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • keep web-project standing orders available for addressed turns while removing unsupported ambient/bot controls from member and admin editors
  • derive policy applicability on the server and enforce it consistently across member, admin, and agent-facing writes
  • reject unsupported web-project ambientEnabled/bots fields atomically without deleting legacy values or history
  • make web-project tool guidance and the composed autonomous-mode prompt explicitly addressed-only while preserving Slack autonomous behavior

Fixes #317.

Test plan

  • prompt/resolution/orchestrator suites: 190 passed
  • policy/project/auth/core suites: 382 passed
  • web UI suites: 32 passed
  • admin plugin suites: 114 passed
  • root, web UI, admin, CLI, and contract typechecks
  • targeted ESLint, Oxlint, Prettier, and git diff --check

The tests cover orders-only save/read and prompt use, atomic rejection, legacy preservation, stale UI responses, full composed prompt semantics, and Slack channel/group-DM controls.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ambient policy can be saved on a web project but is never read

1 participant