Joseph Ferano
b34d0d7d59
plan.org's hot reload section now says a signature-changing redefinition should make a new internal function version with its own trampoline: new code resolves the name to it, existing callers and stored Fn values keep the old one safely, and the session warns at every tracked caller site still on the old signature. session.ml refuses the change outright, with a reason that reads like the final answer. None of the three parts exists - no function versions, no trampolines, and no record of which source location called what - so the refusal stays, because the alternative to refusing is not the new design, it is a silent argument mismatch. What changes here is only that the code and NEXT.md now say which one it is, so the next person reads it as the stopgap it is.