In `@app/init/models.php`:
- Around line 27-31: The import statements for the attribute models are not
sorted to PSR-12 order; reorder the use statements for AttributeLongtext,
AttributeMediumtext, AttributeText, AttributeURL, and AttributeVarchar (and the
similar block containing the same symbols around the second occurrence) into
canonical alphabetical order (or run Pint) so the imports are consistently
ordered and the linter passes.

In
`@src/Appwrite/Platform/Modules/Databases/Http/Databases/Collections/Attributes/Varchar/Create.php`:
- Line 65: Update the parameter description for the size option in the Create
endpoint: locate the param call that defines 'size' (the ->param('size', null,
new Range(1, 16381, Validator::TYPE_INTEGER), '...') invocation) and change the
human-readable string to reference "varchar attributes" (or "varchar attribute")
instead of "text attributes" so the description correctly reads that the size is
for varchar attributes and states the maximum of 16381 characters.

In `@src/Appwrite/Platform/Modules/Databases/Services/Registry/Legacy.php`:
- Around line 31-40: The added use statements for CreateTextAttribute,
UpdateTextAttribute, CreateURLAttribute, UpdateURLAttribute,
CreateVarcharAttribute, UpdateVarcharAttribute, CreateMediumtextAttribute,
UpdateMediumtextAttribute, CreateLongtextAttribute, and UpdateLongtextAttribute
need to be alphabetically ordered to satisfy PSR-12 ordered_imports; open
Legacy.php and reorder those use lines (and any nearby use imports) so they are
in ascending alphabetical order by full import string (or simply run
./vendor/bin/pint to auto-fix), ensuring symbols like CreateLongtextAttribute,
CreateMediumtextAttribute, CreateTextAttribute, CreateURLAttribute,
CreateVarcharAttribute and their corresponding Update* imports appear in the
correct alphabetical sequence.

In `@src/Appwrite/Platform/Modules/Databases/Services/Registry/TablesDB.php`:
- Around line 34-43: Reorder the import statements so they satisfy PSR-12
ordered_imports: alphabetize the added column class imports (CreateLongtext,
CreateMediumtext, CreateText, CreateURL, CreateVarchar, UpdateLongtext,
UpdateMediumtext, UpdateText, UpdateURL, UpdateVarchar) among the existing use
statements in TablesDB.php; you can either manually sort those use lines or run
./vendor/bin/pint to auto-fix the import ordering.

In `@tests/e2e/Services/Databases/Legacy/DatabasesStringTypesTest.php`:
- Around line 170-252: The duplicate-key assertion in
testCreateVarcharAttributeFailures assumes an attribute named 'varchar_field'
exists; modify the test so it explicitly depends on or creates that attribute
first: either add a dependency annotation to require the test/method that
creates the 'varchar_field' attribute (or collection attribute creation test) or
insert a setup step inside testCreateVarcharAttributeFailures that calls the
same API to create 'varchar_field' (expecting 201) before issuing the duplicate
create (expecting 409); reference the test name
testCreateVarcharAttributeFailures and the POST endpoint used to create varchar
attributes to locate where to add the dependency or setup call.

In `@tests/e2e/Services/Databases/TablesDB/DatabasesStringTypesTest.php`:
- Around line 461-462: Replace the fixed sleep(3) and sleep(2) calls with
polling using assertEventually() from the Async trait: for the "Wait for columns
to be created" case (where sleep(3) is used) wrap the condition that verifies
the columns exist in assertEventually() with a sensible timeout and poll
interval; do the same for the other sleep(2) instance—replace it with
assertEventually() checking the exact expected state instead of a fixed delay.
Use the existing assertEventually() helper and the same condition expressions
used after each sleep to determine success, and tune timeout/interval to match
CI reliability.

In `@tests/e2e/Services/Databases/Legacy/DatabasesStringTypesTest.php`:
- Around line 755-776: The test method testDeleteStringTypeAttributes attempts
to delete an attribute named varchar_max which is never created, causing the
delete to return 404; update the test to target an existing attribute (for
example change the DELETE and subsequent GET paths from 'varchar_max' to
'varchar_renamed') or reintroduce creation of a safe-size attribute named
'varchar_max' earlier in the test setup so that the calls in
testDeleteStringTypeAttributes operate on a real attribute; adjust the
Client::METHOD_DELETE and Client::METHOD_GET calls in
testDeleteStringTypeAttributes accordingly to match the chosen attribute name.

