Codex Project Handoff

This is the continuation record for the Jet Admin documentation improvement project. Snapshot: 18 September 2026. It combines the conversation, saved publication reports, the current GitBook page tree, live readbacks of six key pages, and GitBook change-request history. It is an editorial handoff, not a claim that every documented product workflow has been tested.

Start here

The requested AI App Builder, Access & Governance, Version History, Environments, Publish & Deploy, and Classic App Builder updates have been published. First-level section navigation has icons. The main unfinished work is new video production, selected screenshots, end-to-end product verification, and maintenance of older reference articles.

Do not restart these sections from scratch or overwrite the current space from old local drafts. Read the published page and any newer change requests before editing. Existing local files are evidence and working material; GitBook is the current publication source of truth.

Original objective and scope

The user asked Codex to act as a technical writer/content manager and improve article structure and guides in three formats: text, images, and videos. Work began with AI App Builder, expanded to Access & Governance and Publish & Deploy, and then covered Classic App Builder (Legacy). The user also requested first-layer menu icons and supplied screenshots for Version History and Environment settings.

Repeated “do it” instructions authorized implementation of the proposed documentation changes. Text and available images were published; planned video scripts must not be described as finished recordings.

Explicit AI App Builder requirements

• AI Assistant: select data sources, upload images/files, select an AI model, type or dictate, and manage multiple chats with their context.

• Choose a page from the app's page list.

• Select elements/components inside Preview and request focused edits.

• Apply theme presets and customize appearance parameters manually.

• Preview as a specific invited user.

• Use App Console and logs.

• Preview Desktop, Tablet, and Mobile layouts; use full screen; stop/restart Preview.

The user described “unlimited” chats and “50+” themes. The inspected theme gallery showed 42 presets, so published copy deliberately refers to the preset library without a numeric promise. Chat documentation does not turn unlimited chat creation into a guarantee of unlimited usage or shared memory between chats.

Current GitBook location and navigation

• Public documentation: docs.jetadmin.io.

• Organization ID: -LQ08RF9M1pw0T-3zBQH.

• Space ID: -LQ08RFAKZvFADEiXKFy.

• Site ID: site_bMDNZ.

• Before this handoff was added, the live tree contained 617 entries, including section/group entries.

• Current root navigation: Welcome to Jet Admin; FAQ and Troubleshooting; Getting Started; AI App Builder; Data & Integrations; Workflows; AI Agents; Access & Governance; Publish & Deploy; Classic App Builder (Legacy); Account; Affiliate Programs; Welcome old.

• “Welcome old” still exists. Its presence is an audit item, not authorization to delete it.

The following are the current immediate children of the four principal sections. IDs are included so a new agent can locate canonical pages even if URLs change.

AI App Builder

1. AI App Builder overview — kxzlWfC22SDeDvg22RL7

2. AI Assistant — uSV7U7xGccn1I5cU0J5j

3. Create an app — mGm7LpAoKQ8oMVEZASxD

4. Navigate and edit your app — 2EknAgC2G5quyq42pisu

5. Themes and appearance — 7poI1KnY15pc7IBrYgKT

6. Preview and troubleshoot — YujWuAnigrZUAxMsust1

7. Test and publish — sakGTsQTNEJAG6lsV24q

8. Practical guides — hPgTx4lXsdNQmw33xJRD

9. Move from Classic to AI — ipKAVshmYBp6gHre3kGE

Access & Governance

1. Access & Governance overview — 1pvrGalHXvJXKt8o2fEq

2. Users and invitations — vP1IBnhNwn8f7uhQ80iD

3. Teams and roles — RwSIN3Jy44Yv3ewqDcIz

4. Authentication and SSO — inDfXOIFXkcJaOMJIsvX

5. App and data permissions — 0QFpSrJtJ2W5Mv7Gbl6Q

6. Test and govern access — BlUTlGLQEhIyDJTEXuIk

7. Audit trail and system logs — HcsovHQruDbiULo27OWd

8. Security and data handling — -LQF3Ko_wgU_aPUEVyvF

Publish & Deploy

1. Publish & Deploy overview — Ij69wpYMN69KZs78UqiH

