web/agent-proposals-inbox #9

Closed
opened 2026-05-09 23:24:41 +02:00 by codex · 1 comment
Collaborator

Parent: #2
Wave: 1 - Maintainer Foundation
Depends on: #8

Summary

Add a small, calm web surface for reviewing AI/agent proposals without digging through logs.

Scope

  • List pending/recent proposals for the current workspace/board.
  • Show proposal summary, actor, source, affected cards, createdAt, and current status.
  • Provide explicit accept/reject actions.
  • Ensure accept/reject writes audit events.

Non-goals

  • No autonomous proposal application.
  • No broad workflow automation UI.
  • No redesign of the whole board experience.

Acceptance Criteria

  • Piotr can see pending agent proposals in one place.
  • Accept/reject is explicit and auditable.
  • Applied proposals remain idempotent.
  • Rejected proposals remain visible as history.

Tests / Smoke

  • API contract tests for list/get/apply/reject paths.
  • Browser check for proposal list and accept/reject states.
  • Manual smoke with an Iskra-created proposal.

Rollback

Disable/hide the proposal inbox route while keeping API/audit data intact.

Owner Gates

Owner approval before enabling this on production agent write workflows.

Parent: #2 Wave: 1 - Maintainer Foundation Depends on: #8 ## Summary Add a small, calm web surface for reviewing AI/agent proposals without digging through logs. ## Scope - List pending/recent proposals for the current workspace/board. - Show proposal summary, actor, source, affected cards, createdAt, and current status. - Provide explicit accept/reject actions. - Ensure accept/reject writes audit events. ## Non-goals - No autonomous proposal application. - No broad workflow automation UI. - No redesign of the whole board experience. ## Acceptance Criteria - Piotr can see pending agent proposals in one place. - Accept/reject is explicit and auditable. - Applied proposals remain idempotent. - Rejected proposals remain visible as history. ## Tests / Smoke - API contract tests for list/get/apply/reject paths. - Browser check for proposal list and accept/reject states. - Manual smoke with an Iskra-created proposal. ## Rollback Disable/hide the proposal inbox route while keeping API/audit data intact. ## Owner Gates Owner approval before enabling this on production agent write workflows.
Author
Collaborator

Opened PR #33: #33

Implemented the web proposal inbox slice:

  • /settings/proposals
  • Agent proposals Settings tab gated by board:edit
  • status filters: pending/approved/applied/rejected/all
  • visible proposal actor/source/actions/status
  • explicit approve/reject buttons for pending proposals
  • popup feedback after audited decisions
  • fixed base Button loading/disabled behavior so decisions do not double-fire

Validation run:

  • pnpm --filter @kan/api build
  • pnpm --filter @kan/api typecheck
  • pnpm --filter @kan/mcp typecheck
  • pnpm --filter @kan/api test -- agent.test.ts integration-tests/agent.integration.test.ts
  • pnpm --filter @kan/web exec eslint src/components/Button.tsx src/components/SettingsLayout.tsx src/pages/settings/proposals.tsx src/views/settings/AgentProposalsSettings.tsx
  • pnpm exec prettier --check apps/web/src/components/SettingsLayout.tsx apps/web/src/components/Button.tsx apps/web/src/pages/settings/proposals.tsx apps/web/src/views/settings/AgentProposalsSettings.tsx
  • git diff --check
  • local browser smoke on /settings/proposals; rendered no-permission fallback without local auth/data

Known baseline: full @kan/web typecheck still fails on unrelated pre-existing web type issues; no proposal inbox errors surfaced.

Opened PR #33: https://git.pdurlej.com/pdurlej/kan-ductor/pulls/33 Implemented the web proposal inbox slice: - `/settings/proposals` - `Agent proposals` Settings tab gated by `board:edit` - status filters: pending/approved/applied/rejected/all - visible proposal actor/source/actions/status - explicit approve/reject buttons for pending proposals - popup feedback after audited decisions - fixed base `Button` loading/disabled behavior so decisions do not double-fire Validation run: - `pnpm --filter @kan/api build` - `pnpm --filter @kan/api typecheck` - `pnpm --filter @kan/mcp typecheck` - `pnpm --filter @kan/api test -- agent.test.ts integration-tests/agent.integration.test.ts` - `pnpm --filter @kan/web exec eslint src/components/Button.tsx src/components/SettingsLayout.tsx src/pages/settings/proposals.tsx src/views/settings/AgentProposalsSettings.tsx` - `pnpm exec prettier --check apps/web/src/components/SettingsLayout.tsx apps/web/src/components/Button.tsx apps/web/src/pages/settings/proposals.tsx apps/web/src/views/settings/AgentProposalsSettings.tsx` - `git diff --check` - local browser smoke on `/settings/proposals`; rendered no-permission fallback without local auth/data Known baseline: full `@kan/web typecheck` still fails on unrelated pre-existing web type issues; no proposal inbox errors surfaced.
Sign in to join this conversation.
No labels
3plus3-followup
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
analytics
api
cockpit
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
docs
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
gemini-flash
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
leviathan
mcp
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
ops
priority:p0
priority:p1
priority:p2
priority:p3
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
scout
security
size/large
size/medium
size/small
size/tiny
size/unknown
small-task
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tests
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
ui
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/kan-ductor#9
No description provided.