This is a problem in Forge since the scaffold provider attempts to read the target directory value when deciding to activate the scaffold facet. Due to some synchronization issue, the configuration value read by the AngularJS provider is out of date, thus preventing the provider from detecting a recently installed scaffold. Forge thus detects that the AngularJS scaffold facet is not (yet) active and thus does not allow execution of the scaffold-x from command.

This problem doesn't manifest when the commands are run manually via copy+paste, since the time window appears to be large enough to ensure that the scaffold-x from command can be activated.