docs: Add multiuser documentation and reposition Workflows

[lstein]

Summary

This PR migrates the multiuser documentation from docs-old into the new astro docs directory. It also moves the Workflows section into Features, which seems to be a more appropriate place for it than at the top level.

For convenience, this PR also updates the make docs Makefile target.

Related Issues / Discussions

QA Instructions

1. make docs will fire up astro
2. Browse the reorganized Features section.
3. Check for broken images and links.

Merge Plan

Simple merge.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

[joshistoast]

Good overall add, but needs some updates.

Notes:

• I added some quick suggestions for reordering to keep the non subgrouped docs links at the top of the respective parent group.

• Lots of areas where the <Steps> component can be used for those instructional step-by-step ordered lists.

• I think we should move the spec to the corresponding invoke dir as a feature readme, as opposed to being a docs page.

• Found a couple broken links and left the fix suggestions.

• The multi user docs leaves a lot of "not right now, but in the future for sure" promises, maybe it'd be better to just say "Not at this time, create an issue if this is important to you" verbiage?

• There seemed to be an instance or two of inconsistency between existence of a feature. For example the user vs administrative docs seem to have different opinions on the existence of a user management webui. And there is also documentation now of a board having a desciption- which unless I'm mistaken doesn't exist.

• I can have my LLM do another pass over this to see if I missed anything, but this was everything I found initially.

[lstein]

Thanks for the thorough review. There was a lot more cruft in the docs than I realized. I've implemented all the suggested changes and removed redundant and out-of-date content. Let me know if I missed anything.

[joshistoast]

PR remains inconsistent with real behavior. Features that don't exist, incorrect endpoints, inaccurate and conflicting feature behaviors, etc.

Also we should document GET /api/v1/auth/status

[joshistoast]

Returns a plain array, no pagination

[lstein]

Fixed.

[joshistoast]

Shape needs to be:

[
  {
    "user_id": "string",
    "email": "string",
    "display_name": "string",
    "is_admin": false,
    "is_active": true,
    "created_at": "2026-05-07T21:12:09.008Z",
    "updated_at": "2026-05-07T21:12:09.008Z",
    "last_login_at": "2026-05-07T21:12:09.008Z"
  }
]

Returns a plain array without items

[joshistoast]

this

[lstein]

Fixed for real this time.

[joshistoast]

Found a few more things, clarified another thing. We're getting closer.

[joshistoast]

Shape needs to be:

[
  {
    "user_id": "string",
    "email": "string",
    "display_name": "string",
    "is_admin": false,
    "is_active": true,
    "created_at": "2026-05-07T21:12:09.008Z",
    "updated_at": "2026-05-07T21:12:09.008Z",
    "last_login_at": "2026-05-07T21:12:09.008Z"
  }
]

Returns a plain array without items

[joshistoast]

Suggested change

	# Session configuration (multi-user mode only)
	jwt_secret_key: "your-secret-key-here" # Auto-generated if not specified
	jwt_token_expiry_hours: 24 # Default session timeout
	jwt_remember_me_days: 7 # "Remember me" duration
	# Optional password policy
	strict_password_checking: true # Enforce uppercase/lowercase/number requirements

[lstein]

Fixed.

[joshistoast]

These seem to still be present

[lstein]

They should be gone for good.

[joshistoast]

Almost there, found a few more discrepancies, and some were even from my own suggestions (left suggested fixes for those). Clarified what happens to boards on multiuser switching edge cases, a typo here or there, and highlighted some api response docs

[joshistoast]

this

[joshistoast]

On success it returns a 204 No Content not a json with status. If there's an error the response is 422 with json:

{
  "detail": [
    {
      "loc": [
        "string",
        0
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

[lstein]

Thanks for picking that one up. Fixed.

[joshistoast]

Suggested change

	#### List One Boards
	#### Get One Board

[lstein]

Fixed