If this is implemented, it needs to be done before the wood component of #5 can be finished or risk duplicating work.

Why implement recipe inheritance for the stone sawmill?
Ease of use. Pack-dev could define wood recipes one time for the chopping block, or let the auto-generated stuff ride, instead of defining once for chopping block and again for stone sawmill. Recipes defined for the chopping block would then, by default, propagate all the way up to the brick sawmill.

However, once the wood recipe compat system is implemented and many popular modded woods are added to it, there may not be a big need for it.

Change sawblade config for stone sawmill to include a quantity for the auto-generated wood recipe outputs:

@Config.Comment({
        "Valid sawmill blades.",
        "Quantity applies to the output quantity of wooden plank and slab recipes inherited from the Chopping Block.",
        "NOTE: Items listed here are assumed to have durability.",
        "Item string format is (domain):(path);(quantity)"
    })
    public String[] SAWMILL_BLADES = {
        "pyrotech:sawmill_blade_stone;1",
        "pyrotech:sawmill_blade_flint;2",
        "pyrotech:sawmill_blade_bone;2",
        "pyrotech:sawmill_blade_iron;3",
        "pyrotech:sawmill_blade_gold;1",
        "pyrotech:sawmill_blade_diamond;4",
        "pyrotech:sawmill_blade_obsidian;3"
    };

Entries without a ;# at the end would default to a quantity of 1.

Details:

• method that validates sawblade would have to split string
• inheritance code would have to group blades by quantity to make recipes