docs: improve README examples, bump v0.1.1

- Replace Record<string, string> with Record<Route, string> to show
  satisfies key exhaustiveness checking
- Show as const and as const satisfies as allowed patterns
- Fix Bad example to demonstrate missing-field problem

Author: Hiro5409

README.md

@@ -38,13 +38,24 @@ This rule nudges code toward:
 ## Examples
 
 ```typescript
-// Bad
-const canvas = document.getElementById("c") as HTMLCanvasElement;
-const name = <string> data.name;
-
-// Good
-const canvas: HTMLCanvasElement | null = document.querySelector("canvas");
-const config = { mode: "dark" } satisfies AppConfig;
+// Bad — compiler won't catch missing fields
+const user = {} as { name: string; email: string };
+const el = <HTMLCanvasElement> document.getElementById("c");
+
+// Good — type annotation catches missing fields at compile time
+const user: { name: string; email: string } = { name: "alice", email: "a@b.c" };
+
+// Good — satisfies ensures all keys are covered (forget one → compile error)
+type Route = "home" | "about" | "contact";
+const paths = {
+  home: "/",
+  about: "/about",
+  contact: "/contact",
+} satisfies Record<Route, string>;
+
+// Good — as const and as const satisfies are always allowed
+const ROLES = ["admin", "user"] as const;
+const config = { debug: false } as const satisfies { debug: boolean };
 ```
 
 ## Ignoring a report

deno.json

@@ -1,6 +1,6 @@
 {
   "name": "@hiro5409/deno-no-type-assertion-lint",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "license": "MIT",
   "exports": "./mod.ts",
   "publish": {