org.eolang.cage must prohibit different object "types"

[yegor256]

The cage object must return an error if we try to .write an object that is not a copy of the abstract object that was saved before.

[yegor256]

@Graur please, help

[yegor256]

@maxonfjvipon please, help

[maxonfjvipon]

@yegor256 please have a look at this.

[x] > obj
  x > @
obj 1 > obj1

# Case 1
cage obj > cg
cg.write obj1

# Case 2
cage obj1 > cg
cg.write obj

1. Init cage with abstract object obj then write its copy obj1 with bounded x
2. Init cage with copy (of obj) obj1 then write abstract obj

Should these both cases be legal in scope of the task?

[yegor256]

@maxonfjvipon both cases should be illegal, in my opinion

[0pdd]

@yegor256 2 puzzles #2335, #2336 are still not solved.

[0pdd]

@yegor256 2 puzzles #2335, #2373 are still not solved; solved: #2336.

[0pdd]

@yegor256 the puzzle #2373 is still not solved; solved: #2335, #2336.

[0pdd]

@yegor256 all 3 puzzles are solved here: #2335, #2336, #2373.