Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- 2026-04-25 기준의 새 reverse-sync replacement plan을 작성합니다. - 기존 3월 phase/cleanup/review 계획 문서에 superseded 안내를 추가합니다. - capability registry, planner/strategy/proof 분리, verifier taxonomy 재정의를 중심으로 새 계획을 정리합니다. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
e86c83d to
432283b
Compare
- replacement plan을 현재 기준의 주 문서로 명시합니다 - planner/strategy/proof, table verifier normalization, pages.yaml 역할 합의를 반영합니다 - verifier taxonomy를 Accept/Review/Block/Error 기준으로 구체화합니다 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
replacement plan에 visible segment 기반 planner 방향을 명시합니다. text-bearing block은 MDX visible model에서 edit sequence를 도출한 뒤, XHTML node edit operation으로 lowering하는 구조를 목표 아키텍처에 추가합니다. 또한 planner 출력, strategy 분리, paragraph/heading 확장, contract/strategy 테스트 계획까지 함께 보강합니다. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
replacement plan에 visible segment planner 기준의 구체적 코드 분해안을 추가합니다. planner/lowering/strategy 모듈 분리, 초기 함수 시그니처, 테스트 파일 배치안을 문서화해 구현 착수 전 책임 경계를 더 명확히 정리합니다. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
요약
이번 PR에서 합의/반영된 핵심 방향
pages.yaml는 reverse-sync 관점에서 reference metadata catalog로 유지합니다.visible segment -> edit sequence -> XHTML node operation흐름을 목표 설계로 채택하되, apply 계층은 기존 patch/DOM/sidecar 체계를 유지합니다.핵심 변경
confluence-mdx/docs/plans/2026-04-25-reverse-sync-replacement-plan.md초기 코드 분해 초안
confluence-mdx/bin/reverse_sync/planner_types.pyconfluence-mdx/bin/reverse_sync/visible_planner.pyconfluence-mdx/bin/reverse_sync/node_operations.pyconfluence-mdx/bin/reverse_sync/operation_lowering.pyconfluence-mdx/bin/reverse_sync/strategy_dispatcher.pyconfluence-mdx/bin/reverse_sync/strategies/{list,text_block,preserved_anchor,container,table}_strategy.py리뷰 포인트
VisibleEditSequence를 planner의 표준 산출물로 두는 방향이 적절한지visible segment -> edit sequence -> XHTML node operation흐름을 paragraph / heading / list의 공통 planning 언어로 삼는 것이 적절한지검증