@telepath-computer/television 0.1.77 → 0.1.79

package/dist/cli.cjs

@@ -50123,8 +50123,8 @@ function resolveVercelSkillsInstallerBin() {
   return localRequire.resolve("skills/bin/cli.mjs");
 }
 function readCLIVersion() {
-  if ("0.1.77".length > 0) {
-    return "0.1.77";
+  if ("0.1.79".length > 0) {
+    return "0.1.79";
   }
   const devPackageJsonPath = import_node_path7.default.join(getDevPackageDir(), "package.json");
   if (!(0, import_node_fs4.existsSync)(devPackageJsonPath)) {
@@ -50133,10 +50133,10 @@ function readCLIVersion() {
   return JSON.parse((0, import_node_fs4.readFileSync)(devPackageJsonPath, "utf8")).version;
 }
 function listKnownArtifactTypeDocs() {
-  if ('["artifact-types/table.md"]'.length > 0) {
-    return JSON.parse('["artifact-types/table.md"]');
+  if ('["artifact-types/calendar.md","artifact-types/table.md"]'.length > 0) {
+    return JSON.parse('["artifact-types/calendar.md","artifact-types/table.md"]');
   }
-  const televisionSkillsWorkspaceDir = import_node_path7.default.resolve(getDevPackageDir(), "../television-skills");
+  const televisionSkillsWorkspaceDir = import_node_path7.default.resolve(getDevPackageDir(), "../skills");
   if (!(0, import_node_fs4.existsSync)(televisionSkillsWorkspaceDir)) {
     return [];
   }

package/dist/skills/television/SKILL.md

@@ -21,4 +21,5 @@ Read `what-to-read.md` next to decide which companion docs apply.
 
 ## Known artifact-type docs
 
+- `artifact-types/calendar.md` — Calendar
 - `artifact-types/table.md` — Table

package/dist/skills/television/artifact-types/calendar.md

@@ -0,0 +1,139 @@
+# Authoring a calendar week
+
+A working-week calendar with a generated header strip, all-day band, time axis,
+and timed event grid. The agent only authors a single `<calendar-week>` plus
+flat sibling `<calendar-event>` children. The component renders the rest.
+
+## Required assets
+
+Every calendar artifact must load both the canonical stylesheet and the
+calendar element bundle:
+
+```html
+<link rel="stylesheet" href="/canonical/v1/styles.css" />
+<link rel="stylesheet" href="/skills/artifact-calendar/calendar.css" />
+<script type="module" src="/skills/artifact-calendar/calendar.js"></script>
+```
+
+`/skills/artifact-calendar/calendar.js` and
+`/skills/artifact-calendar/calendar.css` are the built skill-local assets
+served by artifactory from the package's `dist/` output. They register the
+custom elements and provide the calendar-specific chrome styling. Do not
+inline or reimplement those elements yourself.
+
+## Markup contract
+
+Author exactly this surface:
+
+```html
+<calendar-week start-date="YYYY-MM-DD" days="N" start-hour="8">
+  <calendar-event title="..." start="..." end="..." color="blue"></calendar-event>
+  <calendar-event title="..." start="..." end="..." all-day color="purple"></calendar-event>
+</calendar-week>
+```
+
+`<calendar-week>` attributes:
+
+- `start-date` is required and must be a real `YYYY-MM-DD` date.
+- `days` is required and should usually be `5` or `7`.
+- `start-hour` is optional. Omit it unless you need a fixed initial scroll
+  position.
+
+`<calendar-event>` attributes:
+
+- `title` is required.
+- `start` is required.
+- `end` is required.
+- `all-day` is optional and presence-only. Use it only for all-day events.
+- `color` is optional. Allowed values: `red`, `orange`, `yellow`, `green`,
+  `blue`, `purple`. Omitted or unknown values fall back to the neutral default.
+
+## Timed vs. all-day events
+
+Timed events:
+
+- Omit `all-day`.
+- Use `YYYY-MM-DDTHH:MM` wall-clock datetimes for both `start` and `end`.
+- Keep each event within a single day.
+
+All-day events:
+
+- Include `all-day`.
+- Use date-only `YYYY-MM-DD` values for both `start` and `end`.
+- `end` is non-inclusive, following RFC 5545.
+
+Examples:
+
+- Single-day all-day holiday on Monday:
+  `start="2026-05-04" end="2026-05-05" all-day`
+- Tue–Thu offsite:
+  `start="2026-05-05" end="2026-05-08" all-day`
+- Timed design review from 11:00 to 12:30:
+  `start="2026-05-06T11:00" end="2026-05-06T12:30"`
+
+Repeat the non-inclusive rule when you think about date spans. A Mon–Fri trip
+is `start="2026-05-04" end="2026-05-09"`, not `end="2026-05-08"`.
+
+## What the component auto-renders
+
+Do not author any of these directly:
+
+- `<calendar-headers>`
+- `<calendar-day>`
+- `<calendar-allday>`
+- `<calendar-grid>`
+- `<calendar-time-axis>`
+- `<calendar-column>`
+- `<calendar-cell>`
+
+Those are internal chrome and CSS targets created by `<calendar-week>`.
+
+## Behavior to rely on
+
+- All-day events clip silently to the visible range.
+- All-day events stack into lanes automatically when their visible spans
+  overlap.
+- Timed events on the same day cascade to the right when their time ranges
+  overlap.
+- Malformed events are silently dropped. There is no error pill or fallback UI.
+
+## Content guidance
+
+- Make the schedule feel real. Use plausible meeting names, owners, and time
+  blocks.
+- Vary the event titles and use sensible durations.
+- Use the color palette intentionally; don't paint everything the same color.
+- Avoid placeholder text like "Lorem ipsum", "Event 1", or "Meeting".
+
+## Minimal complete example
+
+```html
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Team Week</title>
+    <link rel="stylesheet" href="/canonical/v1/styles.css" />
+    <link rel="stylesheet" href="/skills/artifact-calendar/calendar.css" />
+    <script type="module" src="/skills/artifact-calendar/calendar.js"></script>
+    <style>
+      html, body { margin: 0; min-height: 100vh; }
+      calendar-week { height: 100vh; }
+    </style>
+  </head>
+  <body>
+    <calendar-week start-date="2026-05-04" days="5">
+      <calendar-event title="Holiday" start="2026-05-04" end="2026-05-05" all-day color="red"></calendar-event>
+      <calendar-event title="Standup" start="2026-05-05T09:00" end="2026-05-05T09:30" color="blue"></calendar-event>
+      <calendar-event title="Design review" start="2026-05-06T11:00" end="2026-05-06T12:30" color="purple"></calendar-event>
+    </calendar-week>
+  </body>
+</html>
+```
+
+## Non-goals
+
+- Do not author internal chrome or custom day headers.
+- Do not use timezones, UTC conversion, or seconds.
+- Do not invent interaction, editing UI, filters, or legends unless asked.

package/dist/skills/television/what-to-read.md

@@ -23,4 +23,5 @@ HTML artifact work may also require a kind-specific doc under `artifact-types/`.
 
 ## Known artifact-type docs
 
+- `artifact-types/calendar.md` — Calendar
 - `artifact-types/table.md` — Table