@xbibzlibrary/telebibz 0.1.9 → 0.1.11

package/docs/API.id.md

@@ -6,7 +6,7 @@
 
 Dokumen ini adalah referensi API untuk `@xbibzlibrary/telebibz@0.1.4`. Seluruh signature dan perilaku yang dijelaskan di sini dipetakan dari source TypeScript yang diekspor package. Jika suatu tipe Telegram belum memiliki pemetaan parameter/result khusus, package tetap menyediakan akses runtime melalui API dinamis, tetapi tipe parameternya masih generik.
 
-> **Status implementasi.** Dokumentasi ini menjelaskan kemampuan yang tersedia pada rilis saat ini. `JsonFileStorage`, storage Redis/SQL/Mongo berbasis driver, session/conversation berbasis Storage, cron lima field lengkap, `MenuController`, approval message branded, structured logging dengan redaction, validasi Web App, `PaymentsClient`, dan declaration `TelegramTypes` sudah tersedia. Core method map tetap khusus untuk inferensi request/result tertentu, sedangkan `api.raw()` tersedia untuk method Telegram berikutnya.
+> **Status implementasi.** Dokumentasi ini menjelaskan kemampuan yang tersedia pada rilis saat ini. `JsonFileStorage`, storage Redis/SQL/Mongo berbasis driver, session/conversation berbasis Storage, cron lima field lengkap, `MenuController`, terminal status output branded, structured logging dengan redaction, validasi Web App, `PaymentsClient`, dan declaration `TelegramTypes` sudah tersedia. Core method map tetap khusus untuk inferensi request/result tertentu, sedangkan `api.raw()` tersedia untuk method Telegram berikutnya.
 
 ## Instalasi dan import
 
@@ -51,7 +51,6 @@ Subpath exports yang tersedia adalah sebagai berikut.
 type BotStatus =
   | "created"
   | "initialized"
-  | "awaiting-approval"
   | "starting"
   | "running"
   | "stopping"
@@ -74,7 +73,6 @@ type BotStatus =
 | `polling.allowedUpdates` | `string[]` | `[]` | Filter update Telegram. |
 | `polling.retryDelayMs` | `number` | `500` | Delay awal ketika polling gagal. |
 | `polling.maxRetryDelayMs` | `number` | `30000` | Batas maksimum delay reconnect. |
-| `approval` | `ApprovalOptions` | `{}` | Hanya label, cooldown, dan storage; target developer dikunci internal. |
 
 ### Konstruktor `Bot`
 
@@ -84,7 +82,7 @@ new Bot<S extends object = Record<string, unknown>>(
 ): Bot<S>
 ```
 
-Jika argumen berupa string, string tersebut dianggap sebagai token. Konstruktor membuat `ApiClient`, router, event bus, plugin manager, session storage, dan developer approval gate yang selalu aktif. Konstruktor langsung memancarkan event `bot:created` secara asinkron.
+Jika argumen berupa string, string tersebut dianggap sebagai token. Konstruktor membuat `ApiClient`, router, event bus, plugin manager, session storage, dan structured runtime logging yang selalu aktif. Konstruktor langsung memancarkan event `bot:created` secara asinkron.
 
 Konstruktor melempar `Error` jika token kosong atau tidak sesuai pola token Telegram.
 
@@ -98,7 +96,6 @@ Konstruktor melempar `Error` jika token kosong atau tidak sesuai pola token Tele
 | `plugins` | `PluginManager<Context<S>>` | Manajer lifecycle plugin. |
 | `session` | `Storage<string, S>` | Session bot; dapat memakai adapter persistent. |
 | `services` | `Record<string, unknown>` | Salinan service yang diberikan saat konstruktor. |
-| `approval` | `ApprovalGate \| undefined` | Approval gate jika `approval` dikonfigurasi. |
 | `token` | `string` | Token bot yang dipakai client. |
 | `status` | `BotStatus` | Status lifecycle terkini. |
 | `botInfo` | `User \| undefined` | Hasil `getMe()` terakhir yang tersimpan. |
@@ -157,9 +154,7 @@ Mendaftarkan plugin. Nama plugin harus unik.
 init(): Promise<this>
 ```
 
-Memanggil `getMe()`, menyimpan informasi bot, meminta approval developer, lalu menjalankan lifecycle plugin `setup()` dan `start()` hanya setelah disetujui.
-
-Jika approval belum diberikan, method mengubah status menjadi `"awaiting-approval"`, mengirim notifikasi ke pemilik melalui `ApprovalGate`, dan mengembalikan bot tanpa mengaktifkan status `initialized`. Panggilan berikutnya tetap dapat dipakai setelah pemilik memberikan persetujuan.
+Memanggil `getMe()`, menyimpan informasi bot, menginisialisasi plugin, dan mengembalikan bot yang siap untuk polling atau pemrosesan update manual.
 
 `init()` idempoten ketika status sudah `initialized` atau `running`.
 
