1.9.6

• What a run makes says its version: the foot of the map, the RH and the stage («cast-list 1.9.6»), their
  generator tag, and the cast file (# Written by cast-list 1.9.6., renewed on every run), so two runs can be told
  apart.
• A topic that begins a connected agent (<schema>.InvokeConnectedAgentTaskAction.<Name>) is checked against
  the agent's actions — in actions/, topics/, or a file of agents/, where the extension clones them — and not
  reported as a topic not found. Any <schema>.<type>.<Name> other than a topic is read the same way.

1.9.5

cast-list, the second run on a real cast (22 files «not understood», down from 96).

• Flows whose jsonFileName is a path (workflows/<folder>/workflow.json, as the extension writes it) are read: the
  file was looked for by the whole path. The rest of those flows' names, connectors and callers come back with them.
• A topic that begins an action (<schema>.action.<Name>) is checked against the agent's actions, not its topics.
  One not found is named in full, so an action of another agent's prefix (copied from another agent) shows as such:
  «Chama a ação (não encontrada) …».
• A call without a prefix keeps its whole name: it showed only its last letter («Chama o tópico (não encontrado) s»).
• The cast cards no longer spill: a long path or a GUID wraps inside its card, and a file «not understood» twice
  for the same reason shows once, with ×2.

1.9.4

cast-list on agents cloned by the VS Code extension on Windows, after a run on a real cast left 96 files «not
understood».

• Flows are read again: a workflow.json saved with a byte-order mark (Windows) did not parse, so every flow was
  lost — its name, its connectors and operations, who calls it. Every file now drops the mark before it is read. The
  name comes from name in metadata.yml, and a folder ending in a whole GUID gives the flow's short name.
• Uploaded knowledge counts: each knowledge/files/*.mcs.yml (only its metadata) is a knowledge source
  («Conhecimento em arquivo enviado»); the document beside it and the agent's icon.png are not read and no longer
  show as «not understood».
• connectionreferences.mcs.yml without a kind is known by its name, as cloned, so the access review has its
  connections.
• «Not understood» says why in the cast card too, as the sheet does (a telemetry event whose name is a formula).
• The example agents are cloned the same way: flows with a byte-order mark and a GUID folder, a real metadata.yml,
  connection references without a kind, an icon each.

house-lights 1.9.3

• The résumé says where each fact came from: team, owner, hiring, publishing and environment carry their source
  (inventario.csv › linha 6) in small letters under the value, as the sheet does beside it.
• The stage's arrow labels never sit on a node, with a lens or without; with a lens, only the arrows that touch
  someone it lights say something.
• Short names in the follow spot too: its buttons and its steps say «O orquestrador encaminha para Frete». One rule
  for the shared part of the names (shortNames) serves the stage, its scenes and the RH.

house-lights 1.9.2

• The RH's résumé has two views: as a résumé — the paper one of the prototype, with a face, the name, the post and
  the stamp on top, the facts in two columns and the sources at its foot — and as the sheet, every field with its
  source beside it. It opens as a résumé; one click turns it.

house-lights 1.9.1

cast-list's RH and stage, after a test in claude.ai.

• The RH's org chart shows one of two types once, in its first, with «also orientação»; the staff board, the org
  chart and the stage leave out the part of the names every one shares («Bodega Azul - »), and the one not in the
  folder is no longer cut.
• The stage: a lens closes the scene and a scene turns the lens off; the follow spot is the size of the node; the
  caption sits below the stage, never over it; knowledge sources are on stage and in the scenes («Consulta
  «Conhecimento no SharePoint»»).
• Connectors by name: when the files give none (a flow's connection names only the API), a common Microsoft
  connector goes by Microsoft's name — shared_commondataserviceforapps is «Microsoft Dataverse».
• The post's requirements: a fact whose name is already a sentence is said as it is («Recebe «X» do
  orquestrador»), not inside «Tem «…»».
• The example evaluations are named in kebab-case (evaluate-bodega-azul-pedidos-2026-10-30.csv); the name the
  Evaluate tab gives, with spaces, reads the same.

house-lights 1.9.0

cast-list reads the evaluations and reviews the access.

• --evals <folder> reads the exports of Copilot Studio's Evaluate tab («Evaluate .csv»): who is
  named by the file, a row passes when every method passes, each method counted. The counts only: what was asked,
  answered and explained is the client's conversation and never reaches an output. The résumé gets «Certifications»,
  the staff board «with no evaluation», and who has one gets eval:run, so a rule has: "eval:*" asks for it. A file
  that names nobody, or is not an export, is told and left out.
• The review of access: within each type of two or more, a connector, an MCP server or what a flow reaches that
  only one has is asked about on the résumé and the stage's card — does the post need it? With a decision rejected
  on that key in the type's scope, it becomes a cleanup item of the plan.
• The examples get two exports of the Evaluate tab (examples/avaliacoes/), written by the fixtures' generator.

house-lights 1.8.0

cast-list puts the cast on a stage.

• --plot (in --all too) writes <id>.plot.html: the light plot, to show in a meeting. The customer, the
  orchestrators, the specialists by type, the flows (one node however many share one) and the systems they reach, in
  columns; the same run gives the same stage.
  • The traffic: dots along the arrows, as many as the log of each one's topic starts in the export; the arrows
    into flows and systems are structure, never a measured volume; one with no line in the telemetry has a dashed
    arrow and «no telemetry». With reduced motion, nothing moves.
  • The arrows say what is wrong: «NO history · NO «Category»» in red, «routed by «Coupons.»» in amber, «returns
    nothing», «calls it, but it is not in the folder»; a flow nobody calls, and what only it reaches, dashed.
  • Lenses: the accepted patterns and the first ones someone is off, then Contract, Telemetry and Unused — who
    follows lights green, who is off blinks red, what is to decide shows amber.
  • The follow spot: one scene per call of the orchestrator; ← → walk it, space plays it, Esc leaves; it stops
    where the call breaks.
  • The actor's card: the fingerprint of its instructions (shared blocks, a variation, its own text) and what it
    meets of its post, with its résumé a link away (the RH opens at #<id>).
• The map links to the stage when the same run wrote it.

house-lights 1.7.0

cast-list writes the RH of the cast.

• --playbill (in --all too) writes <id>.playbill.html: the same cast as people, for whoever thinks in HR
  terms. Everything comes from the files, the telemetry and the tables people gave; a field nothing says stays empty.
  • The staff board: on the staff, being hired (called and not in the folder, or in another environment), with no
    owner and never published (with the inventory), with a development plan, in good standing — each with the names.
  • The org chart by type, and the post of each role and type: the accepted patterns and the profile's rules,
    as requirements; with no decision yet, a proposal.
  • A résumé each: the first sentence of its instructions, its manager, team, owner, hiring and publishing dates,
    tools, conduct, goal, and the performance from the telemetry (topic starts, errors logged, what did not fire).
  • The development plan (PDI): what «to look at» says about that one alone, as actions — one item per fact, the
    inputs the orchestrator does not pass in one call as one. A solo, a type with one and a marker set in ways across
    the cast are the team's call, not anyone's plan. references/playbill.md says how each part is read.
• The workbook gets the Staff and PDI sheets; the map links to the RH when the same run wrote it.
• Two keys for who answers for it: the team spreadsheet's «Dono», «Equipe», «Squad» give declared:team; only
  the inventory's Owner gives declared:owner (until 1.6, «Dono» was the owner).

house-lights 1.6.0

cast-list's «to look at» comes in groups.

• Groups, each with how many: Contradictions · Contract and telemetry · Off pattern · Rules · Only one has it ·
  Unused · Not understood — in the command's output (a ▸ line per group; every finding keeps its ! line), at the
  top of the map and in the workbook's summary. One list decides them, so the three always agree.
• The map folds «Only one has it» and «Unused» at first: they are many and rarely urgent; a click opens them. A rule
  not met now comes after what is off a pattern, with its own group.