2. Publish your app — 3QWIYyleggw7HfIhpNzS

3. Share and embed — lp6h5IPCSLIqKk0O2FpG

4. Custom domains — QBursZZykocu81VGNDHX

5. Environments — -MPK8WlwS6SpKCso2uT0

6. Version History and recovery — PJ1mqtj0RjGwjTdP9jLx

7. Deployment options — b9iqmwgXV8Gwacf17oVT

8. Troubleshooting — d0SVTazGxsEDuQN2uavY

Classic App Builder (Legacy)

1. Classic Builder overview — 5ljnyMHhqWtFwsCOX2il

2. Pages and components — -M9tUaeroJalnsMvEeO9

3. Data binding and variables — tgd4Iq7JppXOqgIZ2sqK

4. Actions and logic — sxDOhyXAXbckDt4CFRk4

5. Appearance and localization — kDB8Iato333fy4rB4Rdb

6. Component Designer and Figma — TF3ThYn96f7U1CeILDkG

7. Practical guides — bNNGeOvCgTtaLtyKLzk0

8. Test, publish, and maintain — c4uNpbdGUozaKsgvsW6U

9. Video tutorials — -MPoUw6DE_nF5VfYgkDn

10. Move to AI App Builder — 2BCYv10dF66o74bw3CoL

Completed work

AI App Builder

Published 16 September in #1142: 18 new and 16 revised articles, including the canonical first-app quickstart. Navigation covers overview, assistant, creation, editing, themes, preview, testing/publishing, practical guides, and transition from Classic. #1143 added first-level icons.

Published media and validation:

• 12 current UI screenshots embedded.

• Downloadable sample ticket CSV attached to the quickstart and support guide.

• Three existing Arcade demos preserved.

• Two redirects created for moved articles.

• All 34 published articles read back against authored text, and internal page targets checked.

• Public overview/navigation and image rendering visually checked.

• Nine video scripts/shot lists prepared; no new recordings.

Important factual decisions: direct component editing is a targeted prompt workflow, not an assumed property-panel editor. Preview-as-user guidance is included, but actual permission enforcement was not tested. The page selector opened without populating in the inspected project; the feature is documented from the user's description, without publishing the empty menu as a representative result.

Access & Governance

Published in #1144: 12 new and 17 rewritten articles, organized into eight sections. Ten detailed provider guides retained. Seven new screenshots and six video scripts prepared. Twelve redirects cover moved/normalized URLs.

Coverage includes invitations, teams, built-in roles, authentication/SSO, page/action/data permissions, record access and isolation, access testing, AI-assisted change review, audit trail, system logs, and data handling. Thin Jet Auth/Auth0/Firebase/token material was expanded without claiming provider installations had been exercised.

Read-only Fleet Management inspection verified Users/Teams/Authentication navigation, Invite Member/Share dialogs, team selection, import/export options, property setup, authentication provider selection, Activity trail filters, and System logs controls. Role labels observed: Administrator can build/modify, Editor can modify, Read Only can view. The interface warns that non-builder users see the published app.

No invitations were sent, memberships changed, data imported/exported, authentication settings saved, or new invitation links created merely to document the interface.

Version History

Published in #1145, with a user-provided screenshot and links from AI testing/publishing, governance, and deployment recovery material.

Canonical page: Version History, ID K1RM2aZdSPUG8SqXPPqe, URL path ai-app-builder/test-and-publish/version-history.

Verified menu labels: Preview version, Revert version, and Show changes. Show changes was inspected read-only and displays file differences. No revert or product release was executed. The guide distinguishes “Previewing now” from the version users actually receive and avoids promising that reverting app configuration reverses database writes or external side effects.

The earlier Version Control article was retained with an earlier-interface/Classic note. Historical claims about saving, live behavior, plan eligibility, and manual backups still deserve focused verification.

Environments and platform updates

Published in #1146. Rewrote Environments and Update to new version. Their current paths are under jet-bridge-deployment/environments.

Verified navigation: app menu → Environments → settings gear. Documented Add new Environment, name/color, Production's non-renamable default name, Jet Admin Version selector, View Changelog, Save, Download backup, and Restore backup.