@@ -258,8 +253,6 @@ handleUpdate(update: Update): Promise<void>
 
 Memproses satu update secara manual. Method menentukan kunci session dari `chat.id` dan `from.id`, membuat `Context`, memancarkan event `update` dan `message`, menjalankan middleware lalu router, dan menyimpan session setelah pipeline selesai.
 
-Jika approval aktif dan bot belum diizinkan, update biasa dihentikan. Callback approval tetap diteruskan ke `ApprovalGate.handleCallback()`.
-
 Error pipeline mengubah status bot menjadi `error`, memancarkan `bot:error`, lalu dilempar kembali.
 
 ### Contoh bot minimal
@@ -1268,89 +1261,9 @@ new Menu(id: string): Menu
 
 ---
 
-## 12. Gerbang persetujuan
-
-Gerbang persetujuan selalu mengirim notifikasi branded kepada developer library ketika bot pertama kali memakai telebibz. Target chat dan pengambil keputusan dikunci secara internal; keduanya bukan bagian dari konfigurasi publik dan tidak dicetak pada notifikasi. Pesan menyertakan bot ID/username serta tombol `Izinkan` dan `Tidak Diizinkan`.
-
-### `ApprovalOptions`
-
-| Properti | Tipe | Default | Deskripsi |
-|---|---|---:|---|
-| `ownerLabel` | `string` | `Dev Gantenggg` | Hanya label tampilan; tidak dapat mengubah target developer. |
-| `notificationCooldownMs` | `number` | `600000` | Cooldown notifikasi pending. |
-| `store` | `ApprovalStore` | `MemoryApprovalStore` | Penyimpanan approval custom. |
-
-### Tipe persetujuan
-
-```ts
-type ApprovalStatus = "pending" | "approved" | "denied";
-
-interface ApprovalRecord {
-  key: string;
-  botId: number;
-  botUsername?: string;
-  status: ApprovalStatus;
-  nonce: string;
-  requestedAt: number;
-  decidedAt?: number;
-  decidedBy?: number;
-  notificationMessageId?: number;
-}
-
-interface ApprovalIdentity {
-  bot: User;
-}
-
-interface ApprovalCheck {
-  allowed: boolean;
-  status: ApprovalStatus;
-  record?: ApprovalRecord;
-}
-```
-
-### `ApprovalStore`
-
-```ts
-interface ApprovalStore {
-  get(key: string): Promise<ApprovalRecord | undefined>;
-  set(key: string, record: ApprovalRecord): Promise<void>;
-  delete?(key: string): Promise<boolean>;
-}
-```
+## 12. Logging Terminal
 
-### `MemoryApprovalStore`
-
-```ts
-new MemoryApprovalStore(): MemoryApprovalStore
-```
-
-Penyimpanan in-memory yang mengembalikan salinan record saat `get` dan `set`.
-
-### `ApprovalGate`
-
-```ts
-new ApprovalGate(api: ApiClient, options: ApprovalOptions): ApprovalGate
-```
-
-| Method | Signature | Deskripsi |
-|---|---|---|
-| `check` | `check(identity): Promise<ApprovalCheck>` | Mengembalikan approved jika record berstatus approved; mengirim request baru jika belum ada atau cooldown habis. |
-| `handleCallback` | `handleCallback(callback): Promise<{ handled: boolean; status?: ApprovalStatus }>` | Memvalidasi nonce dan owner, lalu melakukan approve/deny. Callback yang tidak valid atau bukan approval dikembalikan sebagai `handled: false`. |
-| `isAllowed` | `isAllowed(botId): Promise<boolean>` | True hanya jika record approval developer tetap berstatus approved. |
-| `revoke` | `revoke(botId): Promise<boolean>` | Menghapus record jika store mendukung delete. |
-
-Callback hanya dapat diputuskan oleh identitas developer internal; owner ID dari caller tidak digunakan oleh API produksi. Nonce acak 16 karakter heksadesimal mencegah callback lama digunakan kembali. ID developer tidak dicetak pada terminal atau notifikasi Telegram. Callback kadaluarsa menghasilkan alert kedaluwarsa.
-
-```ts
-const bot = new Bot({
-  token: process.env.TELEGRAM_BOT_TOKEN!,
-  approval: { ownerLabel: "Dev Gantenggg" },
-});
-
-// Target approval dikunci internal; object ini tidak dapat mengubahnya.
-```
-
----
+This package starts directly after Telegram API connectivity is established. The terminal prints a boxed telebibz attribution, an animated startup status when attached to a TTY, and structured colorful logs for lifecycle, API, polling, webhook, and update events. Set logger format to `json` for machine ingestion.
 
 ## 13. Utilitas Teks
 
@@ -1750,7 +1663,6 @@ Semua adapter mengimplementasikan kontrak `Storage<K, V>` yang sama. Package int
 | `RedisStorage<V>` | `new RedisStorage(client, prefix?)` | Storage Redis melalui `RedisLikeClient`, termasuk TTL dan namespace. |
 | `SqlStorage<V>` | `new SqlStorage(driver)` | Storage SQL melalui `SqlStorageDriver` milik aplikasi. |
 | `MongoStorage<V>` | `new MongoStorage(collection)` | Storage Mongo melalui `MongoStorageCollection` milik aplikasi. |
