diff --git a/.env.example b/.env.example new file mode 100644 index 0000000..d62906f --- /dev/null +++ b/.env.example @@ -0,0 +1,24 @@ +# +# Decentra – local environment variables (example) +# +# Copy to `.env.local` (recommended) or `.env` and fill values. +# Files matching `.env*` are gitignored by default (except `.env.example`). +# +# Nuxt exposes variables prefixed with `NUXT_PUBLIC_` to the browser. +# + +# +# Optional remote debug logging (default: console-only) +# +# When empty/unset: Decentra only logs to the browser console. +# When set: Decentra will POST debug payloads to this URL. +# +# Example (Cursor debug session ingest): +# NUXT_PUBLIC_DEBUG_LOG_INGEST_URL=http://127.0.0.1:7476/ingest/ +# NUXT_PUBLIC_DEBUG_LOG_SESSION_ID= +# NUXT_PUBLIC_DEBUG_LOG_SESSION_HEADER=X-Debug-Session-Id +# +NUXT_PUBLIC_DEBUG_LOG_INGEST_URL= +NUXT_PUBLIC_DEBUG_LOG_SESSION_ID= +NUXT_PUBLIC_DEBUG_LOG_SESSION_HEADER= + diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md new file mode 100644 index 0000000..790624b --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug.md @@ -0,0 +1,54 @@ +--- +name: Bug +about: Plan and track a bug fix slice +title: "Bug: " +labels: ["type:bug"] +assignees: [] +--- + +## Goal + + +## Scope + + +## Branch +`bug/` + +## Bug Details +### Current Behavior + + +### Expected Behavior + + +### Steps to Reproduce +1. ... +2. ... +3. ... + +## Acceptance Criteria +- [ ] Root cause is identified and fixed. +- [ ] Behavior matches expected result in affected flow. +- [ ] No regression is introduced in related flow. + +## Test Checklist +### Unit +- [ ] Add or update unit tests for the bug scenario. + +### Integration +- [ ] Add or update integration tests if cross-component behavior changed. + +### E2E +- [ ] Add or update E2E coverage when user flow is affected. + +### Manual +- [ ] Reproduce bug on current main/develop baseline. +- [ ] Verify fix with same repro steps after patch. + +## Notes + diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..f7b6465 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: false +contact_links: + - name: Questions and support + url: https://github.com/mjkatgithub/Decentra/discussions + about: Please ask questions in Discussions. \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/epic.md b/.github/ISSUE_TEMPLATE/epic.md new file mode 100644 index 0000000..3b18f77 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/epic.md @@ -0,0 +1,24 @@ +--- +name: Epic +about: Group related feature issues under one milestone goal +title: "Epic: " +labels: ["type:epic"] +assignees: [] +--- + +## Goal + + +## Scope +- [ ] Feature issue 1 +- [ ] Feature issue 2 +- [ ] Feature issue 3 + +## Definition of Done +- [ ] All feature issues are created and linked as sub-issues +- [ ] All feature issues are assigned to the same milestone +- [ ] All feature issues are added to the project board +- [ ] Every feature issue has acceptance criteria and test checklist + +## Notes + diff --git a/.github/ISSUE_TEMPLATE/feature.md b/.github/ISSUE_TEMPLATE/feature.md new file mode 100644 index 0000000..b2a7c57 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature.md @@ -0,0 +1,36 @@ +--- +name: Feature +about: Plan and implement a feature slice +title: "Feature: " +labels: ["type:feature"] +assignees: [] +--- + +## Goal + + +## Scope + + +## Branch +`feature/` (Feature) + +## Acceptance Criteria +- [ ] ... +- [ ] ... +- [ ] ... + +## Test Checklist +### Unit +- [ ] ... + +### Integration +- [ ] ... + +### E2E +- [ ] ... + +## Notes + diff --git a/.github/PULL_REQUEST_TEMPLATE/default.md b/.github/PULL_REQUEST_TEMPLATE/default.md new file mode 100644 index 0000000..7fb7590 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE/default.md @@ -0,0 +1,35 @@ +## Summary + + +## Related Issue + + +## Branch Flow +- Source branch: `feature/` or `bug/` +- Target branch: `develop` + +## Scope of Changes +- [ ] Code changes are limited to the issue scope +- [ ] No unrelated refactors are included + +## Validation +### Local checks +- [ ] Unit tests pass +- [ ] Integration tests pass (if relevant) +- [ ] E2E smoke passes (if relevant) + +### Manual test +- [ ] Happy path verified +- [ ] Edge cases verified + +## Risk and Rollback +- Risk level: [ ] Low [ ] Medium [ ] High +- Rollback plan: + - Revert this PR + - Disable affected feature path if needed + +## Checklist +- [ ] Issue is linked and updated +- [ ] Acceptance criteria are met +- [ ] Test checklist in the issue is completed +- [ ] No secrets or credentials are included diff --git a/.github/PULL_REQUEST_TEMPLATE/release.md b/.github/PULL_REQUEST_TEMPLATE/release.md new file mode 100644 index 0000000..499b03b --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE/release.md @@ -0,0 +1,39 @@ +## Release Summary + + +## Branch Flow +- Source branch: `develop` +- Target branch: `master` + +## Included Work +- [ ] Milestone completed (example: Phase 3) +- [ ] Linked feature/bug PRs are merged into `develop` +- [ ] Release notes draft is prepared + +## Compatibility and Risk +- Breaking changes: [ ] No [ ] Yes (describe below) +- Migration required: [ ] No [ ] Yes (describe below) +- Risk level: [ ] Low [ ] Medium [ ] High + +### Breaking changes / migration notes + + +## Validation +### Pre-release checks +- [ ] CI pipelines passed on `develop` +- [ ] Smoke tests passed +- [ ] Critical user flows validated manually + +### Post-merge plan +- [ ] Verify production/staging health +- [ ] Monitor logs and error tracking +- [ ] Prepare rollback if required + +## Rollback Plan +- Revert release merge commit on `master` +- Hotfix from `master` if partial rollback is needed + +## Checklist +- [ ] CHANGELOG updated +- [ ] Version/tag strategy confirmed +- [ ] Stakeholder communication prepared diff --git a/.github/workflows/changelog.yml b/.github/workflows/changelog.yml new file mode 100644 index 0000000..3595406 --- /dev/null +++ b/.github/workflows/changelog.yml @@ -0,0 +1,88 @@ +name: Changelog Check + +on: + pull_request: + branches: + - develop + - master + +jobs: + changelog: + name: Changelog policy + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v4 + with: + fetch-depth: 0 + + - name: Enforce changelog policy by target branch + run: | + set -euo pipefail + + BASE_SHA="${{ github.event.pull_request.base.sha }}" + HEAD_SHA="${{ github.event.pull_request.head.sha }}" + BASE_REF="${{ github.base_ref }}" + HEAD_REF="${{ github.head_ref }}" + + if ! git diff --name-only "$BASE_SHA" "$HEAD_SHA" | \ + grep -q '^CHANGELOG.md$'; then + echo "ERROR: CHANGELOG.md was not updated." + exit 1 + fi + + extract_unreleased() { + awk ' + /^## \[Unreleased\]/ { in_section=1; next } + /^## \[/ { if (in_section) exit } + in_section { print } + ' + } + + count_entries() { + grep -E -c '^[[:space:]]*-[[:space:]]+' || true + } + + BASE_UNRELEASED="$(git show "$BASE_SHA:CHANGELOG.md" | \ + extract_unreleased)" + HEAD_UNRELEASED="$(git show "$HEAD_SHA:CHANGELOG.md" | \ + extract_unreleased)" + + BASE_COUNT="$(printf '%s\n' "$BASE_UNRELEASED" | count_entries)" + HEAD_COUNT="$(printf '%s\n' "$HEAD_UNRELEASED" | count_entries)" + + if [ "$BASE_REF" = "develop" ]; then + # Feature/Bug/etc -> develop: + # PR must add at least one Unreleased entry. + if [ "$HEAD_COUNT" -le "$BASE_COUNT" ]; then + echo "ERROR: PR into develop must add an Unreleased entry." + echo "Base Unreleased entries: $BASE_COUNT" + echo "Head Unreleased entries: $HEAD_COUNT" + exit 1 + fi + + echo "OK: Unreleased entries increased ($BASE_COUNT -> $HEAD_COUNT)." + exit 0 + fi + + if [ "$BASE_REF" = "master" ] && [ "$HEAD_REF" = "develop" ]; then + # develop -> master: + # Unreleased must be empty and a new version section must be added. + if [ "$HEAD_COUNT" -ne 0 ]; then + echo "ERROR: develop -> master requires empty Unreleased section." + echo "Current Unreleased entries: $HEAD_COUNT" + exit 1 + fi + + if ! git diff "$BASE_SHA" "$HEAD_SHA" -- CHANGELOG.md | \ + grep -E '^\+\#\# \[[0-9]+\.[0-9]+\.[0-9]+\] - '; then + echo "ERROR: No new version section found in CHANGELOG.md." + exit 1 + fi + + echo "OK: Release changelog structure is valid." + exit 0 + fi + + # For other PR routes, require changelog file change only. + echo "OK: CHANGELOG.md updated for this PR route." \ No newline at end of file diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml new file mode 100644 index 0000000..27ec440 --- /dev/null +++ b/.github/workflows/ci.yml @@ -0,0 +1,85 @@ +name: CI + +on: + push: + branches: + - develop + - master + - feature/** + pull_request: + branches: + - develop + - master + workflow_dispatch: + inputs: + run_full: + description: Run full pipeline (coverage + full E2E) + required: false + type: boolean + default: false + schedule: + - cron: '0 2 * * *' + +concurrency: + group: ci-${{ github.workflow }}-${{ github.ref }} + cancel-in-progress: true + +jobs: + fast: + name: Fast lane (unit + integration + e2e smoke) + runs-on: ubuntu-latest + if: > + (github.event_name == 'push' && github.ref != 'refs/heads/master') || + (github.event_name == 'pull_request' && github.base_ref != 'master') || + (github.event_name == 'workflow_dispatch' && inputs.run_full != true) + + steps: + - name: Checkout + uses: actions/checkout@v4 + + - name: Setup Node.js + uses: actions/setup-node@v4 + with: + node-version: 20 + cache: npm + + - name: Install dependencies + run: npm ci + + - name: Install Playwright browser and system deps + run: npx playwright install --with-deps chromium + + - name: Run fast CI lane + run: npm run test:ci:fast + + full: + name: Full lane (coverage + full e2e) + runs-on: ubuntu-latest + if: > + (github.event_name == 'push' && github.ref == 'refs/heads/master') || + (github.event_name == 'pull_request' && github.base_ref == 'master') || + github.event_name == 'schedule' || + (github.event_name == 'workflow_dispatch' && + inputs.run_full == true) + + steps: + - name: Checkout + uses: actions/checkout@v4 + + - name: Setup Node.js + uses: actions/setup-node@v4 + with: + node-version: 20 + cache: npm + + - name: Install dependencies + run: npm ci + + - name: Install Playwright browser and system deps + run: npx playwright install --with-deps chromium + + - name: Verify Docker availability + run: docker --version + + - name: Run full CI lane + run: npm run test:ci:full diff --git a/.gitignore b/.gitignore index 4a7f73a..551917e 100644 --- a/.gitignore +++ b/.gitignore @@ -17,8 +17,13 @@ logs .DS_Store .fleet .idea +coverage +coverage/ +tests/e2e/reports +tests/e2e/reports/ # Local env files .env .env.* !.env.example +!tests/e2e/.env.e2e.example diff --git a/.nuxtrc b/.nuxtrc deleted file mode 100644 index 1e1fe83..0000000 --- a/.nuxtrc +++ /dev/null @@ -1 +0,0 @@ -setups.@nuxt/test-utils="4.0.0" \ No newline at end of file diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 0000000..2d83409 --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,8 @@ +{ + "cucumberautocomplete.steps": [ + "tests/e2e/step-definitions/**/*.mjs", + "tests/e2e/support/**/*.mjs" + ], + "cucumberautocomplete.syncfeatures": "tests/e2e/features/**/*.feature", + "cucumberautocomplete.strictGherkinCompletion": true +} diff --git a/CHANGELOG.md b/CHANGELOG.md index 84dbcd3..c8c51ee 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,176 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +### Added + +- Matrix space hierarchy in the channel column: subspaces as collapsible + category headers (chevron toggle), rooms grouped under `m.space.child` + order, and a root-level "General" segment for direct space children (#5) +- Drag-and-drop reordering of category blocks and rooms (within and across + categories) with persistence via `m.space.child` / `order`, gated by + `m.room.power_levels` for `m.space.child` (no DnD when not allowed) +- `vue-draggable-plus` dependency for the space channel sidebar +- Helpers and unit tests for space category mapping, space state writes, and + hierarchy permission checks (`matrixSpaceHierarchyPermissions`) +- reCAPTCHA UIA stage (`m.login.recaptcha`) in signup with consent-gated + script load and optional iubenda hooks (#57) +- Optional Synapse-backed E2E for registration captcha (`@recaptcha_signup`); + see `tests/e2e/RECAPTCHA-SIGNUP.md` +- Dedicated GitHub Bug issue template at `.github/ISSUE_TEMPLATE/bug.md` + with `bug/` branch guidance and bug-focused planning/test sections +- MVP signup page with Matrix registration and user-facing error feedback (#52) +- Chat image messages with inline preview and lightbox support +- E2EE image sending support from chat input +- Media utilities for encrypted media fetch, decrypt, cache, and revoke flows +- Unit and integration test coverage for media utilities and image timelines +- Four-column chat layout with responsive sidebars and mobile overlays +- Space rail with compact/expanded modes and create-space stub route +- Account settings page and space settings base page +- Member list with presence badges (online, away, offline, unknown) +- Presence selector in account settings with homeserver capability check +- Theme preference composable with explicit localStorage persistence +- App i18n composable with English/German locale persistence +- SVG favicon and global head registration +- Message timeline event notices for join/leave/profile and room metadata changes +- Message replies with Matrix `m.in_reply_to` relation payload support +- Reply mode in chat composer with preview and explicit cancel action +- Message interaction bar component for hover/focus actions +- E2E env template and loader for credential-based login scenarios +- Smoke-tagged E2E scenarios and dedicated smoke test script +- GitHub Actions CI workflow with fast and full test lanes +- Synapse-backed E2E orchestration script (`test:e2e`) with startup, seeding, + execution, and teardown flow +- Local Synapse runtime scripts for env loading, server lifecycle management, + and deterministic test seeding +- Synapse Docker Compose setup under `tests/e2e/synapse` for local and CI runs +- Executable chat E2E scenarios for E2EE fallback continuity, image rendering + and lightbox behavior, plus reply and missing-origin fallback handling +- Executable chat E2E presence scenarios for standard member states + (online, away, offline) with sidebar status-dot verification +- Message reactions with add/remove support, grouped emoji counters, and + incremental live updates in timeline rendering +- Advanced reaction emoji picker with category tabs, shortcode conversion + (for example `:wave:` to `👋`), and user-scoped frequent emojis +- Additional reaction coverage in unit and E2E tests for Matrix toggle logic, + aggregation mapping, and message-level reaction UI behavior +- Session restore gating with explicit startup lifecycle state and completion + helpers in `useMatrixClient` +- Global startup loading modal shown while Matrix session restore is in progress +- Global auth middleware for protected routes with restore-aware redirect checks +- Unit coverage for restore-state transitions and global auth middleware +- Root landing page on `/` with hero content, feature cards, and a download + call-to-action placeholder +- Dedicated landing logo background assets (`logoBg.svg`) for the root route +- Unit tests for root-page restore and redirect behavior in + `tests/unit/pages/index.spec.ts` +- Onboarding panel on empty chat state with entry points for starting a + direct message, creating a group room, and exploring public rooms (#59) +- Direct message start panel with user-id input, user directory search, + and shareable `matrix.to` links for the own account and invited users +- Public room discovery panel with homeserver directory search and + distinct loading, empty, and error states +- Dedicated room creation page at `/rooms/new` for single group rooms + with visibility and topic controls +- Matrix client wrappers for direct-message lookup and reuse via + `m.direct` account data, group room creation, id/alias joining, + public room directory search, and user directory search +- Unit coverage for the new Matrix client wrappers, the room creation + page, and the `/rooms` auth middleware protection +- Matrix email sign-up (UIA): pending state in session storage, dedicated + registration helpers, two-step `/signup` with an email-confirmation step, + `/signup/verify-email` auto-finalize page, and matching i18n keys (#56) +- E2E stack: MailHog beside Synapse in `tests/e2e/synapse` Docker Compose, + optional `DECENTRA_E2E_SIGNUP_EMAIL` homeserver overrides (3pid email + + SMTP to MailHog), Cucumber scenarios tagged `@email_signup`, helper + runners to exclude that tag in default E2E, `test:e2e:signup-email` full + pipeline script, and `tests/e2e/EMAIL-SIGNUP.md` notes +- Extended Matrix signup UIA (#58): `m.login.registration_token` + (including `*.login.registration_token` ids), `m.login.terms` with + `SignupTermsStep.vue`, shortest completable email-flow selection, chained + pre-email stages on `/signup` and `/signup/verify-email` +- User-facing SSO-only registration hint (`SIGNUP_SSO_USE_WEB_CLIENT`) + and explicit SMS signup non-support (`SIGNUP_MSISDN_NOT_SUPPORTED`) + (#58) +- Additional unit coverage for registration UIA helpers and signup pages + (`matrixRegistrationUia.spec.ts`, page specs) +- Matrix delegated OIDC sign-up (MSC2965 / MAS): OpenID discovery, PKCE, + dynamic client registration, token exchange, `/auth/matrix-oidc/callback`, + and Matrix JS SDK session wiring (`matrixOidcNative.ts`, `useMatrixClient` + with persisted OIDC client and token-endpoint metadata for refresh) +- Sign-up entry point for delegated browser OAuth; runtime + `nuxt.public.siteUrl` / `matrixOidcClientId`; EN/DE i18n for callback and + error paths; README notes on HTTPS redirect requirements for matrix.org +- Account verification panel in settings with device verification (SAS) + and recovery key bootstrap for cross-signing (#69) +- Optional remote debug logging via `NUXT_PUBLIC_DEBUG_LOG_*` env vars and + `.env.example` template (#69) + +### Changed + +- Space rail (first column) lists only root spaces; nested subspaces appear + only as categories in the second channel column +- Room grouping under a selected space no longer uses `/` prefixes in room + names; ordering follows Matrix space state +- Direct message resolution now consults `m.direct` account data before + falling back to two-member heuristics for existing rooms +- Global auth middleware now also protects the `/rooms` route prefix +- Chat timeline now opens with a bounded initial message window to reduce + startup scroll depth and perceived room-load latency +- Login page now shows a post-signup success banner (#52) +- Chat history loading switched from button-based pagination to bidirectional + infinite scroll with guarded top/bottom sentinel triggers +- Initial message viewport now centers around the user's last-read event when + newer messages exist, and otherwise starts at the bottom +- Matrix attachment encryption now uses unpadded base64 for IV and hashes +- Image sending flow now checks room encryption before creating media events +- Space navigation now separates icon-button interaction from text-click area +- Room navigation supports home categories for personal/unassigned rooms +- Chat shell styling refined with distinct visual background accents +- Read receipts now show smaller avatars on each reader's last-read message +- README: CI/E2E credential setup; Matrix registration (UIA) section and + signup-related structure paths; phased roadmap bullets removed—priorities + in GitHub Issues; status line shortened +- Message list rendering was modularized with a dedicated `ChatMessageItem` + component and reusable `ChatMessageActionBar` +- Full CI lane now runs E2E against local Dockerized Synapse instead of + requiring repository Matrix credential secrets +- Default `test:e2e:run` Cucumber invocation now skips `@email_signup` + scenarios; use `test:e2e:run:email` or `test:e2e:signup-email` for the + MailHog-backed email registration path +- Synapse-specific E2E step definitions were consolidated into existing + `login.steps.mjs` and `chat.steps.mjs` +- Synapse environment validation moved from scenario-level Given setup into + hook-based prechecks for seeded-room scenarios +- Message action bar now uses icon-only reply/reaction controls with compact + gray styling and native button tooltips +- Chat page media helper logic was moved into `useChatMedia` to reduce page + size and improve composable reuse +- Root route startup behavior now waits for restore completion before login/chat + navigation decisions +- Root route now keeps restore-aware `watchEffect` gating while rendering + landing content for unauthenticated users +- Landing copy and i18n keys were aligned with the finalized Issue-41 hero and + feature text +- Landing background logo loading now uses a bundler URL import to avoid + runtime path resolution issues + +### Fixed + +- Space-to-room parent mapping now uses Matrix `m.space.parent` state +- Space avatar resolution now supports Matrix mxc avatar URLs with fallback +- Homeserver base URL normalization now upgrades public http to https to avoid + redirect-driven CORS failures in the browser (#52) +- CI install issues from unused `@nuxt/test-utils` setup were resolved +- Synapse compose configuration no longer contains duplicate `services` blocks + that broke Docker parsing +- Seeded image events now include upload-backed media URLs so image preview and + lightbox assertions can pass reliably +- Protected route redirects now avoid startup auth flicker by waiting for + session restore and sending unauthenticated users to `/` +- E2EE decryption regressions after login/session changes were fixed by + reusing remembered Matrix `device_id` for the same account and homeserver + while preventing reuse across different homeservers + ## [0.1.0] - 2025-02-13 ### Added diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..19cc6f0 --- /dev/null +++ b/LICENSE @@ -0,0 +1,661 @@ + GNU AFFERO GENERAL PUBLIC LICENSE + Version 3, 19 November 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU Affero General Public License is a free, copyleft license for +software and other kinds of works, specifically designed to ensure +cooperation with the community in the case of network server software. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +our General Public Licenses are intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + Developers that use our General Public Licenses protect your rights +with two steps: (1) assert copyright on the software, and (2) offer +you this License which gives you legal permission to copy, distribute +and/or modify the software. + + A secondary benefit of defending all users' freedom is that +improvements made in alternate versions of the program, if they +receive widespread use, become available for other developers to +incorporate. Many developers of free software are heartened and +encouraged by the resulting cooperation. However, in the case of +software used on network servers, this result may fail to come about. +The GNU General Public License permits making a modified version and +letting the public access it on a server without ever releasing its +source code to the public. + + The GNU Affero General Public License is designed specifically to +ensure that, in such cases, the modified source code becomes available +to the community. It requires the operator of a network server to +provide the source code of the modified version running there to the +users of that server. Therefore, public use of a modified version, on +a publicly accessible server, gives the public access to the source +code of the modified version. + + An older license, called the Affero General Public License and +published by Affero, was designed to accomplish similar goals. This is +a different license, not a version of the Affero GPL, but Affero has +released a new version of the Affero GPL which permits relicensing under +this license. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU Affero General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Remote Network Interaction; Use with the GNU General Public License. + + Notwithstanding any other provision of this License, if you modify the +Program, your modified version must prominently offer all users +interacting with it remotely through a computer network (if your version +supports such interaction) an opportunity to receive the Corresponding +Source of your version by providing access to the Corresponding Source +from a network server at no charge, through some standard or customary +means of facilitating copying of software. This Corresponding Source +shall include the Corresponding Source for any work covered by version 3 +of the GNU General Public License that is incorporated pursuant to the +following paragraph. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the work with which it is combined will remain governed by version +3 of the GNU General Public License. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU Affero General Public License from time to time. Such new versions +will be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU Affero General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU Affero General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU Affero General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM +IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF +SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU Affero General Public License as + published by the Free Software Foundation, either version 3 of the + License, or (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If your software can interact with users remotely through a computer +network, you should also make sure that it provides a way for users to +get its source. For example, if your program is a web application, its +interface could display a "Source" link that leads users to an archive +of the code. There are many ways you could offer source, and different +solutions will be better for different programs; see section 13 for the +specific requirements. + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU AGPL, see +. diff --git a/README.md b/README.md index d843867..965c4e9 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ Matrix-based chat client with Spaces, Categories, and Rooms. -**Status:** Alpha (v0.1.0) – MVP Phase 1. Full four-column layout follows in Phase 2. +**Status:** Alpha (v0.1.0). Priorities follow GitHub Issues for this repo. ## Tech Stack @@ -30,6 +30,22 @@ npm run dev Open [http://localhost:3000](http://localhost:3000). +### Optional debug logging (console vs. remote) + +By default, Decentra logs debug traces only to the **browser console**. +You can optionally forward those traces to a remote ingest endpoint by +setting environment variables (recommended via a local untracked file): + +```bash +cp .env.example .env.local +``` + +Then set one or more of: + +- `NUXT_PUBLIC_DEBUG_LOG_INGEST_URL` (enables remote logging) +- `NUXT_PUBLIC_DEBUG_LOG_SESSION_ID` (optional) +- `NUXT_PUBLIC_DEBUG_LOG_SESSION_HEADER` (optional, e.g. `X-Debug-Session-Id`) + ## Build & Preview ```bash @@ -49,20 +65,78 @@ npm run test:integration # E2E tests (builds app, starts server, runs Cucumber) npm run test:e2e +# E2E smoke tests only (@smoke-tagged scenarios) +npm run test:e2e:smoke + # E2E with visible browser npm run test:e2e:headed +# Coverage (currently from unit Vitest config) +npm run test:coverage + +# CI fast lane (unit + integration + e2e smoke) +npm run test:ci:fast + +# CI full lane (unit + integration + coverage + full e2e) +npm run test:ci:full + # Install Playwright browser (one-time) npm run prepare:e2e ``` +### E2E Credentials + +For credential-based E2E scenarios, create a local env file: + +```bash +cp tests/e2e/.env.e2e.example tests/e2e/.env.e2e.local +``` + +Then fill `E2E_MATRIX_USERNAME` and `E2E_MATRIX_PASSWORD`. +The local file stays untracked. + +## GitHub Actions CI + +This repo uses `.github/workflows/ci.yml` with two lanes: + +- **Fast lane:** runs on push + pull request (`test:ci:fast`). +- **Full lane:** runs nightly and optionally manual + (`test:ci:full`). + +### Required repository secrets (for full lane) + +Set these in GitHub under **Settings > Secrets and variables > Actions**: + +- `E2E_MATRIX_HOMESERVER` (optional, defaults to `https://matrix.org`) +- `E2E_MATRIX_USERNAME` +- `E2E_MATRIX_PASSWORD` + +### How to run manually + +1. Open your repository on GitHub. +2. Go to **Actions**. +3. Select workflow **CI**. +4. Click **Run workflow**. +5. Set `run_full` to `true` if you want the full lane. + +### Note on Nuxt test-utils + +`@nuxt/test-utils` is intentionally not part of the current test runtime. +In our current dependency set, it caused peer dependency conflicts in CI while +its Nuxt runtime helpers were not actively used by our tests. +We can reintroduce it later when we add dedicated Nuxt runtime integration +tests (`setupTest()`, plugin/runtime integration, Nitro route tests). + ## Project Structure ``` app/ -├── composables/useMatrixClient.ts # Matrix login, sync, rooms, messages +├── composables/useMatrixClient.ts # Login, crypto, sync, messaging +├── composables/matrix/matrixRegistrationUia.ts +│ # Email signup UIA loop ├── pages/ -│ ├── login.vue +│ ├── login.vue / signup.vue +│ ├── signup/verify-email.vue │ ├── chat.vue │ └── index.vue └── components/Chat/ @@ -71,12 +145,54 @@ app/ └── MessageInput.vue ``` -## Roadmap +## Matrix registration (UIA) + +Signup uses Matrix **User-Interactive Authentication** against +`/register`: first request may return **401** with `session`, `flows`, +and `params`; the client keeps the session and completes stages in order. + +**Delegated auth (MAS / OAuth — e.g. matrix.org)** + +If `/.well-known/matrix/client` includes `org.matrix.msc2965.authentication`, +the homeserver typically **blocks legacy `POST /register`** for web clients but +delegates new-account creation (and related flows) to a Matrix Authentication + Service (OAuth/OIDC). + +- Set **`NUXT_PUBLIC_SITE_URL`** to your app's public **`https://` origin** + **without path** (Matrix dynamic client registration rejects `http://localhost` + redirects; use an HTTPS tunnel / preview URL for local OAuth). +- Optional **`NUXT_PUBLIC_MATRIX_OIDC_CLIENT_ID`** — static OAuth client id if you + register one yourself. +- Redirect/callback **`/auth/matrix-oidc/callback`** completes the PKCE exchange, + restores the Matrix JS SDK session (`matrixOidcNative.ts`, `useMatrixClient`). + +**Supported stages today (legacy `/register` UIA)** + +| Stage | Notes | +| --- | --- | +| `m.login.email.identity` | Email verification link; continuation on `/signup/verify-email` | +| `m.login.recaptcha` | reCAPTCHA v2/v3 from homeserver params | +| `m.login.registration_token` | Opaque token; unstable ids ending in `.login.registration_token` treated the same | +| `m.login.terms` | Policy links from `params`; user accepts before continuing | +| `m.login.dummy` | Included in finalize loop when required by the server | + +**Explicit non-support** + +- **`m.login.sso`** as an in-flow stage **after `/register` already returned UIA** + (`session` + flows) — not wired in-app; where MSC2965 is advertised, prefer + the **delegated OAuth** button on the **sign-up** page instead. +- **`m.login.msisdn`** – Phone/SMS registration is not implemented; users get + a clear “not supported” message instead of failing silently. + +When several flows include email verification, Decentra picks a **shortest** +flow whose stages are all supported. -- **Phase 1 (current):** Login, Rooms, Chat, Messages -- **Phase 2:** Four-column layout (Spaces | Categories/Rooms | Chat | Members) -- **Phase 3+:** Voice, E2E encryption, Design system, Native clients +**Locations:** `matrixRegistrationUia.ts` (logic), `signup.vue` / +`signup/verify-email.vue` + `SignupTermsStep.vue` (UI). +**Regression tests:** `npm run test:unit` (see `tests/unit/composables/matrixRegistrationUia.spec.ts` +and signup page specs). ## License -[Add license here] +This project is licensed under the GNU Affero General Public License v3.0 +or later (AGPL-3.0-or-later). See `LICENSE` for details. diff --git a/app/app.vue b/app/app.vue index a0cbd02..82abbc4 100644 --- a/app/app.vue +++ b/app/app.vue @@ -1,6 +1,38 @@ + + diff --git a/app/assets/css/main.css b/app/assets/css/main.css index 7c95c6f..f53d934 100644 --- a/app/assets/css/main.css +++ b/app/assets/css/main.css @@ -1,2 +1,9 @@ @import "tailwindcss"; @import "@nuxt/ui"; + +.decentra-shell { + background-image: + radial-gradient(circle at 12% 8%, rgb(56 189 248 / 12%), transparent 40%), + radial-gradient(circle at 88% 16%, rgb(244 114 182 / 10%), transparent 35%), + linear-gradient(180deg, rgb(15 23 42 / 14%), transparent 28%); +} diff --git a/app/assets/logoBg.svg b/app/assets/logoBg.svg new file mode 100644 index 0000000..9001bea --- /dev/null +++ b/app/assets/logoBg.svg @@ -0,0 +1,77 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/app/components/Chat/MemberList.vue b/app/components/Chat/MemberList.vue new file mode 100644 index 0000000..e449bf8 --- /dev/null +++ b/app/components/Chat/MemberList.vue @@ -0,0 +1,96 @@ + + + diff --git a/app/components/Chat/MessageActionBar.vue b/app/components/Chat/MessageActionBar.vue new file mode 100644 index 0000000..ff7776b --- /dev/null +++ b/app/components/Chat/MessageActionBar.vue @@ -0,0 +1,105 @@ + + + diff --git a/app/components/Chat/MessageInput.vue b/app/components/Chat/MessageInput.vue index 9f4bd14..30543c7 100644 --- a/app/components/Chat/MessageInput.vue +++ b/app/components/Chat/MessageInput.vue @@ -1,17 +1,30 @@