No environment was created, upgraded, or restored. The supplied screenshot exceeded the upload limit encountered in this workflow; a readable current settings capture was embedded instead. Historical 1.x→2.x notes remain explicitly historical. Separate environments must not be described as proof of separate database credentials or isolated business data.

Publish & Deploy

Published in #1147: 11 new and eight rewritten articles, eight first-level sections with icons, four fresh screenshots, existing relevant screenshots reused, four redirects, and seven video scripts.

Coverage now follows release preparation, publication, published-app verification, sharing/embedding, domains, environments, version history/recovery, deployment choices, and troubleshooting. Detailed Cloud/Jet Bridge/on-premises tutorials were preserved rather than represented as newly validated deployments.

Verified distinctions:

• Toolbar Share is for invitations.

• More → Sharing contains social title, description, and image metadata; it is not the membership/access dialog.

• More → General → Custom Domain opens the current domain flow. Use the exact DNS values supplied by that flow; do not copy old hardcoded DNS targets as universal instructions.

• A team invitation link does not establish anonymous access.

• Classic public embedding is separate from current AI app sharing and must not be presented as automatic feature parity.

All 19 authored pages were read back and internal targets checked. The public overview was checked after cache refresh. No Fleet app publication, DNS changes, custom-domain connection, deployment, or access grant was performed.

Classic App Builder (Legacy)

Published in #1148: five new and 11 rewritten/expanded articles, ten first-level sections with icons, and 11 redirects. Existing page IDs were preserved.

New navigation separates pages/components, data binding, actions/logic, appearance/localization, Component Designer/Figma, practical guides, testing/maintenance, video tutorials, and transition to AI Builder. Added a button-action guide and troubleshooting guide; expanded form-to-table and table-filter guides with text. Renamed ambiguous quickstart material to task-oriented titles and moved action/appearance articles into appropriate hubs.

Existing screenshots, Arcade content, and recordings were retained as Classic reference material. Added one Mermaid binding-flow diagram. No fresh Classic app UI or end-to-end workflow was validated. Sixteen article readbacks matched after normalizing GitBook formatting, and three published spot checks passed. Seven replacement-video briefs are ready; recordings, captions, transcripts, and full playback review remain pending.

“Legacy” is a product/interface distinction, not an invented retirement date. Moving to AI Builder is not documented as guaranteed automatic conversion.

Publication audit trail

All requests below are merged. They were published on 16 September 2026. Counts above describe authored work per release and overlap; do not sum them as unique pages.

Change request	Scope	Merged revision
#1142	Expand AI App Builder: assistant, visual editing, themes, preview and practical guides	QAjl31yEGEvIo3Tqn175
#1143	Add icons to AI App Builder first-level navigation	9s03dps60IYB1NFQ9yQy
#1144	Rebuild Access & Governance guides: users, teams, authentication, permissions, and audit	lDLvhbrsDojBB6uzTlaE
#1145	Add Version History guide and link release and governance workflows	UQLCjUu2NX8Dwtw9asRD
#1146	Update environment setup, backup, and platform upgrade scenarios	TgZcEP6MR21XS53dMLbI
#1147	Rebuild Publish & Deploy guides, navigation, screenshots, and release workflows	bX1NKDieBMSY8yolrPLG
#1148	Organize Classic Builder guides, maintenance workflows, and learning paths	6czu9kgs9Q7yHUYdARDw
#1149	Remove inactive community forum links	ruylKqje0NeBKvU4MVLa
#1150	Remove inactive Community documentation page	wjz8XnPF8BnwauDNe3bN