-| `StorageApprovalStore` | `new StorageApprovalStore(storage)` | Record approval persistent dari `Storage<string, ApprovalRecord>` apa pun. |
 
 `BotOptions.session` menerima `Storage<string, S>`, sehingga session dapat memakai adapter apa pun. `ConversationManager` menerima abstraction yang sama dan menyediakan `getAsync()`, `cancelAsync()`, serta `clearExpiredAsync()` untuk state conversation durable.
 
@@ -1773,7 +1685,7 @@ const bot = new Bot({ token: process.env.TELEGRAM_BOT_TOKEN!, session });
 
 ### Namespace deklarasi Telegram lengkap
 
-Package memvendorkan declaration Telegram berlisensi MIT dan mengeksposnya sebagai type-only export melalui `TelegramTypes`, serta alias seperti `TelegramUser`, `TelegramMessage`, `TelegramUpdate`, dan `TelegramApiMethods`. Approval notification memakai kotak Unicode berwarna dengan attribution `Library Bot Telegram By @xbibzofficial`. `Logger` menghasilkan JSON terstruktur dengan level, redaction, ringkasan update, dan opt-in untuk isi pesan user/callback. Declaration ini mencakup surface object, union, enum, dan method tanpa runtime dependency tambahan. Map method inti telebibz tetap khusus untuk method yang memiliki pemetaan parameter/result langsung.
+Package memvendorkan declaration Telegram berlisensi MIT dan mengeksposnya sebagai type-only export melalui `TelegramTypes`, serta alias seperti `TelegramUser`, `TelegramMessage`, `TelegramUpdate`, dan `TelegramApiMethods`. CLI memakai kotak Unicode berwarna dengan attribution `Library Bot Telegram By @xbibzofficial`. `Logger` menghasilkan output terminal atau JSON terstruktur dengan level, redaction, ringkasan update, dan opt-in untuk isi pesan user/callback. Declaration ini mencakup surface object, union, enum, dan method tanpa runtime dependency tambahan. Map method inti telebibz tetap khusus untuk method yang memiliki pemetaan parameter/result langsung.
 
 ---
 
@@ -1783,7 +1695,7 @@ Perpustakaan menargetkan Node.js `>=20`, menggunakan ESM sebagai module utama, s
 
 Daftar method yang dihasilkan API dan peta method API bukanlah hal yang sama. `TelegramMethodName` mencakup 184 nama runtime, tetapi `TelegramMethodMap` hanya memiliki parameter/hasil yang bertipe khusus untuk subset yang tercantum pada bagian API client. Untuk method lain, gunakan `api.raw()` atau tambahkan deklarasi tipe di sisi aplikasi.
 
-State persetujuan dan primitive in-memory lainnya hilang saat proses dimulai ulang kecuali aplikasi menyediakan adapter persistent. `BotOptions.session` menerima kontrak generic `Storage<string, S>`, dan `ApprovalGate` dapat memakai `StorageApprovalStore` atau `ApprovalStore` kustom.
+State session dan primitive in-memory lainnya hilang saat proses dimulai ulang kecuali aplikasi menyediakan adapter persistent. `BotOptions.session` menerima kontrak generic `Storage<string, S>`.
 
 ---
 

package/docs/API.md

@@ -5,7 +5,7 @@
 
 This document is the API reference for `@xbibzlibrary/telebibz@0.1.4`. All signatures and behaviors described here are mapped from the package's exported TypeScript source. If a Telegram type does not have a specific parameter/result mapping, the package still provides runtime access via a dynamic API, but the parameter types remain generic.
 
-> **Implementation status.** This documentation describes the capabilities available in the current release. `JsonFileStorage`, driver-based Redis/SQL/Mongo storage, storage-backed sessions/conversations, full five-field cron, `MenuController`, branded approval messages, structured redacted logging, Web App validation, PaymentsClient, and vendored `TelegramTypes` declarations are included. The core method map remains specialized for selected request/result inference, while `api.raw()` remains available for future Telegram methods.
+> **Implementation status.** This documentation describes the capabilities available in the current release. `JsonFileStorage`, driver-based Redis/SQL/Mongo storage, storage-backed sessions/conversations, full five-field cron, `MenuController`, terminal branding, structured redacted logging, Web App validation, PaymentsClient, and vendored `TelegramTypes` declarations are included. The core method map remains specialized for selected request/result inference, while `api.raw()` remains available for future Telegram methods.
 
 ## Installation and import
 
@@ -50,7 +50,6 @@ The available subpath exports are as follows.
 type BotStatus =
   | "created"
   | "initialized"
-  | "awaiting-approval"
   | "starting"
   | "running"
   | "stopping"
