This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
name: Client checks
|
||||
|
||||
on:
|
||||
push:
|
||||
pull_request:
|
||||
|
||||
jobs:
|
||||
checks:
|
||||
runs-on: debian-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- run: test -f README.md && test -f AGENTS.md && test -f .prettierrc.json
|
||||
@@ -0,0 +1,8 @@
|
||||
node_modules/
|
||||
dist/
|
||||
build/
|
||||
coverage/
|
||||
.env
|
||||
.env.*
|
||||
!.env.example
|
||||
*.AppImage
|
||||
@@ -0,0 +1,6 @@
|
||||
{
|
||||
"printWidth": 100,
|
||||
"singleQuote": true,
|
||||
"trailingComma": "all",
|
||||
"tabWidth": 2
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
nodejs 22.14.0
|
||||
@@ -0,0 +1,10 @@
|
||||
# Client Repository Rules
|
||||
|
||||
Read the parent `AGENTS.md`, `PLAN.md`, `TODO.md`, and `docs/wiki/README.md` before working.
|
||||
|
||||
- Client code only; server logic belongs in `trixie-server`.
|
||||
- Consume contracts from `trixie-api`; do not duplicate schemas.
|
||||
- Use Prettier for Svelte, JavaScript/TypeScript, JSON, YAML, and Markdown.
|
||||
- Never store passwords, tokens, or secrets in source, settings, fixtures, logs, or artifacts.
|
||||
- Do not edit the parent `PLAN.md` without explicit user permission.
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
# Contributing
|
||||
|
||||
Run formatting, linting, type checks, tests, and the AppImage build before submission. Use deterministic mocked server/API fixtures.
|
||||
|
||||
@@ -0,0 +1,10 @@
|
||||
# Trixie Linux Client
|
||||
|
||||
This directory is the home of the standalone Linux client repository.
|
||||
|
||||
The client is a Svelte-based control surface distributed as an x86-64 AppImage. It communicates with `trixie-server` through the documented versioned HTTP and authenticated WebSocket interfaces.
|
||||
|
||||
Implementation has not started. See the parent workspace's `PLAN.md`, `TODO.md`, and `AGENTS.md` before beginning work.
|
||||
|
||||
Consumes the versioned contracts from the sibling `trixie-api` repository.
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
# Security
|
||||
|
||||
Report vulnerabilities privately through the hosting instance. Never include credentials, tokens, or real user data in issues or fixtures.
|
||||
|
||||
Reference in New Issue
Block a user