README.md in tork-19.8.0

- old
+ new

@@ -3,10 +3,15 @@
       _  __/ __ \  __/ /_/
       / /_/ /_/ / / / ,\
       \__/\____/_/ /_/|_\
                  >>>------>
 
+* Package: <https://rubygems.org/gems/tork>
+* Manuals: <https://sunaku.github.io/tork>
+* Sources: <https://github.com/sunaku/tork>
+* Support: <https://github.com/sunaku/tork/issues>
+
 # _Test with fork_
 
 Tork runs your tests as they change, in parallel:
 
   1. Absorbs test execution overhead into a master process.
@@ -130,9 +135,20 @@
     echo run_test_file test/some_test.rb 4 33 21 | tork-remote tork-engine
 
 You can monitor your test processes from another terminal:
 
     watch 'pgrep -f ^tork | xargs -r ps uf'
+
+### With Bundler
+
+The `bundler` configuration helper loads a Bundler bundle into tork-master(1).
+The `default` configuration helper does this for you automatically if there is
+a `Gemfile` or `Gemfile.lock` file present in your current working directory.
+
+As a result, you don't need to add Tork to your `Gemfile` _just_ to run tests!
+Instead, installing Tork as a Ruby gem _outside_ of your bundle is sufficient.
+
+Try it: go into any bundled application and call `tork` to run its test suite.
 
 ### With MiniTest
 
 MiniTest 1.3.2 and newer contain a bug where `minitest/autorun` won't run any
 tests if someone calls `Kernel#exit` explicitly or simply loads a library