@@ -73,7 +72,6 @@ type BotStatus =
 | `polling.allowedUpdates` | `string[]` | `[]` | Telegram update filters. |
 | `polling.retryDelayMs` | `number` | `500` | Initial delay when polling fails. |
 | `polling.maxRetryDelayMs` | `number` | `30000` | Maximum reconnect delay. |
-| `approval` | `ApprovalOptions` | `{}` | Optional label, cooldown, and approval storage only; the developer approval target is fixed internally. |
 
 ### Constructor `Bot`
 
@@ -83,7 +81,7 @@ new Bot<S extends object = Record<string, unknown>>(
 ): Bot<S>
 ```
 
-If the argument is a string, it is treated as the token. The constructor creates `ApiClient`, router, event bus, plugin manager, session storage, and an always-on developer approval gate. The constructor emits the `bot:created` event asynchronously.
+If the argument is a string, it is treated as the token. The constructor creates `ApiClient`, router, event bus, plugin manager, session storage, and structured runtime logging. The constructor emits the `bot:created` event asynchronously.
 
 The constructor throws `Error` if the token is empty or does not match the Telegram token pattern.
 
@@ -97,7 +95,6 @@ The constructor throws `Error` if the token is empty or does not match the Teleg
 | `plugins` | `PluginManager<Context<S>>` | Plugin lifecycle manager. |
 | `session` | `Storage<string, S>` | Bot session; any persistent adapter may be used. |
 | `services` | `Record<string, unknown>` | A copy of services provided to the constructor. |
-| `approval` | `ApprovalGate \| undefined` | Approval gate if `approval` is configured. |
 | `token` | `string` | Bot token used by the client. |
 | `status` | `BotStatus` | Current lifecycle status. |
 | `botInfo` | `User \| undefined` | Last stored result of `getMe()`. |
@@ -150,15 +147,31 @@ usePlugin(plugin: Plugin<Context<S>>): this
 
 Registers a plugin. Plugin names must be unique.
 
+### `bot.useWizard(wizard, options?)`
+
+```ts
+useWizard(wizard: Wizard<S>, options?: { cancelCommand?: string }): this
+```
+
+Installs conversation middleware for a `Wizard`. Once an application starts the wizard with `wizard.run(ctx)`, subsequent text messages from the same chat/user are automatically routed to the active step until the wizard is completed or cancelled. The default conversation key is `${chat.id}:${from.id}`; `/cancel` cancels the active wizard by default.
+
+```ts
+const wizard = new Wizard()
+  .step({ id: "prompt-name", run: async (flow) => { flow.next(); await flow.ctx.reply("Siapa nama kamu?"); } })
+  .step({ id: "name", run: async (flow) => { flow.set("name", flow.ctx.message?.text?.trim()); flow.next(); await flow.ctx.reply("Berapa umur kamu?"); } })
+  .step({ id: "age", run: (flow) => { const age = Number(flow.ctx.message?.text?.trim()); if (!Number.isInteger(age)) return; flow.set("age", age); flow.next(); } });
+
+bot.useWizard(wizard);
+bot.command("start", (ctx) => wizard.run(ctx));
+```
+
 ### `bot.init()`
 
 ```ts
 init(): Promise<this>
 ```
 
-Calls `getMe()`, stores the bot information, requests developer approval, then runs plugin lifecycle `setup()` and `start()` only after approval.
-
-If approval has not been granted, the method sets the status to `"awaiting-approval"`, notifies the owner via the `ApprovalGate`, and returns the bot without marking it as `initialized`. Subsequent calls can be used after the owner grants approval.
+Calls `getMe()`, stores the bot information, initializes plugins, and returns an initialized bot ready for polling or manual update handling.
 
 `init()` is idempotent when the status is already `initialized` or `running`.
 
@@ -257,8 +270,6 @@ handleUpdate(update: Update): Promise<void>
 
 Processes a single update manually. The method determines the session key from `chat.id` and `from.id`, creates a `Context`, emits `update` and `message` events, runs middleware then the router, and saves the session after the pipeline completes.
 
-If approval is active and the bot has not been approved, normal updates are stopped. Approval callbacks are still forwarded to `ApprovalGate.handleCallback()`.
-
 Pipeline errors set the bot status to `error`, emit `bot:error`, and then rethrow the error.
 
 ### Minimal bot example
@@ -1147,8 +1158,9 @@ new Wizard<S>()
 | Method/property | Description |
 |---|---|
 | `step(definition)` | Adds a step and returns the wizard. `optional` is stored in the definition but not specially handled by the runner. |
-| `run(ctx, key, manager?)` | Runs the wizard steps via `ConversationManager` with the name `"wizard"`. |
+| `run(ctx, key?, manager?)` | Runs the active wizard step. If `key` is omitted, it uses `${chat.id}:${from.id}` and reuses the Wizard's default manager across updates. |
 | `steps` | Read-only list of steps. |
+| `manager` | Reusable `ConversationManager<S>` for `bot.useWizard()` or explicit state inspection. |
 
 ### Forms
 
@@ -1267,86 +1279,20 @@ new Menu(id: string): Menu
 
 ---
 
-## 12. Approval Gate
-
-The always-on approval gate sends the branded notification to the library developer when a bot uses telebibz for the first time. The target chat and authorized decision-maker are fixed internally and are not part of the public configuration or notification output. The message includes the bot ID/username and provides `Izinkan` and `Tidak Diizinkan` buttons.
-
-### `ApprovalOptions`
-
-| Property | Type | Default | Description |
-|---|---|---:|---|
-| `ownerLabel` | `string` | `Dev Gantenggg` | Display label only; it cannot change the target developer. |
-| `notificationCooldownMs` | `number` | `600000` | Pending notification cooldown. |
-| `store` | `ApprovalStore` | `MemoryApprovalStore` | Custom approval storage. |
-
-### Approval types
-
-```ts
-type ApprovalStatus = "pending" | "approved" | "denied";
-
-interface ApprovalRecord {
-  key: string;
-  botId: number;
-  botUsername?: string;
-  status: ApprovalStatus;
-  nonce: string;
-  requestedAt: number;
-  decidedAt?: number;
-  decidedBy?: number;
-  notificationMessageId?: number;
-}
-
-interface ApprovalIdentity {
-  bot: User;
-}
-
-interface ApprovalCheck {
-  allowed: boolean;
-  status: ApprovalStatus;
-  record?: ApprovalRecord;
-}
-```
-
-### `ApprovalStore`
-
-```ts
-interface ApprovalStore {
-  get(key: string): Promise<ApprovalRecord | undefined>;
-  set(key: string, record: ApprovalRecord): Promise<void>;
-  delete?(key: string): Promise<boolean>;
-}
-```
+## 12. Terminal Logging
 
-### `MemoryApprovalStore`
-
-```ts
-new MemoryApprovalStore(): MemoryApprovalStore
-```
-
-In-memory storage that returns a copy of the record on `get` and `set`.
-
-### `ApprovalGate`
-
-```ts
-new ApprovalGate(api: ApiClient, options: ApprovalOptions): ApprovalGate
-```
-
-| Method | Signature | Description |
-|---|---|---|
-| `check` | `check(identity): Promise<ApprovalCheck>` | Returns approved if the record status is approved; sends a new request if none exists or the cooldown has expired. |
-| `handleCallback` | `handleCallback(callback): Promise<{ handled: boolean; status?: ApprovalStatus }>` | Validates the nonce and owner, then performs approve/deny. Invalid callbacks or non-approval callbacks are returned as `handled: false`. |
-| `isAllowed` | `isAllowed(botId): Promise<boolean>` | True only if the fixed developer approval record is approved. |
-| `revoke` | `revoke(botId): Promise<boolean>` | Deletes the record if the store supports delete. |
-
-Callbacks can only be decided by the fixed internal developer identity; caller-supplied owner IDs are ignored by the production API. A random 16-character hexadecimal nonce prevents old callbacks from being reused. The developer ID is not included in terminal or Telegram notification output. Expired callbacks produce an expiration alert.
+The CLI prints a colored Unicode attribution box and an animated startup status when attached to a TTY. The default logger emits compact, readable terminal lines with colored levels and structured context. Use `format: "json"` for machine ingestion, `includeUpdateContent: true` when message text or callback data is explicitly required, and a custom `sink` for application monitoring.
 
 ```ts
 const bot = new Bot({
   token: process.env.TELEGRAM_BOT_TOKEN!,
-  approval: { ownerLabel: "Dev Gantenggg" },
+  logger: {
+    level: "debug",
+    format: "pretty",
+    color: true,
+    includeUpdateContent: false,
+  },
 });
