When the master-child Track pattern is in play (one Master Trackfile + N Phase children + a long-lived master branch like `track-session-manager`), the canonical checkout MUST stay on `main` so the operator has a stable read-only inspection point. Use a dedicated worktree for the master branch — eve
When the master-child Track pattern is in play (one Master Trackfile + N Phase children + a long-lived master branch like `track-session-manager`), the canonical checkout MUST stay on `main` so the operator has a stable read-only inspection point. Use a dedicated worktree for the master branch — every Phase merge, every Master Trackfile update (Children list, Child progress, Files-likely-affected)
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.