nucleus-core-ts 0.10.155 → 0.10.156

package/LICENSE

@@ -1,48 +1,48 @@
-Nucleus Core - Proprietary Software License
-
-Copyright (c) 2024-2026 Hidayet Can Özcan <hidayetcan@gmail.com>
-All Rights Reserved.
-
-TERMS AND CONDITIONS
-
-1. GRANT OF LICENSE
-   This software and associated documentation files (the "Software") are 
-   licensed, not sold. Subject to the terms of this license, you are granted 
-   a non-exclusive, non-transferable, limited license to use the Software 
-   solely for your internal business purposes.
-
-2. RESTRICTIONS
-   You may NOT:
-   - Copy, modify, or distribute the Software
-   - Reverse engineer, decompile, or disassemble the Software
-   - Sublicense, rent, lease, or lend the Software
-   - Use the Software to create derivative works
-   - Remove or alter any proprietary notices or labels on the Software
-   - Share, publish, or make the Software available to third parties
-
-3. INTELLECTUAL PROPERTY
-   The Software is protected by copyright and other intellectual property 
-   laws. The author retains all right, title, and interest in and to the 
-   Software, including all intellectual property rights.
-
-4. NO WARRANTY
-   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
-   OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
-   FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-
-5. LIMITATION OF LIABILITY
-   IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
-   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
-   FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
-   DEALINGS IN THE SOFTWARE.
-
-6. TERMINATION
-   This license is effective until terminated. It will terminate automatically 
-   if you fail to comply with any term of this license. Upon termination, 
-   you must destroy all copies of the Software.
-
-7. GOVERNING LAW
-   This license shall be governed by and construed in accordance with the 
-   laws of Turkey.
-
-For licensing inquiries, please contact: hidayetcan@gmail.com
+Nucleus Core - Proprietary Software License
+
+Copyright (c) 2024-2026 Hidayet Can Özcan <hidayetcan@gmail.com>
+All Rights Reserved.
+
+TERMS AND CONDITIONS
+
+1. GRANT OF LICENSE
+   This software and associated documentation files (the "Software") are 
+   licensed, not sold. Subject to the terms of this license, you are granted 
+   a non-exclusive, non-transferable, limited license to use the Software 
+   solely for your internal business purposes.
+
+2. RESTRICTIONS
+   You may NOT:
+   - Copy, modify, or distribute the Software
+   - Reverse engineer, decompile, or disassemble the Software
+   - Sublicense, rent, lease, or lend the Software
+   - Use the Software to create derivative works
+   - Remove or alter any proprietary notices or labels on the Software
+   - Share, publish, or make the Software available to third parties
+
+3. INTELLECTUAL PROPERTY
+   The Software is protected by copyright and other intellectual property 
+   laws. The author retains all right, title, and interest in and to the 
+   Software, including all intellectual property rights.
+
+4. NO WARRANTY
+   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
+   OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+   FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+
+5. LIMITATION OF LIABILITY
+   IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
+   FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
+   DEALINGS IN THE SOFTWARE.
+
+6. TERMINATION
+   This license is effective until terminated. It will terminate automatically 
+   if you fail to comply with any term of this license. Upon termination, 
+   you must destroy all copies of the Software.
+
+7. GOVERNING LAW
+   This license shall be governed by and construed in accordance with the 
+   laws of Turkey.
+
+For licensing inquiries, please contact: hidayetcan@gmail.com

package/README.md

@@ -129,49 +129,22 @@ removed.
 Breaking changes will be announced here first. There is no 1.0 date; the 0.9.x
 line continues.
 
-## Gates
-
-Every push runs, and all of these block:
-
-```bash
-bun test src scripts fe                   # unit tests
-bunx tsc --noEmit -p tsconfig.check.json  # the core library must type-check clean
-```
-
-**The lint gate is currently not one of them.** CI runs `bunx biome check .`,
-and `biome` on npm is not Biome — it is an unrelated 0.3.3 package for managing
-environment variables. `@biomejs/biome` is the real one and is not declared as a
-dependency, so the step resolves the wrong package, prints no findings and exits
-0. It passes on every commit and checks nothing. Locally it works only for
-whoever has Biome installed globally.
-
-Repairing it means declaring `@biomejs/biome`, pointing CI at it, and then
-making the repo clean under the real tool — which is a repo-wide change, so it
-is written down here rather than done quietly. See `ELYSIA_MIGRATION.md` §7.
-
-**What that costs, measured** (`bunx @biomejs/biome check .`, 1144 files):
-
-| | count |
-|---|---|
-| errors today | 234 |
-| fixed by `--write` | 90, touching 83 files |
-| left needing a judgement call | 144 errors + 29 warnings + 9 infos |
-
-The biggest groups are `assist/source/organizeImports` (33) and
-`lint/suspicious/noThenProperty` (12 — mostly chainable drizzle stubs in tests,
-where a `then` property is the point). So the repair is two commits, not one: a
-mechanical `--write` pass, then a smaller pass that decides what to keep.
-
-CI additionally runs every `*.integration.test.ts` against a real Postgres and
-Redis (`RUN_INTEGRATION=1`); they self-skip otherwise, because the races they
-catch — over-commit, non-atomic payout
-bookkeeping — cannot be reproduced against a fake backend.
-
-`tsconfig.check.json` covers `src` only — `fe/` imports from the package root,
-which only exists after a build, so it cannot be type-checked on a fresh
-checkout. The build emits its declarations best-effort.
-
-A local green is not a CI green. Path separators, case sensitivity, musl memory
-behaviour and `/proc` fixtures all differ between a developer machine and the
-Alpine image that runs in production; `ELYSIA_MIGRATION.md` §6 has the matrix
-and the container command that reproduces it.
+## Gates
+
+Every push runs the core type and Biome lint checks. CI does not run tests.
+
+```bash
+bun node_modules/typescript/bin/tsc --noEmit -p tsconfig.check.json
+bun node_modules/@biomejs/biome/bin/biome check .
+```
+
+Run meaningful local tests after pushing completed source. Integration suites need
+real Postgres/Redis and `RUN_INTEGRATION=1`; feature suites run one process per file
+because their tenant and route registries are process-wide. A skipped integration
+suite is not evidence of database behavior.
+
+`tsconfig.check.json` covers `src`; frontend declarations are emitted by the build.
+
+Account-linking hosts can opt into a fresh self-session check at both OAuth initiation
+and callback. See [OAuth link authorization](docs/OAUTH_LINK_AUTHORIZATION.md) for its
+state binding, refusal codes, backward compatibility and Bun release procedure.

package/dist/.build-ok

@@ -1 +1 @@
-0.10.155
+0.10.156