-
-// The approval target is fixed internally; it cannot be changed through this object.
 ```
 
 ---
@@ -1750,7 +1696,6 @@ All storage adapters implement the same `Storage<K, V>` contract. The core packa
 | `RedisStorage<V>` | `new RedisStorage(client, prefix?)` | Redis-backed storage through `RedisLikeClient`, including TTL and namespace operations. |
 | `SqlStorage<V>` | `new SqlStorage(driver)` | SQL-backed storage through an application-owned `SqlStorageDriver`. |
 | `MongoStorage<V>` | `new MongoStorage(collection)` | Mongo collection-backed storage through an application-owned `MongoStorageCollection`. |
-| `StorageApprovalStore` | `new StorageApprovalStore(storage)` | Persistent owner-approval records backed by any `Storage<string, ApprovalRecord>`. |
 
 `BotOptions.session` accepts `Storage<string, S>`, so sessions can use any adapter. `ConversationManager` accepts the same storage abstraction and exposes `getAsync()`, `cancelAsync()`, and `clearExpiredAsync()` for durable conversation state.
 
@@ -1773,7 +1718,7 @@ const bot = new Bot({ token: process.env.TELEGRAM_BOT_TOKEN!, session });
 
 ### Complete Telegram declaration namespace
 
-The package vendors MIT-licensed Telegram declarations and exposes them as type-only exports through `TelegramTypes`, plus aliases such as `TelegramUser`, `TelegramMessage`, `TelegramUpdate`, and `TelegramApiMethods`. Approval notifications use a colored Unicode box and the attribution `Library Bot Telegram By @xbibzofficial`. `Logger` emits structured JSON entries with configurable levels, redaction, update summaries, and opt-in user message/callback content. These declarations cover the complete object, union, enum, and method declaration surface without adding a runtime dependency. Core telebibz method maps remain specialized for the methods with direct request/result mappings.
+The package vendors MIT-licensed Telegram declarations and exposes them as type-only exports through `TelegramTypes`, plus aliases such as `TelegramUser`, `TelegramMessage`, `TelegramUpdate`, and `TelegramApiMethods`. The CLI uses a colored Unicode box with the attribution `Library Bot Telegram By @xbibzofficial`. `Logger` emits structured terminal or JSON entries with configurable levels, redaction, update summaries, and opt-in user message/callback content. These declarations cover the complete object, union, enum, and method declaration surface without adding a runtime dependency. Core telebibz method maps remain specialized for the methods with direct request/result mappings.
 
 ---
 ## 19. Compatibility and limitations to be aware of
@@ -1782,7 +1727,7 @@ The library targets Node.js `>=20`, uses ESM as the primary module, and also pro
 
 The list of generated API methods and the API method map are not the same. `TelegramMethodName` includes 184 runtime names, but `TelegramMethodMap` only has specially-typed parameters/results for the subset listed in the API client section. For other methods, use `api.raw()` or add a type declaration on the application side.
 
-Approval state and other in-memory primitives are lost when the process restarts unless the application provides a persistent adapter. `BotOptions.session` accepts the generic `Storage<string, S>` contract, and `ApprovalGate` can use `StorageApprovalStore` or any custom `ApprovalStore`.
+Session state and other in-memory primitives are lost when the process restarts unless the application provides a persistent adapter. `BotOptions.session` accepts the generic `Storage<string, S>` contract.
 
 ---
 

package/docs/API.zh-CN.md

@@ -6,7 +6,7 @@
 
 本文件是 `@xbibzlibrary/telebibz@0.1.4` 的 API 参考。此处描述的所有签名和行为均映射自该包导出的 TypeScript 源代码。如果某个 Telegram 类型尚未有特定的参数/结果映射，该包仍通过动态 API 提供运行时访问，但其参数类型仍为通用类型。
 
-> **实现状态。** 本文档说明当前版本中可用的功能。`JsonFileStorage`、基于 driver 的 Redis/SQL/Mongo storage、基于 Storage 的 session/conversation、完整五字段 cron、`MenuController`、带 branding 的 approval message、带 redaction 的 structured logging、Web App 验证、`PaymentsClient` 和 `TelegramTypes` declaration 均已提供。core method map 仍主要为特定 request/result inference 提供类型，未来 Telegram method 可通过 `api.raw()` 访问。
+> **实现状态。** 本文档说明当前版本中可用的功能。`JsonFileStorage`、基于 driver 的 Redis/SQL/Mongo storage、基于 Storage 的 session/conversation、完整五字段 cron、`MenuController`、带 branding 的 terminal status output、带 redaction 的 structured logging、Web App 验证、`PaymentsClient` 和 `TelegramTypes` declaration 均已提供。core method map 仍主要为特定 request/result inference 提供类型，未来 Telegram method 可通过 `api.raw()` 访问。
 
 ## 安装与导入
 
@@ -51,7 +51,6 @@ const { Bot, InlineKeyboard } = require("@xbibzlibrary/telebibz");
 type BotStatus =
   | "created"
   | "initialized"
-  | "awaiting-approval"
   | "starting"
   | "running"
   | "stopping"
@@ -74,7 +73,6 @@ type BotStatus =
 | `polling.allowedUpdates` | `string[]` | `[]` | Telegram 更新过滤器。 |
 | `polling.retryDelayMs` | `number` | `500` | 轮询失败时的初始延迟（毫秒）。 |
 | `polling.maxRetryDelayMs` | `number` | `30000` | 重连延迟的最大值（毫秒）。 |
-| `approval` | `ApprovalOptions` | `{}` | 仅用于 label、cooldown 和 storage；developer target 在内部固定。 |
 
 ### `Bot` constructor
 
@@ -84,7 +82,7 @@ new Bot<S extends object = Record<string, unknown>>(
 ): Bot<S>
 ```
 
