Split out files.liw.fi scenario to its own file

This will be good for the long run, so that it's not one huge file,
but rather several small ones. Easier to manage in the source.

2 files changed, 18 insertions, 20 deletions

diff --git a/000.yarn b/000.yarn
index fd226e8..0021faa 100644
--- a/000.yarn
+++ b/000.yarn
@@ -25,23 +25,3 @@ Do this with:
 
     EXAMPLE
     yarn --env SERVER=new.example.com ...
-
-
-# files.liw.fi
-
-<http://files.liw.fi/> is where I publish various files I want to
-share with others. There are no accounts, no passwords. A tiny amount
-of privacy is available by not having directory listings and choosing
-semi-random URLs, but mostly I just don't put anything really
-sensitive there.
-
-    SCENARIO files.liw.fi
-    GIVEN server is also known as files.liw.fi
-
-    WHEN user fetches http://files.liw.fi/
-    THEN HTTP status is 200
-    AND HTTP body matches "Random files of mine"
-
-    WHEN user fetches http://files.liw.fi/private/
-    THEN HTTP status is 200
-    AND HTTP body matches "Not for you"
diff --git a/010-files.liw.fi.yarn b/010-files.liw.fi.yarn
new file mode 100644
index 0000000..4ac8702
--- /dev/null
+++ b/010-files.liw.fi.yarn
@@ -0,0 +1,18 @@
+# files.liw.fi
+
+<http://files.liw.fi/> is where I publish various files I want to
+share with others. There are no accounts, no passwords. A tiny amount
+of privacy is available by not having directory listings and choosing
+semi-random URLs, but mostly I just don't put anything really
+sensitive there.
+
+    SCENARIO files.liw.fi
+    GIVEN server is also known as files.liw.fi
+
+    WHEN user fetches http://files.liw.fi/
+    THEN HTTP status is 200
+    AND HTTP body matches "Random files of mine"
+
+    WHEN user fetches http://files.liw.fi/private/
+    THEN HTTP status is 200
+    AND HTTP body matches "Not for you"