Skip to content

feat(phase22): add durable attention foundation - #21

Draft
SuperLogicAI wants to merge 1 commit into
mainfrom
feat/phase22-attention-foundation
Draft

feat(phase22): add durable attention foundation#21
SuperLogicAI wants to merge 1 commit into
mainfrom
feat/phase22-attention-foundation

Conversation

@SuperLogicAI

Copy link
Copy Markdown
Owner

Summary

  • add the durable, provider-neutral source context needed by the future cross-project Attention inbox
  • persist accepted lifecycle observations alongside their deduplicated raw hook events
  • retain session, tab, adapter, and actor identity on new blockers, decisions, and result lifecycle events
  • prevent subagent terminal events from driving parent state or landing parent results
  • mark trusted OpenCode and Antigravity adapter traffic without inferring unknown providers
  • add focused attention-state and terminal-result characterization checks

Scope

This is the Phase 22 foundation only. It does not add the Attention palette or rail, ranking, pin/snooze behavior, shared inbox queries, provider transcript expansion, or autonomous terminal input.

Phase 22 is not yet accepted. This PR is intentionally a draft so the implemented and verified work can be reviewed while one provider-specific manual check remains unavailable.

Verification

  • npx tsc --noEmit
  • npm run check (all 18 registered check scripts)
  • npm run build
  • cd src-tauri && cargo test --lib (57 passed)
  • cd src-tauri && cargo clippy --all-targets -- -D warnings
  • git diff --check

The production build retains the existing Vite warning for a JavaScript chunk larger than 500 kB; the build exits successfully.

Manual Phase 22 checks passed for:

  • same-project blocker isolation and project-level manual blockers
  • decision source context surviving an active-tab switch during extraction
  • Codex and OpenCode adapter identity, with unmarked traffic remaining unknown
  • late/subagent terminal events not reviving or landing a parent result
  • database-write failure remaining fail-open for terminal use

Remaining Before Acceptance

  • repeat the adapter-marker check in a real Antigravity session when the weekly Antigravity limit resets

This remaining check is recorded in docs/TESTING.md and is required before PHASE 22 ACCEPTED.

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.

1 participant