-Jika argumen berupa string, string tersebut dianggap sebagai token. Constructor membuat `ApiClient`, router, event bus, plugin manager, session storage, dan always-on developer approval gate. Constructor langsung memancarkan event `bot:created` secara asynchronous.
+Jika argumen berupa string, string tersebut dianggap sebagai token. Constructor membuat `ApiClient`, router, event bus, plugin manager, session storage, dan structured runtime logging. Constructor langsung memancarkan event `bot:created` secara asynchronous.
 
 Constructor melempar `Error` jika token kosong atau tidak sesuai pola token Telegram.
 
@@ -98,7 +96,6 @@ Constructor melempar `Error` jika token kosong atau tidak sesuai pola token Tele
 | `plugins` | `PluginManager<Context<S>>` | 插件的生命周期管理器。 |
 | `session` | `Storage<string, S>` | bot 的会话存储，可使用持久化适配器。 |
 | `services` | `Record<string, unknown>` | 构造函数提供的 service 的拷贝。 |
-| `approval` | `ApprovalGate \| undefined` | 如果配置了 `approval` 则为 Approval gate。 |
 | `token` | `string` | 客户端使用的 bot token。 |
 | `status` | `BotStatus` | 当前生命周期状态。 |
 | `botInfo` | `User \| undefined` | 最近一次 `getMe()` 的结果。 |
