dreampiler/kandev
1
0
Fork 0
Code Issues 43 Pull Requests Actions 6 Packages Projects Releases Wiki Activity

P31 upstream prep: accept header-only modern notifications #88

New Issue
Closed
opened 2026-10-14 16:11:07 +09:00 by dreampiler · 0 comments
dreampiler commented 2026-10-14 16:11:07 +09:00
Owner
Copy Link
Copy Source

Owner goal: move approved fork behavior into upstream and reduce the fork delta. Candidate P31, proposal.md row 93: fix(mcp): accept header-only modern notifications. Original fork source is 90dc4a0e65 / fork PR #76 / W032; this is historical fork work, not an upstream assignment. Proposal notes upstream #3404 changed mcp/server/server.go and public docs, so inspect that merged implementation and all current upstream PRs before editing. Prepare only the still-missing behavior if a header-only modern notification is currently rejected; do not duplicate work already in #3404. Design pointer: 설계색인.md:44 maps External MCP to docs/features.md §Integrations And MCP; card invariant 1 is the nearest input-boundary rule, but verify whether it governs this protocol path. Identify current files:lines, check source and compatibility contract, then make a minimal upstream-ready change with focused tests/review. No upstream GitHub write, PR creation, ledger/status edit, force push, shared-checkout write, or broad framework.

Owner goal: move approved fork behavior into upstream and reduce the fork delta. Candidate P31, proposal.md row 93: fix(mcp): accept header-only modern notifications. Original fork source is 90dc4a0e65 / fork PR #76 / W032; this is historical fork work, not an upstream assignment. Proposal notes upstream #3404 changed mcp/server/server.go and public docs, so inspect that merged implementation and all current upstream PRs before editing. Prepare only the still-missing behavior if a header-only modern notification is currently rejected; do not duplicate work already in #3404. Design pointer: 설계색인.md:44 maps External MCP to docs/features.md §Integrations And MCP; card invariant 1 is the nearest input-boundary rule, but verify whether it governs this protocol path. Identify current files:lines, check source and compatibility contract, then make a minimal upstream-ready change with focused tests/review. No upstream GitHub write, PR creation, ledger/status edit, force push, shared-checkout write, or broad framework.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dreampiler (dreampiler)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dreampiler/kandev#88
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?