Credit upstream package projects

Add consistent Credits sections to the user guides for non-Laravel upstream ports that have dedicated documentation pages. Each section links to the original project and explains that the Hypervel package has been adapted for the framework architecture and coroutine runtime.

Move repeated lineage details out of the JWT, Nested Set, Permission, and Testbench introductions so attribution lives in one predictable place without interrupting the documentation flow.

Author: binaryfire

src/docs/coroutine-context.md

@@ -24,6 +24,7 @@
     - [Request Context](#request-context)
     - [Parent Coroutine Context](#parent-coroutine-context)
 - [Common Pitfalls](#common-pitfalls)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -466,3 +467,8 @@ Values set outside a coroutine are stored in the shared non-coroutine context. T
 Values stored in one coroutine are not visible inside another unless you copy them. Use `Coroutine::fork`, `go(..., copyContext: true)`, `parallel(..., copyContext: true)`, or `CoroutineContext::copyFrom(...)` when a child needs values from its parent.
 
 Objects remain shared when context is copied unless they implement `ReplicableContext`. Avoid copying mutable request-specific objects when shared changes would be unsafe.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Coroutine Context began as a port of [Hyperf Context](https://github.com/hyperf/context) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/coroutines.md

@@ -28,6 +28,7 @@
     - [Lockers](#lockers)
 - [Advanced Coroutine APIs](#advanced-coroutine-apis)
 - [Common Pitfalls](#common-pitfalls)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -824,3 +825,8 @@ Use `Coroutine::defer()` for cleanup that belongs to one coroutine. Use [`Hyperv
 Prefer the [Concurrency facade](/docs/{{version}}/concurrency) or the `parallel` helper when the parent coroutine needs results or exceptions from child coroutines. Use `go`, `co`, `Coroutine::create`, or `Concurrent` when a child may run independently and its exceptions may be reported instead of returned to the parent.
 
 Swoole can make most stream-based I/O operations yield to other coroutines while they wait. Some PHP extensions cannot be hooked and will block the entire worker process. For CPU-intensive work or extensions that cannot yield, you should run the work in a separate process.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Coroutine began as a port of [Hyperf Coroutine](https://github.com/hyperf/coroutine) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/jwt.md

@@ -24,11 +24,12 @@
 - [Guard Methods](#guard-methods)
 - [Exceptions](#exceptions)
 - [Differences From php-open-source-saver/jwt-auth](#differences-from-php-open-source-saver-jwt-auth)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
 
-Hypervel JWT provides stateless bearer token authentication using Hypervel's authentication guard system. It is based on the `php-open-source-saver/jwt-auth` package and adapted for Hypervel's long-lived Swoole workers and coroutine runtime.
+Hypervel JWT provides stateless bearer token authentication using Hypervel's authentication guard system.
 
 JWT authentication is useful when your application needs signed tokens that can be sent with API, mobile, or service-to-service requests. If you need first-party SPA session authentication or database-backed personal access tokens, consider [Sanctum](/docs/{{version}}/sanctum) instead.
 
@@ -593,7 +594,7 @@ Common exceptions include:
 <a name="differences-from-php-open-source-saver-jwt-auth"></a>
 ## Differences From php-open-source-saver/jwt-auth
 
-Hypervel JWT is based on `php-open-source-saver/jwt-auth`, but its internals are adapted for Hypervel:
+Hypervel JWT differs from `php-open-source-saver/jwt-auth` in several ways:
 
 <div class="content-list" markdown="1">
 
@@ -606,3 +607,8 @@ Hypervel JWT is based on `php-open-source-saver/jwt-auth`, but its internals are
 - The `show_black_list_exception` option is not included; JWT exceptions fail normally.
 
 </div>
+
+<a name="credits"></a>
+## Credits
+
+Hypervel JWT began as a port of [PHP Open Source Saver JWT Auth](https://github.com/PHP-Open-Source-Saver/jwt-auth) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/nested-set.md

@@ -28,6 +28,7 @@
 - [Soft Deleting Nodes](#soft-deleting-nodes)
 - [Rendering Trees](#rendering-trees)
 - [Performance](#performance)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -36,8 +37,6 @@ Hypervel's nested set package provides tools for storing hierarchical data in a
 
 Nested sets store each node with left and right boundary columns. This makes ancestor and descendant reads efficient, while inserts and moves update the affected boundary ranges.
 
-The package is based on Aimeos's maintained `laravel-nestedset` package and adapted for Hypervel's Eloquent implementation.
-
 <a name="installation"></a>
 ## Installation
 
@@ -896,3 +895,8 @@ If a model observer vetoes a mutation and it returns `false`, throw from the tra
 Concurrent writers to the same table and nested set scope must also be serialized by your application. The package does not add an implicit distributed lock or network call.
 
 The schema helpers create separate indexes for right-bound scans, left-bound scans, and parent lookups. Scope columns prefix each index, which keeps each scoped tree's reads isolated and substantially reduces ancestor, descendant, child, and sibling query work. These indexes add a bounded cost to structural writes; this favors the read-heavy workloads nested sets are designed for. Add a depth index only when your application frequently filters large trees by depth.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Nested Set began as a port of [Aimeos Laravel Nested Set](https://github.com/aimeos/laravel-nestedset) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/permission.md

@@ -57,13 +57,14 @@
 - [Performance](#performance)
 - [Exceptions](#exceptions)
 - [Differences From Spatie Laravel Permission](#differences-from-spatie-laravel-permission)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
 
 Hypervel's permission package provides role-based access control for Eloquent models. A permission represents one ability, such as `edit articles`. A role is a named group of permissions, such as `editor`. You may assign roles and permissions to users or other models, then check access by role, direct permission, or permission inherited through a role.
 
-The package is based on Spatie's `laravel-permission` package and adapted for Hypervel. It also supports denied permissions, which explicitly reject an ability even when the model receives the same permission directly or through a role.
+The package also supports denied permissions, which explicitly reject an ability even when the model receives the same permission directly or through a role.
 
 <a name="installation"></a>
 ## Installation
@@ -1514,3 +1515,8 @@ Partition registration and isolation failures use focused exceptions:
 - Hypervel adds opt-in generic row partitioning through `PermissionRegistrar::resolvePartitionUsing(...)`. It scopes model lifecycle operations, every package relation and pivot, queries, commands, cache identities, and invalidation without depending on any partition domain.
 - Hypervel's cache config uses `expiration_seconds` and separate named cache keys so role, model-role, model-permission, and assignment-token caches can be invalidated independently.
 - Undefined `permission.cache.store` values fail fast through Hypervel's cache manager instead of silently falling back to an array store.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Permission began as a port of [Spatie Laravel Permission](https://github.com/spatie/laravel-permission) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/redis.md

@@ -26,6 +26,7 @@
 - [Pub / Sub](#pubsub)
     - [Wildcard Subscriptions](#wildcard-subscriptions)
     - [Using the Subscriber](#using-the-subscriber)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -777,3 +778,8 @@ try {
 ```
 
 The subscriber supports `subscribe`, `unsubscribe`, `psubscribe`, `punsubscribe`, `ping`, `channel`, and `close` methods. It uses the selected connection's standalone, Sentinel, or Cluster topology and supports TCP, TLS, IPv4, IPv6, and Unix sockets. Message payloads are returned as the exact bytes sent by Redis, including embedded newlines and null bytes. Messages received from pattern subscriptions include the matched pattern on the message's `pattern` property.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Redis began as a port of [Hyperf Redis](https://github.com/hyperf/hyperf/tree/master/src/redis) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/saloon.md

@@ -72,6 +72,7 @@
     - [Fixtures](#fixtures)
 - [Publishing Configuration and Stubs](#publishing-configuration-and-stubs)
 - [Differences From Saloon](#differences-from-saloon)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -2026,3 +2027,8 @@ Hypervel Saloon keeps the connector, request, middleware, authentication, respon
 - The optional `xmlReader` response extension is not included. Use the built-in `xml` or `dom` methods instead.
 
 These differences remove framework-neutral adapter layers while retaining the public concepts needed to build complete integrations and reusable SDKs for Hypervel.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Saloon began as a port of [Saloon](https://github.com/saloonphp/saloon) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/sentry.md

@@ -17,6 +17,7 @@
 - [Sensitive Data](#sensitive-data)
 - [Spotlight](#spotlight)
 - [Delivery and Shutdown](#delivery-and-shutdown)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -327,3 +328,8 @@ use Swoole\Constant;
 ```
 
 Increasing these values does not change normal request latency. They only bound transport operations and graceful shutdown work.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Sentry began as a port of [Sentry Laravel](https://github.com/getsentry/sentry-laravel) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/server-processes.md

@@ -15,6 +15,7 @@
 - [Inter-Process Communication](#inter-process-communication)
     - [Sending Messages](#sending-messages)
     - [Receiving Messages](#receiving-messages)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
@@ -241,3 +242,8 @@ Values such as `false`, `null`, `0`, empty strings, and empty arrays are deliver
 
 > [!WARNING]
 > Server-process IPC uses PHP serialization, so you should only send data created by code you trust. Swoole owns the collected process handles and exported sockets, so you should not close them in application code.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Server Process began as a port of [Hyperf Process](https://github.com/hyperf/hyperf/tree/master/src/process) and has been adapted for Hypervel's framework architecture and coroutine runtime.

src/docs/testbench.md

@@ -36,13 +36,14 @@
     - [Purging the Skeleton](#purging-the-skeleton)
 - [Testing Published Files](#testing-published-files)
 - [Helpers](#helpers)
+- [Credits](#credits)
 
 <a name="introduction"></a>
 ## Introduction
 
 Testbench provides a convenient way to write feature and integration tests for Hypervel packages. It creates a small Hypervel application around your package so your tests may register service providers, publish files, define routes, run migrations, dispatch jobs, and make HTTP requests as if the package were installed in a real application.
 
-Hypervel Testbench is a port of [Orchestra Testbench](https://github.com/orchestral/testbench) adapted for Hypervel's Swoole and coroutine runtime. It also includes several package-development helpers that are commonly useful when testing generated files, command-line behavior, and Workbench applications.
+It also includes several package-development helpers that are commonly useful when testing generated files, command-line behavior, and Workbench applications.
 
 If you are building a package for Hypervel applications, you should generally use Testbench for your package's feature tests. For general package development concepts, see the [package development documentation](/docs/{{version}}/packages).
 
@@ -1163,3 +1164,8 @@ $process->mustRun();
 ```
 
 The `remote` helper reuses the active Testbench runtime skeleton so subprocesses operate on the same disposable application copy as the parent test process.
+
+<a name="credits"></a>
+## Credits
+
+Hypervel Testbench began as a port of [Orchestra Testbench Core](https://github.com/orchestral/testbench-core) and has been adapted for Hypervel's framework architecture and coroutine runtime.