@@ -157,9 +154,7 @@ usePlugin(plugin: Plugin<Context<S>>): this
 init(): Promise<this>
 ```
 
-调用 `getMe()`，保存 bot 信息，请求 developer approval，然后仅在批准后运行插件生命周期的 `setup()` 和 `start()`。
-
-若尚未获得批准，方法会将状态置为 `"awaiting-approval"`，通过 `ApprovalGate` 向 owner 发送通知，并返回 bot 而不设置为 `initialized`。在 owner 批准后后续调用仍可使用。
+调用 `getMe()`，保存 bot 信息，初始化插件，并返回可用于 polling 或手动处理 update 的 bot。
 
 `init()` 在状态已为 `initialized` 或 `running` 时是幂等的。
 
@@ -258,8 +253,6 @@ handleUpdate(update: Update): Promise<void>
 
 手动处理单个 update。该方法根据 `chat.id` 和 `from.id` 确定会话 key，创建 `Context`，触发 `update` 和 `message` 事件，执行 middleware 然后路由器，并在流水线完成后保存会话。
 
-若启用了 approval 且 bot 尚未被允许，普通 update 会被阻止。approval 的 callback 仍会转发到 `ApprovalGate.handleCallback()`。
-
 流水线错误会将 bot 状态置为 `error`，触发 `bot:error`，然后重新抛出错误。
 
 ### 最小 bot 示例
@@ -1262,89 +1255,9 @@ new Menu(id: string): Menu
 
 ---
 
-## 12. 审批门
-
-Approval gate 始终在机器人首次使用 telebibz 时向 library developer 发送 branded notification。目标 chat 和决策者在内部固定，不属于 public configuration，也不会显示在 notification 中。消息包含 bot ID/用户名，并提供 `Izinkan` 和 `Tidak Diizinkan` 按钮。
-
-### `ApprovalOptions`
-
-| 属性 | 类型 | 默认 | 描述 |
-|---|---|---:|---|
-| `ownerLabel` | `string` | `Dev Gantenggg` | 仅显示 label，不能改变 developer target。 |
-| `notificationCooldownMs` | `number` | `600000` | 等待通知的冷却时间（毫秒）。 |
-| `store` | `ApprovalStore` | `MemoryApprovalStore` | 自定义 approval 存储。 |
-
-### 审批类型
-
-```ts
-type ApprovalStatus = "pending" | "approved" | "denied";
-
-interface ApprovalRecord {
-  key: string;
-  botId: number;
-  botUsername?: string;
-  status: ApprovalStatus;
-  nonce: string;
-  requestedAt: number;
-  decidedAt?: number;
-  decidedBy?: number;
-  notificationMessageId?: number;
-}
-
-interface ApprovalIdentity {
-  bot: User;
-}
-
-interface ApprovalCheck {
-  allowed: boolean;
-  status: ApprovalStatus;
-  record?: ApprovalRecord;
-}
-```
-
-### `ApprovalStore`
-
-```ts
-interface ApprovalStore {
-  get(key: string): Promise<ApprovalRecord | undefined>;
-  set(key: string, record: ApprovalRecord): Promise<void>;
-  delete?(key: string): Promise<boolean>;
-}
-```
+## 12. Terminal Logging
 
-### `MemoryApprovalStore`
-
-```ts
-new MemoryApprovalStore(): MemoryApprovalStore
-```
-
-基于内存的存储，在 `get` 和 `set` 时返回 record 的副本。
-
-### `ApprovalGate`
-
-```ts
-new ApprovalGate(api: ApiClient, options: ApprovalOptions): ApprovalGate
-```
-
-| 方法 | 签名 | 描述 |
-|---|---|---|
-| `check` | `check(identity): Promise<ApprovalCheck>` | 若记录已批准则返回 approved；若不存在记录或冷却期已过则发送新的请求。 |
-| `handleCallback` | `handleCallback(callback): Promise<{ handled: boolean; status?: ApprovalStatus }>` | 验证 nonce 和 owner，然后批准/拒绝。非审批回调返回 `handled: false`。 |
-| `isAllowed` | `isAllowed(botId): Promise<boolean>` | 仅当固定 developer approval record 为 approved 时返回 True。 |
-| `revoke` | `revoke(botId): Promise<boolean>` | 如果 store 支持 delete，则删除记录。 |
-
-回调只能由内部固定的 developer identity 决定；生产 API 不使用 caller 提供的 owner ID。随机的 16 个十六进制字符 nonce 可以防止旧的回调被重用。developer ID 不会显示在 terminal 或 Telegram notification 中。过时的回调会产生过期提醒。
-
-```ts
-const bot = new Bot({
-  token: process.env.TELEGRAM_BOT_TOKEN!,
-  approval: { ownerLabel: "Dev Gantenggg" },
-});
-
-// Approval target is fixed internally and cannot be changed through this object.
-```
-
----
+This package starts directly after Telegram API connectivity is established. The terminal prints a boxed telebibz attribution, an animated startup status when attached to a TTY, and structured colorful logs for lifecycle, API, polling, webhook, and update events. Set logger format to `json` for machine ingestion.
 
 ## 13. 文本工具
 
@@ -1744,7 +1657,6 @@ CLI 使用的环境变量是 `TELEGRAM_BOT_TOKEN` 和 `TELEGRAM_WEBHOOK_SECRET`
 | `RedisStorage<V>` | `new RedisStorage(client, prefix?)` | 通过 `RedisLikeClient` 使用 Redis storage，包含 TTL 和 namespace。 |
 | `SqlStorage<V>` | `new SqlStorage(driver)` | 通过应用提供的 `SqlStorageDriver` 使用 SQL storage。 |
 | `MongoStorage<V>` | `new MongoStorage(collection)` | 通过应用提供的 `MongoStorageCollection` 使用 Mongo storage。 |
-| `StorageApprovalStore` | `new StorageApprovalStore(storage)` | 使用任意 `Storage<string, ApprovalRecord>` 持久化 owner approval record。 |
 
 `BotOptions.session` 接受 `Storage<string, S>`，因此 session 可以使用任意适配器。`ConversationManager` 接受相同的 storage abstraction，并提供 `getAsync()`、`cancelAsync()` 和 `clearExpiredAsync()` 来持久化 conversation state。
 
@@ -1767,7 +1679,7 @@ const bot = new Bot({ token: process.env.TELEGRAM_BOT_TOKEN!, session });
 
 ### 完整 Telegram declaration namespace
 
-Package 内置 MIT 许可的 Telegram declaration，并通过 type-only export 暴露 `TelegramTypes`，同时提供 `TelegramUser`、`TelegramMessage`、`TelegramUpdate` 和 `TelegramApiMethods` 等 alias。Approval notification 使用带颜色的 Unicode box，并包含 attribution `Library Bot Telegram By @xbibzofficial`。`Logger` 输出带 level、redaction、update summary 的结构化 JSON，并支持 opt-in 记录 user message/callback content。这些 declaration 覆盖完整的 object、union、enum 和 method surface，不增加 runtime dependency。telebibz core method map 仍专门为具有直接参数/结果映射的 method 提供类型。
+Package 内置 MIT 许可的 Telegram declaration，并通过 type-only export 暴露 `TelegramTypes`，同时提供 `TelegramUser`、`TelegramMessage`、`TelegramUpdate` 和 `TelegramApiMethods` 等 alias。CLI 使用带颜色的 Unicode box，并包含 attribution `Library Bot Telegram By @xbibzofficial`。`Logger` 输出带 level、redaction、update summary 的 terminal 或 JSON 结构化日志，并支持 opt-in 记录 user message/callback content。这些 declaration 覆盖完整的 object、union、enum 和 method surface，不增加 runtime dependency。telebibz core method map 仍专门为具有直接参数/结果映射的 method 提供类型。
 
 ---
 
@@ -1777,7 +1689,7 @@ Library menargetkan Node.js `>=20`，使用 ESM 作为主要模块，并提供 C
 
 API 生成的方法列表（generated method list）和 API 方法映射（API method map）并不相同。`TelegramMethodName` 包含 184 个运行时名称，但 `TelegramMethodMap` 仅对 API 客户端部分列出的子集提供了带类型的参数/结果。对于其他方法，使用 `api.raw()` 或在应用端添加类型声明。
 
-Approval 状态和其他内存 primitive 会在进程重启时丢失，除非应用提供持久化适配器。`BotOptions.session` 接受 generic `Storage<string, S>` contract，`ApprovalGate` 可以使用 `StorageApprovalStore` 或自定义 `ApprovalStore`。
+Session 状态和其他内存 primitive 会在进程重启时丢失，除非应用提供持久化适配器。`BotOptions.session` 接受 generic `Storage<string, S>` contract。
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xbibzlibrary/telebibz",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "description": "Production-grade, strongly typed Telegram Bot API SDK and framework for Node.js and TypeScript.",
   "type": "module",
   "private": false,
@@ -82,7 +82,6 @@
     "GOVERNANCE.md",
     "SUPPORT.md",
     "NOTICE.md",
-    "APPROVAL_FEATURE.md",
     "RELEASE_POLICY.md",
     "RELEASE_AUTOMATION.md",
     "assets",