fix logic where .reject() is invoked in a NON-backtracking lexer: previously this would create a situation, when you use a custom parseError handler which does NOT THROW an exception, where the erroneous match (i.e. a lexer rule match which is .reject()ed in the matching lexer action code block) simply be skipped (ignored): we now flag this situation by memorizing the error token that should accompany the parseError() invocation and have the lexer produce this token as soon as possible.
tweaked `make clean` target: use the dependency define for cleaning as well
fixed make dependencies and added bootstrapping actions so that the sequence `make superclean; make` will work while the 'superclean' target will kill all generated files
- completed the 'superclean --> deploy' build cycle work: following a `make superclean` all other make targets work as expected

- all files have been regenerated
added generated files again as anyone who wishes to run jison 'out of the box' needs those.
always output the lexer options struct
add support for a 'action header chunk' which is a block of code that is included at the *top* of the actionHandler. You may us$

    %{ /* this is not an 'action header chunk': this chunk is appended to the Parser class itself. */ %}
    %start begin
    %%
    %{
      /* this is the new 'action header chunk': it is included in the performAction handler. */
      /* WARNING: this chunk (or series of chunks) MUST be placed before the FIRST production/rule! */
      /*          (otherwise it would potentially be confused with a production action block) */

      var local1; // variables used in productions' actions
    %}
    begin: A
      %{
        local1 = $1; // use local var, declared in 'action header chunk'
        $$ = local1 + 'xyz';
      %}
    %%
minimal tweak to the web pages: matching the '*' stars for a bold warning, and some whitespace policing