Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
Your project depends on another project, and the other project no longer matches what you wrote down. Here is the story. In the manifest, under requires, you declare each function you call from another project, along with the contract you expect: its parameters and what it returns. Rush does not use a pinned lockfile. Instead, every time your project loads, it compares your declared requirements with what the other project actually offers right now. If the function is gone, or its contract changed, because a parameter was added or a rule was altered, the load is refused before a single statement runs. Why? Because otherwise your call would reach a different function from the one you wrote against, and the surprise would show up deep inside your program. The first slot names the manifest, the item and the witness from the comparison. The second slot gives the repair. Imagine a peer that renamed a function. You will see exactly which requirement broke. Update your requires line, or your call, to match, and the project loads again.
Text from the Rush engine's error catalogue.