Resolve a clone chain into the effective journey (what the patient actually gets, and when), build a new pathway as deltas, and QA it — all read-only, in your browser.
A journey inherits from its clone: parent, then adds and removes activities. mrjourney walks that whole chain (expanding {{ clip }} includes), shows you the effective list each patient sees — with each activity's schedule decoded into real visible dates — and lets you build a new pathway as clean deltas and QA it. It never writes files.
Standing up a new client × procedure journey, checking why an activity does/doesn't show, sanity-checking a clone parent, or seeing exactly what a pathway calls before you push.
mr-content folder (status pill, top-right — Chrome or Edge).tkha-tkr), set the op date, hit Resolve. You get the clone chain, the effective activity list (inherited / own / overridden), each schedule's visible window, and a QA pass.addActivities/removeActivities YAML (never flattens the parent) and QAs it.span straddles the milestone (1y-2w-span-op = 1 year before → 2 weeks after op). A schedule that needs a date you haven't given (e.g. registration) shows as “needs date”, never a guess.mr-op, expanding {{ clip }} lists. If a level's YAML can't be parsed it's flagged, not silently dropped.