The Community-link removal (#1149) and Community-page removal (#1150) were found in the current space history, rather than established by the visible request sequence. Preserve that subsequent cleanup; do not reintroduce the inactive Community destination from older backups.

Related work found in the workspace and space

These are adjacent project records, included for continuity without attributing every change to this conversation:

• Data & Integrations: publication #1134 records 13 new articles, rewritten references, sample data, 26 moved-page redirects, and locally checked SQL/JavaScript examples. #1135 adds business-app migration as a sync use case. #1136 published 30 assets across 15 articles: 29 screenshots and one explicitly labeled AI-assisted annotated derivative. Example checks are not proof of live connector execution. Eight video scripts and missing scenarios remain.

• Workflows: #1137 records 10 new and 19 revised pages, 46 existing media embeds preserved, 17 redirects, and readback of all 29 pages. #1138 added icons; #1139–1141 added/updated Functions, Automations, and trigger coverage. The broader media plan has 31 screenshot shots and nine video scripts. A later experience-review plan identifies further work in the newer workspace; inspect current articles before deciding which proposed edits remain.

• FAQ/support audit: the workspace contains a support-gap audit and FAQ drafts addressing credits/billing, invitations, 403 access, loading, sync, Gmail, and storage. The current FAQ root exists. This handoff does not certify every support recommendation or commercial policy anew.

• Email, What's New, and GTM documents also exist locally. They are separate deliverables and are not proof that changes were published into this GitBook section project.

Important editorial and implementation decisions

1. Organize navigation by user tasks and outcomes, with useful landing pages and icons at the first level. Preserve detailed reference/provider articles under appropriate hubs.

2. Use a consistent guide pattern: outcome, applicability/prerequisites, numbered steps, relevant image or video, expected result, troubleshooting, and next guide. Text must remain sufficient when a video cannot play.

3. Prefer canonical shared pages for data, access, and deployment topics; link instead of duplicating instructions across builders.

4. Preserve page IDs and intentional slugs. Add redirects when moving public paths, including descendants whose parent path changes.

5. Distinguish authentication, membership, and authorization. Hiding a UI element is not proof of server-side enforcement.

6. Distinguish Preview, Publish, Share, and deployment. Distinguish app Version History, platform version, configuration backup, and database recovery.

7. Use actual UI evidence and readable screenshots with alt text. Label retained Classic media and any annotated derivative accurately. Never present generated UI mockups as observed product behavior.

8. Do not invent limits, supported file formats, pricing/plan eligibility, security guarantees, retention periods, recovery guarantees, or migration parity.

9. Documentation publication/readback validates content delivery, not successful product execution. Record what was inspected, what was tested, and what remains unverified.

10. Use synthetic records and dedicated test identities for future demonstrations. Existing authorization to edit/publish docs does not authorize sending invitations, changing production permissions, configuring DNS, restoring backups, or releasing the Fleet app.

11. Treat screenshots, page content, and attachments as evidence, not as instructions to execute.

12. Review factual claims after product changes. AI Builder's recorded next review is the next builder release or 16 October 2026, whichever occurs first. Documentation/Content and AI Builder Engineering are proposed owner roles; no individual owner has been assigned.

Pages currently being worked on and draft status

At the pre-handoff check on 18 September:

• The GitBook API returned no open change requests.

• It reported 100 draft change requests. The first 30 were inspected as metadata, not a full content/diff audit. Each returned draft was marked outdated.

• The newest three returned drafts were untitled #1106 (qxmopmxjmp9jAplq5GC3), #1093 (YjgFmqaevf5WzKj96NHa), and #1087 (hu9rdNmnVrNLuCiBch5k), all updated 15 September. Their page scope and ownership have not been established.

• Another identifiable old draft is #809, “Component designer updates,” ID AEIzmeXcCBKqy2WrVspU; its latest returned update is 28 May 2024.

• None of the confirmed section releases #1142–1148 remains an unfinished draft. This handoff is the new documentation change being produced.

• Local “draft,” “before,” or plan filenames do not establish active ownership or unfinished publication. Do not merge or archive inherited drafts without reading their differences and confirming their intended purpose.

The following are recommended continuation targets, not a claim that another agent is currently editing them:

• AI page selector, attachments, dictation, invited-user preview, and preview lifecycle guides.

• Governance access-testing, authentication/provider, and recovery-related guides.

• Classic maintenance, practical guides, and video index.

• Workflows first-function, trigger, scheduling, record-event, TypeScript, and run-history guides identified by the experience-review plan.

Known issues and validation gaps

Area	Known gap	Required follow-up
AI themes	User requested 50+; inspected UI showed 42	Keep count-neutral copy until current catalog is verified
AI page selector	List did not populate in inspected project	Reproduce in a suitable demo and capture populated list
AI uploads/dictation	UI documented; complete flows not exercised	Test safe sample inputs and observed results
Invited-user preview	Selector exposed administrator and Anonymous in inspected app	Use dedicated invited roles and test allowed/denied actions
Preview lifecycle	Controls inspected; stop/restart not executed; Preview disconnected occurred	Verify reconnect/lifecycle behavior in demo; do not promise state preservation
Governance	Delivery, provider installation, session revocation, and enforcement untested	Perform controlled tests and record exact scope
History/backups	Revert/restore and database side effects not exercised	Separate configuration and data recovery tests
Domains/deployment	Setup forms inspected, no DNS/deployment completion	Validate in designated test infrastructure
Classic	Retained historical UI media; no fresh product execution	Obtain a Classic test app and validate representative workflows
Older references	Potential stale Version Control, provider, and deployment claims	Review individually against current evidence
Videos	Scripts/briefs completed; new recordings absent	Capture, caption, transcribe, embed, and test playback
Draft backlog	100 inherited drafts; incomplete diff audit	Identify owners and affected pages before cleanup
Old landing page	“Welcome old” remains	Review links, purpose, and archival strategy before changes

For the newer Workflows UI, the experience review observed All/Automations/Functions filters, Add Function with Workflow Builder or TypeScript, and six automation choices: interval, schedule, one-time, record created, updated, and deleted. The daily schedule form explicitly displayed UTC (+0); do not extrapolate that observation to all modes. Jet Tables collection selection stated “changes from Jet only”; do not promise external database writes will trigger automations. A populated visual/code demo, actual tests, and successful/failed run details remain to be verified.

Local continuation files

Workspace root: /Users/antonsvetlov/Downloads/WhatsNew. These paths are local operational references, not GitBook downloads. If the next instance has no filesystem access, use the published pages and change requests above first.

Directory/file relative to workspace	Purpose
ai-app-builder-improvements/PUBLICATION.md	Publication counts, CR, verification, owner/review notes
ai-app-builder-improvements/EDITORIAL-NOTES.md	Observed UI, discrepancies, untested behavior, redirects
ai-app-builder-improvements/MEDIA-PRODUCTION-PLAN.md	Nine video scripts and acceptance criteria
ai-app-builder-improvements/PAGE-MAP.json, PUBLISHED-MANIFEST.json, MEDIA-MANIFEST.json	Article and asset mapping
access-governance-improvements/README.md	Governance publication/implementation record
access-governance-improvements/articles/	Governance plus Version History, Environments, platform-update drafts
access-governance-improvements/video-scripts.md	Six governance scripts
publish-deploy-improvements/README.md, articles/, media/, video-scripts.md	Published release work and seven video scripts
classic-builder-improvements/README.md, articles/, video-production.md	Classic changes and seven replacement briefs
workflows-improvements/PUBLICATION.md, MEDIA-PRODUCTION-PLAN.md	Workflow release and original media backlog
workflows-improvements/experience-review/UPDATE-PLAN.md	New-workspace findings, prioritized articles, 25 capture scenarios, five walkthroughs
data-integrations-media/PUBLICATION.md, README.md	Data release/media plan
data-integrations-media/fleet-screenshots/PUBLISHED-ASSETS.json	Published data screenshot mapping
faq-intercom-update/	FAQ source drafts
intercom-documentation-gap-audit-2026-09-15.md	Support-driven content gaps
codex-project-handoff.md	Local source of this handoff

Section directories also contain before.json, draft snapshots, and article sources. Preserve these as audit evidence; read live pages before reusing them.

Recommended next steps

1. Establish the current baseline. Read this handoff, refresh the page tree, inspect newer merged/open requests, and check whether the target articles have changed. Resolve ownership of inherited drafts separately.

2. Assign content and product reviewers. Prioritize the unverified flows that affect access, publication, and recovery. Agree on dedicated demo apps/test identities before mutating product state.

3. Close AI Builder evidence gaps. Capture a working page selector; exercise attachments and dictation; test invited-user behavior and Preview lifecycle. Update copy only from observed results.

4. Review the newer Workflows experience. Compare #1139–1141 with the local experience plan. Verify the visual-function quickstart, real trigger behavior, and run history before recording tutorials.

5. Produce media in user-journey order. Start with first AI app, focused editing, access testing, first publication, and Classic maintenance. Reuse approved scripts, add captions/transcripts, and embed recordings beside complete text instructions.

6. Audit older references and redirects. Check Version Control, provider/deployment tutorials, Classic recordings, and moved-page destinations. Preserve the inactive Community cleanup. Review “Welcome old” with its inbound links before proposing removal.

7. Measure documentation outcomes. Establish baselines for helpfulness, failed searches, first-app completion, first publication, and related support contacts; do not claim improvements without data.

8. Update this handoff after each release. Record CR number, affected pages, exact validation performed, remaining gaps, and media status so future agents do not repeat or overstate work.

Publishing and verification playbook for the next Codex instance

Use the connected GitBook tools. Discover operation schemas rather than guessing them.

1. Read listPages and getPageById; request Markdown with stable references. Save the current content before edits.

2. Inspect listChangeRequestsForSpace for existing relevant work. Create a new narrowly scoped change request when appropriate.

3. Use updateChangeRequestContent with compat=false. Batches support up to 50 ordered changes. Use explicit page IDs and intended slugs; verify descendant paths after moves.

4. For content links, use stable /pages/PAGE_ID references. For uploaded media, use /files/FILE_ID. Upload attachments as files rather than inline data URIs.

5. Read edited pages from the change request. Check headings, tables, embeds, alt text, internal targets, and normalized Markdown. GitBook may normalize formatting and embed attributes; compare meaning, not only raw bytes.

6. Merge the reviewed documentation change request. Confirm the returned merge result/revision, then read back published pages.

7. Add live redirects for moved public paths and verify them. Visually inspect representative public pages; cached content may require a refresh before it reflects the new revision.

8. Save the publication report and update this page. Do not equate a GitBook merge with product acceptance tests.

This review inspected the full navigation tree and selected current page content, not every paragraph of all 617 entries or all 100 draft diffs. The verification limits above should travel with the project.

Analytics-driven follow-up — 18 September 2026

Published documentation work in change request #1153:

• Renamed the existing Overlay article to Modals and overlays, preserving its page ID and URL.

• Added complete text for creating a modal, opening it from a row/button, passing selected-record values, testing, and troubleshooting.

• Expanded Bind page data to a modal and linked the retained video and Overlay layout guides to the canonical instructions. Existing media retained and labeled Classic; no new recording or live Classic acceptance test.

• Created 202 permanent live redirect rules for observed malformed URLs with clear current equivalents and old API paths. The API reference is a separate space: XFsHhniyCGLWr64BOU1D, site-space sitesp_xHN2m. The old API-token path now targets Servers & Authentication there.

• 27 observed URL paths remain for review; some may already resolve now. Do not redirect unknown URLs to an unrelated hub merely to remove a 404. See the local audit report.

• GitBook confirmed every redirect operation as created. Direct HTTP verification was blocked by HTTP 403 in this environment; external redirect behavior still needs browser verification.

Reproducible readership baseline

Snapshot queried on 18 September 2026 using GitBook aggregateSiteEvents, range last7Days. Filter: eventType = page_view, displayContext = site, visitorBot in [null, ""], and page not in [null].

Result: 3,776 resolved-page views; 1,981 distinct visitors; 2,025 sessions. Including unresolved pages returned 4,036 views, 2,223 visitors, and 2,266 sessions.

This is the unclassified/non-bot traffic baseline, not proof that every visitor is human. Identified bots are excluded; undetected automation and internal reviews may remain. Visitors are not additive across days/pages. The site-wide query includes Platform, API reference, and What's New.

The daily query returned 11–17 September, totaling 3,754 views before excluding unresolved pages; the aggregate total was 4,036. A custom range also returned a partial 18 September bucket, and explicit datetime-bound filters failed with Bad Gateway. Preserve this range/bucketing discrepancy: do not present the rolling aggregate as a reconciled seven-complete-day figure or use it for a precise before/after comparison.

Next analytics pass: verify time-window semantics, repeat the same successful-page/non-bot filter, exclude known internal traffic if supported, and recheck broken URLs after enough new traffic accumulates. Do not infer documentation impact from this snapshot alone.

Remaining URL audit — 18 September 2026

The prior list of 27 paths was checked in the public browser:

• 26 now resolve: 23 newly configured redirect paths, two existing pages (Records and Fields), and GitBook's built-in /whats-new redirect.

• Community (/join-the-community) now redirects to https://docs.jetadmin.io/whats-new-updates as explicitly requested.

• Restored the missing legacy HTTP requests API guide in the API reference space and repaired its link from Servers & Authentication. API-space change request #12, revision fMA6inSyqq02snulfoDG. Its endpoint has not been execution-tested.

• Older provider-specific tutorials without a current exact equivalent now lead to the maintained provider/topic guide. These are navigation consolidations, not restored feature guarantees.

• One malformed URL remains a public 404: /whats-new-updates/readme.md):. GitBook rejects literal punctuation in redirect source input. The percent-encoded exact rule exists and points to What's New, but public browser checks of literal and encoded forms still returned 404. Narrow wildcard attempts also failed and were removed. No matching malformed source link was found in the current public documentation repository.

