skip_all plan "1..0"  [test+fix]

test/skip_all.js based on test/ok.js
store skip_all on the plan
  preserving keyset for existing tests,
  but maybe should set plan.skip_all=false ?

gave the t.* assertions some names
  so I can follow the plan

check there are no expected.comments left over

  perl -MTest::More -e 'diag("TAP emitted by Test::More $Test::More::VERSION"); plan skip_all => "Insufficient positron flux"; ok(1, "This does not happen")'
  # TAP emitted by Test::More 0.98
  1..0 # SKIP Insufficient positron flux
plan 1..0 - verify fail if an assertion follows
provide skip_reason from `1..0 # SKIP foo`

pass the reason to 'plan' handler
  store it on the plan
  error if reason & not skipping

document the 1..0 # SKIP behaviour
  link to hexten.net following from http://testanything.org/wiki/index.php/Main_Page
  example parsed output

update test/skip_all*
test the new failure
deal with TODO failures [test, fix, doc]

stash TODO assertions on .todo and don't clear .ok

not_ok_todo.js based on not_ok.js
with TAP abridged from this output,
  perl -MTest::More -e 'diag("TAP emitted by Test::More $Test::More::VERSION"); ok(1, "should be equal"); { local $TODO = "but we will fix it later"; fail("should be equivalent"); } diag("boop"); ok(1, "should be equal"); ok(1, "(unnamed assert)"); print "\n"; plan tests => 4'
  # TAP emitted by Test::More 0.98
  ok 1 - should be equal
  not ok 2 - should be equivalent # TODO but we will fix it later
  #   Failed (TODO) test 'should be equivalent'
  #   at -e line 1.
  # boop
  ok 3 - should be equal
  ok 4 - (unnamed assert)

  1..4
Merge branch 'feature/skip_all'

* feature/skip_all:
  provide skip_reason from `1..0 # SKIP foo`
  plan 1..0 - verify fail if an assertion follows
  skip_all plan "1..0"  [test+fix]
Merge branch 'feature/todo'

* feature/todo:
  deal with TODO failures [test, fix, doc]