Effector posts canonical body verbatim; stops doubling the marker #45
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Ting/CurryComb!45
Loading…
Reference in a new issue
No description provided.
Delete branch "tango/44-single-canonical-marker"
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?
What
classify's create branch prepended the canonicalmarkerto abody_markdownthat already embeds it — the projection'sdesired_body_markdownputs the marker on the first line. Live Slice 1 runs therefore posted canonical comments with the marker twice.body_markdownverbatim.decl_createnow mirrors the real declaration shape (marker-embedded body) instead of the marker-free"hello"that motivated the prepend.create_when_no_marker_presentasserts byte-for-byte equality and exactly one marker occurrence.Convergence properties are unchanged (marker detection still matches; reruns no-op).
Tracker repair
Deviates from the issue's stated repair only by sequencing: the 43 marker-bearing canonical comments on this tracker were deleted and re-created through the fixed effector; second pass converges to 43 no-ops. Verified live before this PR merges.
Closes #44