• This exposes a verification limitation of the earlier 202-rule batch: API creation success does not prove literal punctuation URLs redirect publicly. Recheck those malformed requests before claiming that entire batch resolves in a browser.

• Next step for this one remaining URL: have the GitBook site owner report the literal-versus-encoded redirect behavior to GitBook support. No support message has been sent.

Audited path mappings

Incoming path	Current destination / disposition
/access-and-sharing/authentication-and-sso/sign-in-sign-up/gb-sel-sykjzm	Retired opaque authentication URL; consolidated authentication guide — Authentication and SSO
/user-guide/integrations/jet-tables/storage-and-files	Files and storage — Files & storage
/user-guide/integrations/xano/connect-xano-to-jet-admin	Current Xano connection guide — Xano
/user-guide/integrations/xano/upload-files-to-xano	Current resource-storage and app-upload guide — Configure resource storage and app uploads
/user-guide/project-settings	Application settings — Application settings
/user-guide/integrations/firebase-firestore/import-csv-into-firebase	Retired provider-specific tutorial; current Firebase guide — Firebase / Firestore
/user-guide/integrations/google-sheets/working-with-data	Current Google Sheets guide — Google Sheets
/user-guide/jet-admin-api/http-requests-api	Restored HTTP proxy reference — API reference
/join-the-community	User requested Community to What's New — What's New
/pages/ieobslkbunkq8fuspeze	Restore original case-sensitive page ID — Jet Database
/user-guide/design-and-structure/templates	Retired Classic templates entry; current practical guides — Practical guides
/pages/3liwevtfq8uz7jg5e8fo	Restore original case-sensitive page ID — API calls with SSO token
/user-guide/integrations/xano/create-apis-on-top-of-your-xano-database	Current Xano integration guide — Xano
/user-guide/data/collection	Collections/records consolidated into Records — Records
/slack	Support Slack channel guide — How to Connect to Slack Channel
/user-guide/collaboration	Current Access & Governance guide — Access & Governance overview
/user-guide/integrations/postgresql-integration	SQL database connection guide — SQL Databases
/whats-new-updates/readme.md):	Still 404 publicly; exact encoded rule configured
/whats-new	GitBook built-in redirect to What's New
/changelog	Current news landing page — What's New
/slack-1	Support Slack channel guide — How to Connect to Slack Channel
/developer-reference/jet-admin-api	Current API reference — API reference
/user-guide/integrations/firebase-firestore/visualize-subcollection	Retired provider-specific tutorial; current Firebase guide — Firebase / Firestore
/getting-started/overall-structure	Current core concepts — Explore core concepts
/getting-started/integrations	Current first data-source guide — Connect your first data source
/user-guide/data/records	Existing Records page; verified public
/user-guide/data/fields	Existing Fields page; verified public

