Remove teacher conversation discussion components
This commit is contained in:
@@ -0,0 +1,60 @@
|
||||
# Task: Remove teacher agent conversation component rendering
|
||||
|
||||
## Identity
|
||||
|
||||
- Task ID: 20260928-remove-teacher-cards-ef1cf59c
|
||||
- Mode: Feature
|
||||
- Branch: codex/20260928-remove-teacher-cards-ef1cf59c-remove-teacher-cards
|
||||
- Worktree: D:\Datas\OthersProjects\.codex-worktrees\makelore\20260928-remove-teacher-cards-ef1cf59c
|
||||
- Base commit: 592920da060276fa222ce15383bc22d2dde2eb49
|
||||
- Owner: codex
|
||||
- Status: Ready for Integration
|
||||
|
||||
## Scope
|
||||
|
||||
- Remove the screenshot's teacher consultation discussion components from MakeLore: ideas, structure, flow and comparison panels, their invitations, focus controls, actions and styles.
|
||||
- Stop requesting component presentation for new ordinary questions and guided help. Preserve ordinary replies, quick suggestions, rich text, tool activity, project chat identity and historical data.
|
||||
- Renderer, its focused unit/browser/Electron regressions and README only; no Main/backend protocol or storage migration.
|
||||
|
||||
## Intent And Constraints
|
||||
|
||||
- User explicitly requested removal of component rendering and prohibited subagents without consent. No subagents were created.
|
||||
- Concurrent Task Gate passed: bundled check/start/status established this feature task, branch, absolute worktree and base with matching Git-common ownership. Primary main has unrelated untracked records and remained unchanged.
|
||||
- Project Context Loaded: read-before-planning, own task, memory-index, project-positioning, current-state, decision-index, system-overview, business-rules, success-criteria and ADR-2026-09-22-coding-teacher; AGENTS.md and README supplement generic positioning placeholders. Current product is project-scoped ongoing agent chat; Main owns execution, history and read tools.
|
||||
- Read all 132 peer task records' available Scope, Intent And Constraints and Promotion Candidates. Historical placeholder scopes remain unknown; related consultation/rendering work is integrated. Independent proactive observer work remains separate and does not require the removed component UI. No concrete semantic dependency blocks this task.
|
||||
- Planning Gate Passed before edits. The explicit user request supersedes the old component-rendering behavior; canonical memory remains unchanged in feature mode.
|
||||
- Original workspace was Works Square; matching visible labels were found only in MakeLore TeacherDiscussionPanel and TeacherChatPanel. Companion server task records that routing finding without product edits.
|
||||
- An uncertain pre-upgrade request retries its original ID and full payload, including old presentation fields. New requests omit presentation/discussion. This preserves existing replay semantics and prevents duplicate model execution.
|
||||
|
||||
## Outcome
|
||||
|
||||
- Deleted TeacherDiscussionPanel.tsx and teacher-discussion.css, plus the panel mount, focus selection, state transitions and component API calls from TeacherChatPanel.
|
||||
- Ordinary new questions and guided help use the existing non-component path. Old active/offered discussion state no longer hides suggested follow-up questions.
|
||||
- Input stays fixed using shrink-0 after removal of its former CSS rule. Existing replies, failure originals, tool activity and all Main-owned history remain intact.
|
||||
- Updated README and existing tests/fixtures to describe and verify the final behavior.
|
||||
- No merge, push, packaged installation, deployment or paid model call performed.
|
||||
|
||||
## Verification
|
||||
|
||||
- pnpm 10.33.4 matches packageManager. Reused the primary checkout's existing dependencies through a local node_modules junction; no lockfile/dependency change.
|
||||
- 47 tests passed: coding-teacher-ui.test.tsx and teacher-conversation-panel.test.tsx. Detects hidden old cards reappearing, new component request metadata, lost uncertain-request identity, broken cancellation/drafts and project conversation regressions.
|
||||
- pnpm run typecheck passed; scoped ESLint passed for all changed TS/TSX files.
|
||||
- pnpm run build:vite passed for Renderer/Main/Preload/utility. Existing bundle size, mixed-import and old Browserslist warnings remain.
|
||||
- 12 Edge browser tests passed: 319px/508px ordinary and all four historical component kinds, plus Markdown/table/code/image/math layouts. Captured comparison screenshot was inspected: no component panel and composer remains visible. Vite reported KaTeX fonts outside its allow list because dependencies are reused across the worktree; mathematical DOM rendering passed, but this fixture run is not custom-font verification.
|
||||
- 1 Electron scenario passed: project consultations preserve student drafts and switch between work/chat; ordinary/guided/suggestion messages have no new presentation/discussion metadata.
|
||||
- Tests use deterministic API responses, not live provider calls. Task-aware documentation drift check passed.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- Integrate the client branch when requested; installed applications need an updated client build.
|
||||
- Independent proactive-observer integration must retain this component-free consultation display.
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- Target: coding-teacher ADR, system-overview and teacher behavior in current-state/business-rules.
|
||||
- Proposal: replace the pinned discussion component UI contract with ordinary conversation; new questions and guided help omit discussion-v1, while existing structured histories and uncertain request recovery retain their original data.
|
||||
- Evidence: explicit user screenshot request, Renderer deletion and passing unit/browser/Electron checks.
|
||||
- Future impact: future consultation UI or observer work must not restore those components incidentally.
|
||||
- Semantic conflict: intentionally supersedes the previously accepted visible component workflow; user has authorized this change. Canonical reconciliation belongs to a later Integration Gate, with no further product clarification required.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user