Flisk 有兩個適合週末完成的新手議題

Your first contribution to an open-source project should be small, checkable, and useful. Flisk has two open issues that fit that description. Both are documentation work, both are labelled as good first issues, and both have a way to prove the change is right.

Issue 1: document the /turn request body

The agent resource in Flisk exposes a /turn route. The docs show how to call it with an x-session-id header, but they do not show the JSON body. A newcomer cannot tell which field carries the message.

The task is to add the exact request body and one sample response, checked against a running agent. Scaffold one with flisk resource bot --type agent --stack shop --yes, start it with flisk up shop, send a real request, and write down what it accepted.

Read the issue: #2031.

Issue 2: verify the @ref syntax in the worker recipe

The worker recipe passes connection strings with @ref(postgres.DATABASE_URL) and similar values. The recipe does not say whether that form is supported in every case, or what the worker receives once it is resolved.

The task is to find where the reference is resolved in the source, then either confirm the syntax with a link to that code, or correct the recipe. A container check shows the value the worker sees.

Read the issue: #2032.

How to contribute

Sign off every commit with git commit -s. The repository's Developer Certificate of Origin check fails without it. Keep one issue to one pull request, and read the contributing guide first.

If you finish either task, say what you ran and what you saw. That note is the evidence a maintainer needs to merge quickly.