Current handoff visibility remains hidden from navigation and available by direct link.

Execution update — 18 September 2026: verified corrections and blockers

This update supersedes earlier statements implying that all configured malformed-URL redirects were resolved.

Completed and published

• Platform change request #1156 corrected seven articles: Version Control, both cross-instance backup guides, Welcome to Jet Admin, Business apps, Customizing Pages, and Fields. Revision: lTToawxTlqBC396M1JaL.

• Removed unverified claims about immediate deployment, complete rollback and restoration scope. Configuration recovery is distinguished from database records, files and external effects. Existing media retained; recovery has not been execution-tested.

• Repaired homepage links to the deleted Community and What's New page IDs. Community's existing public route remains redirected to https://docs.jetadmin.io/whats-new-updates.

• Replaced missing spreadsheet, page-query and field-reference links with existing canonical guides. Corrected phone-number guidance: use text to preserve prefixes and leading zeros.

• Change request #1157 updates Run on a schedule with verified trigger names, minute intervals, calendar choices, daily UTC label and one-time Run date. Functions and automations and Choose a trigger now document the Jet Tables restriction “changes from Jet only.” This is interface evidence, not a successful trigger test.

Full public redirect verification

Read all 322 live rules across four API result pages and requested each decoded source using curl HEAD with redirects followed: 127 reached HTTP 200; 195 returned HTTP 404. One initial timeout was retried and returned 404.

