Open a TaskStream board when a project is created through the API

`taskstream: true` on POST /v1/projects also creates the project in
TaskStream, public, as the caller (their Pireon token is passed on), and
the answer carries `taskstream_key` and `taskstream_url`. The key is
`taskstream_key` or one made from the default-language slug.

The board is opened before the project is saved: if TaskStream refuses
it, nothing is created here and the reason comes back as a validation
error (502 when TaskStream does not answer). Machine tokens need the
server's own TASKSTREAM_TOKEN. Updates ignore the flag, and duplicates do
not inherit the link.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

config/services.php

@@ -35,4 +35,23 @@ return [
         ],
     ],
 
+    /*
+     | TaskStream, the collective's issue tracker. Creating a project here can
+     | open its board there too (`taskstream: true`); it is made public.
+     */
+    'taskstream' => [
+        'api_url' => env('TASKSTREAM_API_URL', 'https://api.taskstream.pireon.dev'),
+        'web_url' => env('TASKSTREAM_WEB_URL', 'https://taskstream.pireon.dev'),
+
+        /*
+         | TaskStream only understands Pireon tokens. A person signed in with
+         | one has it forwarded, so the board is theirs; a machine token means
+         | nothing there, so its requests use this one instead — a Pireon
+         | personal access token. Without it, they cannot ask for a board.
+         */
+        'token' => env('TASKSTREAM_TOKEN'),
+
+        'timeout' => (int) env('TASKSTREAM_HTTP_TIMEOUT', 10),
+    ],
+
 ];