Beaver's path — a starter widget for an Eolymp widget problem
=============================================================

Upload this folder, zipped, in the console: Problems -> your problem -> Widget.

  index.html   the page Eolymp loads
  task.js      the widget itself; read this one first
  grid.js      a second script, loaded before task.js by index.html
  style.css    styling, loaded by a relative path like any other file
  beaver.png   an image, addressed the same way
  client.js    the Eolymp client — the widget half of the protocol

Every file is addressed relative to index.html, so ./style.css, ./grid.js and
./beaver.png all work, and folders are kept as they are: ./img/beaver.png would
be fine too.

client.js is copied into the bundle rather than linked. A bundle is served with
a policy that allows scripts from the asset host alone, so a widget cannot load
one from anywhere else. For the same reason the scripts here are plain scripts,
not ES modules.

The answer
----------

  { "cells": [[1,0,0,0],[1,1,0,0],[0,1,1,0],[0,0,1,1]] }

1 marks a cell the beaver swims through, in reading order, four rows of four.

Grading it
----------

A widget problem has no tests. It is worth 100 points, and a checker program
scores it: the answer arrives as output.txt, and the checker holds whatever the
task expects. Compare the two as JSON rather than as text, since key order and
spacing carry no meaning.

There is a worked checker in the documentation:

  https://support.eolymp.com/console/problems/widget