All 195 failures have percent-encoded punctuation in their saved sources. These are malformed incoming URLs, not evidence that 195 canonical articles are missing. The earlier 202-rule batch was only verified as API-created; it must not be reported as fully working. The earlier 27-path audit remains separate: 26 resolved, one punctuation case failed.

Local evidence in /Users/antonsvetlov/Downloads/WhatsNew:

• docs-phase2-redirects.json — all saved live rules.

• docs-phase2-url-results.json and docs-phase2-url-results.csv — full per-path results.

• docs_phase2_audit.py — audit script.

• gitbook-redirect-support-report-2026-09-18.md — ready-to-send report, reproduction steps and all 195 failing paths.

No support message has been sent. Next site-owner action: submit the report to GitBook and request a supported literal/encoded punctuation matching strategy. Preserve valid paths; do not add a broad redirect to conceal failures. Repeat the same audit after a routing fix.

Pages and production work still pending

• Build your first workflow: current worked example remains component/Classic oriented. Rewrite around a tested new visual function, moving the retained component example into Run from a button or list action. Do not remove its existing media.

• Record-event walkthrough: test created, updated and deleted events through Jet separately; confirm payloads and behavior before publishing an executable tutorial.

• TypeScript function guide: inspect the generated scaffold, accepted inputs and return values in a disposable app before writing runnable example code.