In `@tests/e2e/Services/Databases/TablesDB/DatabasesStringTypesTest.php`:
- Around line 755-776: The testDeleteStringTypeColumns method is deleting a
non-existent column varchar_max; update the test to target an existing column or
create the column first: either change the DELETE and subsequent GET requests to
use the existing column name varchar_renamed, or insert a safe creation step for
varchar_max earlier in testDeleteStringTypeColumns (or shared setup) so
varchar_max exists before attempting deletion; ensure the assertions remain
checking for 204 on delete and 404 on subsequent GET.
- Around line 153-238: The duplicate-key assertion in
testCreateVarcharColumnFailures uses 'varchar_field' which is created in
testCreateVarcharColumn but this test only depends on testCreateTable; update
testCreateVarcharColumnFailures to depend on testCreateVarcharColumn (add
"@depends testCreateVarcharColumn") or alternatively create the 'varchar_field'
column inline before the duplicate-key check so the duplicate constraint is
guaranteed; locate the test method testCreateVarcharColumnFailures and add the
dependency or inline column creation around the duplicate-key section
referencing 'varchar_field'.

In `@composer.json`:
- Line 55: Replace the unstable alias dependency entry for utopia-php/database
in composer.json ("utopia-php/database": "dev-feat-string-types as 4.7") with
the stable released constraint that contains string-types support: change it to
"utopia-php/database": "^4.6" (remove the dev branch alias and use the released
version); update composer.lock by running composer update afterward to ensure
the lockfile and installed packages reflect the stable v4.6+ release.

In `@tests/e2e/Services/Databases/Legacy/DatabasesStringTypesTest.php`:
- Around line 573-576: The `@depends` on testUpdateLongtextAttribute in the
testCreateDocumentWithStringTypes method causes this test to be skipped whenever
updates are skipped; change the dependency to the last create-phase test instead
so create/GET/delete coverage still runs (e.g. replace `@depends`
testUpdateLongtextAttribute with `@depends` testCreateLongtextAttribute or the
actual final create test in the file), updating the docstring on
testCreateDocumentWithStringTypes accordingly; ensure you keep the method name
testCreateDocumentWithStringTypes and only modify the `@depends` annotation.
- Around line 626-654: The test testCreateDocumentWithDefaultValues assumes
downstream "update" steps ran and asserts updated defaults; instead make the
assertions validate the create-time defaults so the test is decoupled from
skipped updates: in testCreateDocumentWithDefaultValues update the checks
against document['body']['varchar_with_default'] and
document['body']['text_with_default'] to expect the collection's original
default values (or derive them from the collection/schema fixture/constants)
rather than "updated default" / "Updated text default value", or alternatively
fetch the collection schema defaults dynamically and assert those values.

In `@tests/e2e/Services/Databases/TablesDB/DatabasesStringTypesTest.php`:
- Around line 576-579: The downstream tests are skipping because they depend on
testUpdateLongtextColumn; change those dependencies to depend on the last create
test instead so create/GET/delete coverage still runs when updates are skipped:
locate tests that have a `@depends` annotation referencing
testUpdateLongtextColumn (and any tests that list it in their signature) and
replace that dependency with testCreateRowWithStringTypes (the last create
test), updating method signatures and `@depends` docblocks accordingly so they no
longer transitively skip when update tests are skipped.
- Around line 626-654: The test testCreateRowWithDefaultValues currently asserts
for "updated" defaults but relies on previous skipped update tests; change it to
be deterministic by either (a) asserting the create-time default values defined
in the table schema for the fields varchar_with_default and text_with_default
instead of "updated default"/"Updated text default value", or (b) explicitly
provide values for varchar_with_default and text_with_default in the POST
payload's 'data' so the test does not depend on prior update runs; update the
assertions in testCreateRowWithDefaultValues accordingly.

In
`@src/Appwrite/Platform/Modules/Databases/Http/TablesDB/Tables/Columns/String/Create.php`:
- Line 7: Update the deprecation metadata for the string column creator: change
the replaceWith value from "createTextAttribute" to "createTextColumn" so it
points at the correct TablesDB API; locate the deprecation declaration in the
Create class for string columns (look for the Deprecated metadata and the
replaceWith property currently set to createTextAttribute) and set it to
"tablesDB.createTextColumn" (consistent with Text/Create.php and other tablesDB
creators).

In
`@src/Appwrite/Platform/Modules/Databases/Http/TablesDB/Tables/Columns/String/Update.php`:
- Around line 56-59: The Deprecated annotation in
Tables/Columns/String/Update.php uses since: '1.8.0' which is inconsistent with
the paired String/Create.php deprecation; update the Deprecated(...) invocation
in the Update endpoint to use since: '1.9.0' so both String column create and
update endpoints share the same deprecation version (keep replaceWith:
'tablesDB.updateTextColumn' unchanged).