❓⁄❓ ➡️ 2026-09-22 Update᠄ Vďibňík 3.0 Completion Roadmap

> [!check] This is a page out of [[What Is Grail Diary|Grail Diary]]. ### `Čas`: 06:22:11 (Wednesday, 9 September 2026 / 252) ###### Mood Rating: 10 1. [ ] **UPDATING THE 5 SYSTEM PROMPTS** 1. [ ] (re)read/`lumberjack` the 5 system prompts 2. [ ] KRMIVO ANALYST Updates 1. [ ] take into account TIME (!!!) of `Krmivo` (`Pôst` Schedule !!!) & the MOOD 2. [ ] Summary Picture from `Pažrapka` 1. [ ] Incorrect fasting data from `Pažrapka` 3. [ ] whole-day holistic Rating on the Scale from 1 to 10: NOT mathematical Average !! 1. [ ] quoting `Kvintostratég`: “the `Krmivo Analyst`'s daily judgment needs to consider things that averaging cannot capture: **quantity, nutritional severity, meal composition, timing, repetition, compensatory effects that are genuinely meaningful, and the overall dietary pattern**. A small good item should not numerically neutralize a huge bad one merely because spreadsheet software understands addition better than consequences.” 4. [ ] [[Krmivo Taste Star-Rating Scale]] 1. [ ] also state the mathematical Average of `Krmivo` Taste Ratings for the Day !!! 5. [ ] Have the `Krmivo` summary `Vďibňík` entry itself state something like: 1. [ ] **Average Taste**: ⭐ 3.8/5 1. [ ] ➡️ follows simple mathematical Average 2. [ ] **Daily Reasonableness**: 4/10 1. [ ] ➡️ *interpretive* rating: entirely up to the Discretion of the 🤖 on duty performing the role of `Krmivo Analyst` on that day; *may* coincide with the mathematical Average of individual Ratings for the Day, but may also deviate wildly from it 3. [ ] POHIB ANALYST Updates 1. [ ] do comment on those 3 random notifications !!! 2. [ ] comment on `Strukogram` being listened to 1. [ ] **Media context:** Inspect all boundary screenshots for visible podcast, audiobook, music or other media playback. If legible, record the app, programme or podcast, episode/title fragment, and apparent playback state. Treat spoken-audio playback as a possible influence on walking speed and cognitive load, but do not claim causation from one occurrence. Do not assume playback continued throughout the entire `Časowka` unless the screenshots or accompanying text support that conclusion. If a player is obscured by another Samsung card or notification, explicitly state the uncertainty. 3. [ ] mention `trap window` for `Pochodi` from 6:30 to 7:00 4. [ ] VĎIBŇÍK PLAY-BY-PLAY SYSTEM PROMPT Updates 1. [ ] Start every day by reading the Pair of Summaries for at *least* the most recent day via `Majonéza` in the `daily_wrap-ups` Folder 2. [ ] **crucial Ideas & Principles for the play-by-play 🤖**, especially at the *Start* of every new play-by-play Thread, are captured here: https://chatgpt.com/s/t_6a7e33edca748191a1e22c6ff634adac 3. [ ] After successfully reading individual `Vďibňík` Markdown entries via `Majonéza` at any point over the course of a day, the play-by-play 🤖 should check off the `submitted_to_robots` property in the frontmatter of each such Markdown entry, so that the 🤖 knows that these entries have already been processed for journaling feedback. During the next `Majonéza` round, the 🤖 would then know from which fresh entries he or she should resume the journaling analysis and feedback. 4. [ ] re-think the Footer Navigation-Links Builder Script: Is it really necessary for the file to be *published* before the builder can run? 🤔 This seems inconvenient because I may wish to publish an entry already with the navigation footer in it, whereas right now I first need to publish it *without* the footer, and only *then* the script runs, and then I need to immediately *republish*, which forces me to publish the same `Vďibňík` entry basically twice within 30 seconds. Maybe the builder script could be reworked so that this double publication is not needed? 1. [ ] Perhaps there could be yet another special frontmatter property called `override_publishing_requirement` which I could manually check off on an *impromptu* basis if I want to *quickly* publish a *newly added* individual Vďibňík Markdown file right away? 🤔🛠️ This way, the script would run even *before* I publish that newly added Markdown file for the first time. 5. [ ] mention `trap window` for `Pochodi` from 6:30 to 7:00 6. [ ] insert **DAILY WRAPUP** 1. [ ] **ROT 2.0 analysis** 🥰 (Values in the most recent completed Column *within the Context* of recent Days, Weeks… and the long-Term Averages in Columns `A` to `K`) **is now an integral part of every `Vďibňík` Play-by-Play wrap-up.** 🤩 1. [ ] The play-by-play 🤖 is allowed & *encouraged* to check the Progress of maintaining the ≈165 daily habits over the Course of the Day, too, not just at the End of the Day for the Daily Wrapup ❗ 1. [ ] Thanks to that potentially continuous Checking over the Course of the full Day, the play-by-play 🤖 might point out to `vlčí Sarkofážňik` or notify him that some Habits, in particular, deserve increased Attention today because of long-running Neglect, etc. etc. etc. 2. [ ] Look at & report on also (or *especially*?) the `Habits by Importance` Tab (formerly titled `TSV Export`), not just the main Data-Entry Tab `habits` & the equally crucial Tab `chains` 3. [ ] also crucial: the Tabs `Graf Šťasťia` & `Mapa Šťasťia` 4. [ ] explain the Functionality of Comments within `ROT 2.0` 1. [ ] in the robotic Feedback, *Comments* (at least from the last Day or last few Days) should be considered as well: *both* active *and* resolved Comments (the default State at the End of every Day should be “Inbox Zero”, anyway: *zero* active Comments) 2. [ ] super-exciting AGENTIC Possibilities/future Potential: the play-by-play 🤖 could act as **an Intermediary between `Vďibňík` & `ROT`**, filling in not just the final Happiness Star Ratings Field for me, but also *dozens of others* – based on the Narrative and/or hard Data submitted ***in `Vďibňík`*** (either in the play-by-play thread, or within individual Markdown Entries shared in the thread) 1. [ ] some Cells in today’s column in `ROT 2.0` already *are* filled in automatically (maybe 10 of them – marked with the 🤖 Icon next to the Habit Name), based on Data in other Cells in the same Column 2. [ ] Another **agentic Option**: post *on my Behalf* daily to my Trio of asocial Networks (Facebook + exTwitter + Mastodon) ➡️ 1. [ ] `Wolf(e)ish Report Card / Vlčie Hláseňie` 2. [ ] 🦉 `post-CoD Hoot` 3. [ ] `Pochodapka`’s `Pochod`-Summary Screenshots with literary Quotation attached (& discussed/rebutted by Robots on linked `Webobsedapka` Page) 4. [ ] monitoring any *Reactions* to my Posts in the Trio of asocial Networks (something I regularly fail to keep up with) 5. [ ] see the `Robotapka` dedicated Thread: `Automate Social Posting` ❗❗❗ 3. [ ] Freddy.coach Integrations 1. [ ] `Škridfit`, `Škridľini`, `Elektroprsťeň` & `Chrapapka` seem to work already 2. [x] Jian declined direct Freddy Integration of `Koláčapka` Data for now 3. [ ] asked `Pažrapka` support via in-app chat about lagging Sync via Apple Health 4. [ ] explore `Pochodapka` Freddy Integration Options 2. [ ] Instructions for `Koláčapka` summary analysis 3. [ ] give **average Mood Rating** for the Day (one decimal point) 1. [ ] either via `Náladograf` inside `ROT`, or directly inside the play-by-play thread: that interactive chart throughout the day, or the SVG illustration of the chart, capable of right-mouse-click download. 1. [ ] as also discussed towards the end of pXp Thread for Day 1 of `PIPoSEMWR®` !!! 2. [ ] create custom `ObsePilot` Command to re-check all Mood Ratings from the Course of the Day: both inside pXp Thread & in any referenced individual Markdown files over the course of the day !!! 4. [ ] produce **Summary of `vlčí Sarkofážňik`’s day** in the 3rd person 5. [ ] create `Wolf(e)ish Report Card / Vlčie Hláseňie` (largely based on `ROT 2.0` Values from the Day’s Column, but with *some* Data drawn from `Vďibňík` Entries from the DAy) 6. [ ] try to **guess `vlčí Sarkofážňik`’s Happiness Star-Rating** for the Day 1. [ ] Stress that the crucial, and perhaps the most crucial, criterion for determining the happiness rating for the day is the repeatability of the day. The definition of a three-star day is crucial: "I wouldn't mind if all the days of my life were like this." This frequently determines whether a day can even reach three stars. 1. [ ] The happiness star rating scale alongside the definitions should itself be part of the prompt. 2. [ ] distinguish between Happiness Rating (based on Star *Definitions*!), *holistic* Mood Rating (`ROT` Habit) and average Mood Rating (from individual Mood ratings throughout the Day – *not* weighted) 2. [ ] After discussing the Happiness Star-Rating for the Day, it’s the play-by-play 🤖 himself/herself who, based on `vlčí Sarkofážňik`’ final Decision for the Rating, inserts the Happiness Star-Rating for the Day inside `ROT`, thereby making that Day’s Column fully filled in. ✔️🎉 7. [ ] The ***Play-by-Play Thread* Bullet-List-based *Summary*** (typically produced by `Hĺbkobot`), following the [[Summarize Daily Play-by-Play Thread]] Custom Prompt, is best understood as the **technical broadcast log**: 1. [ ] structured; 2. [ ] highly compressed; 3. [ ] explicit about plans, failures, outputs, and carryovers; 4. [ ] largely bullet-based; 5. [ ] sourced only from the play-by-play conversation. 8. [ ] As opposed to that, the *play-by-play Robot’s* End-of-Day 3rd-person “Kafkaesque” Summary should be the **producer’s cut**: 1. [ ] more narrative and interpretive; 2. [ ] informed by the individual Markdown entries as well as the chat; 3. [ ] incorporating images and specialist reports; 4. [ ] calculating the average mood rating; 5. [ ] estimating the overall happiness star rating; 6. [ ] identifying the day’s central contradiction or turning point. 9. [ ] The two summaries should coexist. `Hĺbkobot` gives you an operational record; the play-by-play 🤖 gives you the high-level account of what the day **meant**. 1. [ ] both robots should double-check the avg. mood rating to 1 decimal point 5. [ ] System-wide instructions updates 1. [ ] Always count on the most absurd potential mistranscriptions by the deaf ŇetipoPisár, so never take whatever is communicated via Vďibňík 3.0 for granted as communicated, because it can always be just a silly mistranscription by ŇetipoPisár. 1. [ ] Especially when a Vďibňík 3.0 entry is not marked as reviewed in the front matter, well, then you must always be on the alert against horrendous ŇetipoPisár mistranscriptions. 2. [ ] Remind the play-by-play robots that whenever they process an individual Vďibňík Markdown file for feedback, they should check off the "submitted to robots" frontmatter property. This way they know, "Yes, I have done this already," and the next time they connect to Majonéza, they can move on to the next entries (if any) that do *not* have that frontmatter property checked off. 6. [ ] re-upload the \[changed] system prompts to `Robotapka`’s project folder sources 1. [ ] likely requires *Deletion* of current Versions & Re-Upload of the updated Versions 2. [x] **==`Koláčapka` Studio== Finishing** ([[Still to Fix in Koláčapka Studio (uq 20260822-Sat-211249)|original Draft]]) 1. [ ] untracked Time ❗❗❗ 2. [ ] **simplify the Input** to **absolute Minimalism** (three Asterisks; no leading Zeros; perhaps even no Percentages ??!!) 3. [ ] change Labels, Button Titles, etc. – make *universal*, not about *me* (remove *Walking* Reference, etc.) 4. [ ] *two* Pictures Upload, not just 1 1. [ ] one Picture: *square* Format *recommended* 2. [ ] the *other* Picture: *Portrait* Format *recommended* 3. [ ] but then how should *landscape* Pictures be handled ??🤔 4. [ ] but uploading **one** Picutre is *enough* – the *second* is only *optional* 5. [ ] implement all the original Observations & Fixes proposed by `Kvintostratég` in the [[2026-08-21 Breakthrough After 15+ Years True-to-Life Daily Koláčapka-Style Piecharts (6a88bea8)|August 21st, 2026 Thread]] 1. [ ] remove fuzzy Blur in the Activities Piechart Donut Hole 2. [ ] Typo in Manual created by `Hĺbkobot` or `Bardoodlebot` 3. [ ] delete Callout (on Imprecision of the Piecharts – **they will now be 100% precise** 🎉👯) from Manual 4. [ ] check faulty Numbering of Items in Manual 5. [ ] publish Version 5.0 of the Manual to `Webobsedapka` ([here](https://avenotes.in.net/convert-atracker-csv-to-obsidian-html) ⬅️ [[(v 4.0) Instruction Manual by Hĺbkobot on Converting Koláčapka's CSV Reports into Obsedapka Color-Coded Tables|local Obsedapka File]]) 3. [ ] ==`Obsedapka` mobile Toolbar Buttons Additions== 1. [ ] create new unique File in current Tab 1. [ ] open new Tab & create new unique File 2. [ ] open new Tab with Launcher & do nothing 3. [ ] open new Tab & launch File-Searcher 4. [ ] display open-Tabs Switcher 5. [ ] Toggle Button creating *exactly this* Type of List employed here in this Roadmap: ***combining*** a **numbered** List with a **Checklist**, or in other Words: a numbered List, but with a Checkbox next to every numbered List Item !!! (the `1. [ ] blablabla` format) 6. [ ] SPEECH BUBBLES 1. [ ] recycle Speech Bubble Colors no. 2, 4, and 6 as Speech Bubbles no. 22, 44, and 66 (but right-aligned) 1. [ ] maybe add *additional* colors (***four*** ?!?!) 1. [ ] so no. 7; 8; 88 (*right*-aligned); 9; 10; 100 (*right*-aligned) 2. [ ] new Script with Popup-Selector Dialogs for *variable* **Speaker** ***AND*** **Bubble Color** ***AND*** **right-or-left** Alignment (these three perhaps *could* be simultaneous & appear on the Screen all at the same Time ??!!) 🤔🤔 1. [ ] in Addition to the 🤖 Options 1 through 10 + 22, 44, 66, 88, and 100, there should be an Option for **`vlčí Sarkofážňik` speaking** (🐺 Speaker Icon instead of the 🤖 Speaker Icon) 1. [ ] and a *third* Speaker Option: `Other…`, where *any* Speaker-Icon & Speaker-Name could be typed in *manually* 7. [ ] Check once again the full custom `Obsedapka` mobile toolbar with all those 200+ custom buttons for any unneeded buttons that could perhaps be removed. 1. [ ] *Especially* look out for **double use of the same icon**: those double icons should be eliminated. For one of the doubled icons, set up a *new* custom icon via the Commander plugin macro workaround. 8. [ ] All the useful `ObseTrubadúr` Commands !!! 4. [ ] reformatting `Robotapka` pXp Threads (or *any* Threads) from automatic Markdown Backup Files **as human-robotic Dialogs** for `Webobsedapka` (**Miyo’s ChatGPT Markdown backup → publishable human–robot dialog for `Webobsedapka`**) 1. [ ] “Konverzia Četu do pekneho Formatovania podľa vzoru z tolstojovského Markdownu” 1. [ ] That's a to-do Item from the old `Vďibňík 2.0` roadmap, except that I no longer remember *which* “tolstojovskí Markdown” may have been referred to here. 😲😮 It must be a Markdown file from around mid-July or late-July 2026. Apparently, the desired formatting of human-robotic dialogs for `Webobsedapka` is ready & finished there. (Including a nice CSS Handling of Time-Stamps, etc.) 1. [ ] So try to remember or locate *which* Markdown file this may have been, and use it as the role model for setting up the reformatting script here for `Vďibňík 3.0`. 1. [ ] I have now found it! 🎊 It's that historic, very first `Vďibňík`-in-`Obsedapka` mammoth entry from that truly historic day, July 27, 2026, titled [[1⁄❓ Bauzeug, Scaffolding, and 10 Days Unwashed᠄ The Architectonic of Migrating Vďibňík to Obsedapka|Bauzeug, Scaffolding, and 10 Days Unwashed: The Architectonic of Migrating Vďibňík to Obsedapka]]. 😂 That is the monumental Markdown journaling entry where I first explained in detail why I'm moving `Vďibňík` away from `Žúrapka` for good and moving it to `Obsedapka`. 2. [ ] There is also the first prototype of a play-by-play thread embedded inside that page with `ObsePilot`'s default paid robot, `Flešbot`. It features the optimal formatting of play-by-play threads for `Webobsedapka`. It's embedded right inside the huge file, which is why it was so difficult to find. The formatting from that particular play-by-play dialog should be implemented in the script so that it can do it automatically on an everyday basis. (Especially the timestamps in two distinct colors look very neat!) 😍 2. [ ] The following Items can be postponed for later (especially no. 2 through 5): 1. [ ] the same Reformatting for `ObsePilot` Chat Threads 2. [ ] ditto for `Robohubka` Chat Threads 3. [ ] ditto for `Bardobot` Chat Threads 4. [ ] ditto for `Hĺbkobot` Chat Threads 5. [ ] ditto for `Grcbot` Chat Threads 3. [ ] Establish a workflow for redacted files: 1. [ ] How to make a copy of them 2. [ ] What template should be used 3. [ ] What link to include at the top to the non-redacted version 4. [ ] etc., etc., etc. 4. [ ] Establish a checklist for the daily wrap-up detailing which files exactly should be included in every individual day folder. 1. [ ] For the landing page, establish the formatting and which components should be there: 1. [ ] Table of contents with links to the individual Markdown files 2. [ ] Link to the play-by-play thread and a summary of it near the top 3. [ ] *Narrative* summary (e.g., by Kvintostratég or Astrabotka) highlighted, potentially outside the play-by-play thread 2. [ ] Ensure nothing will be missing across all daily reports and components: 1. [ ] Kŕmivo report for the day 2. [ ] Koláčapka report 3. [ ] Wolf(e)ish Report Card page 4. [ ] Pohib page 5. [ ] Happiness tracking (*both* the happiness **graph** – a *pair* of them – and the happiness **heatmap**) 6. [ ] Mood chart 7. [ ] ... anything else ?? 3. [ ] There should be a *robotic, automatic* checklist to ensure that every day, when wrapped up, includes all of those components. If any item is unavailable (for example, if there was no movement on that day), there should either be an empty file explicitly stating that, or a note in place of the link indicating there was no movement on that day. 5. [ ] Create a Stable Format for `Vďibňík` Entry *Subtitle*; maybe the one used [[10⁄❓ ➡️ Paradajka by Paradajka᠄ Navigating Monday Mayhem with Šľak Kečup Backslurping Frontloaded|here]] ??!! 6. [ ] Inability of robots and search engines to access `Webobsedapka`; `Šestostratég` says: “When we eventually revisit this under the `Vďibňík 3.0` roadmap, I suggest we treat it as two related but separate investigations: automated access to Obsidian Publish pages and Google search indexing. They may share a cause, but we haven't demonstrated that yet.” 1. [ ] See the latest email reply from Obsidian tech support from late July with suggested next troubleshooting steps with Google's stupid Search Console, etc. 2. [ ] Later, you might want to switch the entire site from avenotes.in.net to avenotes.eu, regardless of whether this access issue gets resolved or not. But avenotes.in.net will remain pointing to the original addresses; it would be set up as a permanent redirect to avenotes.eu. 7. [ ] **`Webobsedapka` Invisibility Issues** for Web Crawlers, Robots, Search Engines, asocial Media Preview Fetchers, etc., etc. etc. ❗❗❗ ➡️ see dedicated `Robotapka` **[Thread](https://chatgpt.com/g/g-p-6a931a10e04881918151e5fd5fc2ffee-building-vdibnik-3-0-revolution/c/6acd1dfd-b8e4-83eb-93c4-999d6a714eb9)** in the `Vďibňík 3.0` Project Folder !!! 5. [ ] ==**`New Vďibňík Entry`** Script== 1. [ ] Copyright below Weather-and-Location Box ??!!; see [[🔒 ❓⁄❓ ➡️ v3᠄ Testing New Header Prototype|v3᠄ Testing New Header Prototype]] 2. [ ] ***Location Precision** Handling* 1. [ ] fetch *precise*, **Street- & House-Level-Precision** Entry Location ***BUT*** apply *known-Place Aliases* such as `vlčí Dom`, `Vinco`, `podzáhradní Vietnamci`, `podunajskí Kaufland`, `autobusoví Lidl`, `biskupické Tesco`, `vlčí Terminál`, `vlčie Internáti`, `pošenskí Lidl`, `Toriská Transit-Hub`, `skorokauflanďia Zastáwka`, `Sunset Street Tram-Stop`, `Telekom HQ Horror Bus-Stop`, `Harbor Bridge Bus-Stop`, `spáľená Zastáwka`, `zajačia Zastáwka`/`Novošampióňi Bus-Stop`, `Šafko`, `central Bus-Station`... 1. [ ] potentially, implement *granular Choice*: 1. [ ] exact Address 2. [ ] Street only 3. [ ] District/City only 2. [ ] For any **non-live** `Vďibňík` entries – *both* in the *regular* `Vďibňík` entries group and in the *special* `Vďibňík` entries group – an *additional* Popup-Selector must run: the Location Popup-Selector, where the options will be: 1. [ ] `current` \[*default*] 2. [ ] `recent` \[*with an additional Popup-Selector Menu of, say, 10 to 15 recent locations*] 3. [ ] `favorit` \[*with an additional Popup-Selector Menu of all saved favorite locations*] 4. [ ] `unknown` \[*this would leave the location for that particular `Vďibňík` Entry blank*] 5. [ ] `withheld` \[*this would leave the location for that particular `Vďibňík` Entry **intentionally** blank*] 6. [ ] `Other…` \[would allow the **manual** Typing-in of any Address or Location*] 3. [ ] fetch the Weather 4. [ ] a SINGLE “Create new `Vďibňík` Entry” Command after all, with multiple successive Popups 1. [x] or could some of the Popup Selectors perhaps even appear *simultaneously*? ➡️ 🤖💃 `Astrabotka` convinced me not to do this 2. [ ] set up new Frontmatter Parameter ??!!: 🤔 `entry_time` 1. [ ] For all those backslurped entries that could occur even days, months, or even years later, `entry_time` could capture the actual time when the entry was created in Vďibňík, regardless of the day and time to which the entry relates. 2. [ ] I think this is *potentially* (?!) different from the default `entry_id` parameter, which should follow the day and time to which the entry is created. At least that's my current impression, because from the `entry_id` parameter, the permalink is also created, and the permalink should definitely point to the day and time to which the entry relates. We can discuss this. 3. [ ] So the current `Yesterday` and `Tomorrow` Options from the second, `Special/Day-Shifted New Vďibňík Entry` Script should be *merged* into a ***single, unified*** `New Vďibňík Entry` Templater Script/Command. 4. [ ] For **all non-live** entries (both *regular* and *special* entries), automatically input the #Retrospective_Entry Tag on the first line of the body of the entry, with a blank line both above & below it. 5. [ ] *4 additional* **regular**-Entry Options need to be added and the final Sequence of Listing of the **7 regular `Vďibňík` Entry Options** could be as follows: 1. [ ] `Live` (*default*) 2. [ ] `Backslurp` (with *Time*-Picker) 3. [ ] `Yesterday` 4. [ ] `Backslurp Yesterday` (with *Time*-Picker) 5. [ ] `Tomorrow` 6. [ ] `Backslurp Tomorrow` (with *Time*-Picker) 7. [ ] `Backslurp Other` (with ***Date***-Picker & *Time*-Picker) 6. [ ] Each of these 7 *regular* `Vďibňík` Entry Types must also (in Addition to *creating all Frontmatter Parameters* as required) correctly update (if needed!) the *Date & Time stated in the Body* of the new `Vďibňík` Entry being created 5. [ ] **Mood-Rating Selector** should be the **second** Popup-Selector right after the initial Entry-Type Popup Selector 1. [ ] add the `?` Option below `1` in the 10-to-1 Mood-Rating Popup-Selector 1. [ ] this is for the `elektricki-brawcomer` Entry Type: I frequently only rate my Mood depending on what Values `elektrickí Brawčomer` deigns to show on that Day – and I typically *don’t know that yet* when *starting* to dictate that `Vďibňík` Entry! 😂 1. [ ] so I will later need to *manually* swap the ❓ with the actual Mood Rating, but that’s OK (*once* a Day…) 6. [ ] **`content-type` Frontmatter Parameter Selector** should be the **third** Popup-Selector following the Mood-Rating Popup-Selector 1. [ ] **potential Content Types** 1. [ ] `general` (default) 2. [ ] `krmivo` 1. [ ] this `entry-type` should insert the **`Krmivo` Taste Rating** Callout automatically in the Body of the `Vďibňík` Markdown Entry 3. [ ] `pochod` 4. [ ] `chrapapka` 5. [ ] `fotograf` 6. [ ] `elektricki_brawcomer` 7. [ ] `human-robotic_dialog` 8. [ ] `tech-prep` 9. [ ] `communication` 10. [ ] `Other…` (allowing manual Entry of an infrequently used `entry-type`) 7. [ ] The **8 special** `Vďibňík` **Entry Types** listed below should *also* appear in the initial Popup-Selector when creating a new `Vďibňík` Entry 1. [ ] (unless we *hide* them behind a `Special…` Menu Item, because those *special* Entries are only created *once per Day*, so it might be useless/too distracting to see them every single Time the `New Vďibňík Entry` Command is activated over the Course of the Day?) 🤔🤔 2. [ ] if *not* hiding them, perhaps a *horizontal dividing Line* in the Popup-Selector Menu between the 7 *regular* `Vďibňík` Entry Types (listed above) & the 8 *special* Types (listed below) should appear ??!! 🤔 3. [ ] Whenever one of these *special* `Vďibňík` Entry Types is selected, then the `entry-type` *Frontmatter Parameter* Popup-Selector would be **skipped** because it would be selected *automatically*. 4. [ ] Don’t forget that every special-Type `Vďibňík` Entry must likewise include a *valid* `entry-id` Frontmatter Parameter (so that the Footer Navigation-Links Creation Script later works as intended) 1. [ ] `permalink` must also be created automatically 5. [ ] Each of the ***8 special*** `Vďibňík` Entry Types listed below should come with ***follow-up Popup-Selector** Options*: 1. [ ] `for Yesterday` (*default* Option; “yesterday” being relative to the Entry’s Creation in real Time) 1. [ ] `Live` (*default*) 2. [ ] `Other…` (provide ***Date** & Time*-Picker) 2. [ ] `for Today` (“today” being relative to Entry’s real Creation-Time) 1. [ ] `Live` (*default*) 2. [ ] `Other…` (provide *Time*-Picker) 3. [ ] `Other...` (provide ***Date & Time***-Picker) 6. [ ] Listing of the 8 Special <code>Vďibňík</code> Content Types 1. [ ] Pohib Summary 2. [ ] Pažrapka Summary 3. [ ] Koláčapka Report 1. [ ] prominently state the **actual length of day** somewhere towards the top of this page 2. [ ] `LT`, `DN` 4. [ ] pXp (the Day’s play-by-play Thread) 5. [ ] pXp Summary (created by a different 🤖 than the one active in the pXp Thread itself) 6. [ ] Šťasťie Report 7. [ ] Wolf(e)ish Report Card 1. [ ] update the [[Template᠄ Wolf(e)ish Report Card ⁄ vlčie Hláseňie|Template/Sample from May 1st, 2026]], by, for example, incorporating the two recently introduced `Krmivo` Rating Types (*Star*-based **Taste** Rating & *Point*-based, interpretative **Reasonableness** Rating) !!! 1. [ ] Move the specific link to the day's landing page towards the top of the report card: probably line 2 would be the proper place. 8. [ ] landing Entry for the Day = Top `Webobsedapka` Menu Item of the Day Folder’s File-Tree; also the Link included in every `Wolf(e)ish Report Card / Vlčie Hláseňie` posted daily to the Trio of asocial Networks 1. [ ] prominently state the **actual length of day** somewhere towards the top of this landing page 7. [ ] Each of these 8 *special* `Vďibňík` Entry Types has its own Template (that, for Example, includes what the special `Vďibňík` Entry’s **Title** should be, the invariable *Structure* of the Permalink, etc.), so the special `Vďibňík` Entry should be created following *that* specific Template for *that* specific special `Vďibňík` Entry Type 6. [ ] Is there still anything left from the [[❓⁄❓ ➡️ Old, Disorganized Vďibňík 2.0 Roadmap – But May Still Contain Some Bits Useful for Vďibňík 3.0|old Vďibňík 2.0 Roadmap]] that should be implemented in `Vďibňík 3.0`? 1. [ ] Transfer any items from the `Vďibňík 2.0` roadmap that are *still useful* but not necessarily needed for `Vďibňík 3.0`, for later Processing to the endless & bottomless Silo of Tasks-to-do-later in the [[for AveNotes]] file.