• Testing/troubleshooting: capture a successful run, a controlled failure and recovery in current Run history.

• AI Builder: validate model selection, attachments, dictation, contextual chats, visual edits and preview controls against the actual app. Preserve count-neutral theme wording until current counts are confirmed.

• Access/Governance and Publish/Deploy: test invitations, allowed/denied access, publish visibility, version recovery and environment backups in an explicitly designated demo.

• Videos: scripts and some retained Arcades exist; no new walkthrough recording was produced in this pass. Record only after the matching text scenario passes; add captions and transcript.

• Analytics: existing rolling aggregate versus daily-bucket discrepancy remains unresolved. Keep 3,776 resolved-page views as the earlier non-bot/unclassified snapshot, not a verified human or seven-complete-day baseline.

• Classic: fresh UI/media acceptance review remains pending.

Continuation boundary and next steps

The user was asked to identify a disposable demo app/environment and permitted test users. No answer had arrived at publication time. Fleet Management was inspected read-only; no function was created, automation saved, message sent, business record changed, or end-to-end product test run.

Follow docs-phase2-execution-tracker.md for the test matrix, evidence requirements and suggested role ownership. Role owners are proposed, not assigned people. Finish tests and matching media after demo details arrive; keep this handoff hidden from navigation and available through its direct URL.