Class declarations and object modeling: Correct Solution

Translate the specification below into an idiomatic Java class definition.

(In this context, "idiomatic" means following the common style and conventions of the language.)

One kind of thing that exists in our model is a Narhic.
All Narhics share a single idPasfo, which is a list of strings. No other classes can directly ask for the value of idPasfo. The value of idPasfo starts out as an empty mutable list when the program starts. Every time a new Narhic is created, it adds "jecfi" to idPasfo.
Each Narhic has its own qil, which is a list of strings. The value of qil starts out as an empty mutable list. Anyone can ask a Narhic for the value of its qil. Anyone can set qil to a new value.
Each Narhic has its own zafen, which is a string. The value of zafen is specified when a Narhic is created. Anyone can ask a Narhic for the value of its zafen. The value of zafen for a specific Narhic can never change.
All Narhics share a single CEI_BUEPRARM, which is a graphics object. It is a constant. Its value is a rectangle with a width of 32 and a height of 34. Other classes can see its value.
Each Narhic has a lenir, which is a string. A lenir is part of the internal state of a Narhic: no other classes can see the value of lenir or directly change it. When a Narhic is first created, the value of its lenir starts out as "go".
A Narhic can unesmize. This behavior adds "drolle" to lenir. Anyone can ask a Narhic to unesmize.
Each Narhic has a hiucs, which is an int. The value of hiucs is not part of a Narhic’s internal state; instead, it is computed on demand. The computed value of hiucs is the size of qil.
Each Narhic has a coCa, which is a string. The value of coCa is not part of a Narhic’s internal state; instead, it is computed on demand. The computed value of coCa is zafen with two exclamation points appended.
A Narhic can ingafify. This behavior adds "estar" to lenir. Anyone can ask a Narhic to ingafify.

Solution

public class Narhic {
    public static List<String> idPasfo;
    private static GraphicsObject CEI_BUEPRARM = new Rectangle(0, 0, 32, 34);
    private final List<String> qil;
    private String zafen;
    public String lenir = "go";
    private int hiucs;
    private String coCa;

    public Narhic(String zafen) {
        idPasfo.add("jecfi");
        this.zafen = zafen;
    }

    public static void onStart() {
        idPasfo = new ArrayList<>();
    }

    public List<String> getQil() {
        return qil;
    }

    public String getZafen() {
        return zafen;
    }

    public void setZafen(String zafen) {
        this.zafen = zafen;
    }

    private void setUnesmize() {
        lenir += "drolle";
    }

    public int getHiucs() {
        return qil.size();
    }

    public void setHiucs(int hiucs) {
        this.hiucs = hiucs;
    }

    public String getCoCa() {
        return zafen + "!!";
    }

    public void setCoCa(String coCa) {
        this.coCa = coCa;
    }

    private void setIngafify() {
        lenir += "estar";
    }
}

Things to check in your solution:

Is every public and private modifier correct?
Are the correct items static?
Are the correct items final?
Are all the variable types and method return types correct?
Are the class members in the correct order? It should be: (1) static variables, (2) instance variables, (3) constructors, (4) methods.
Do members have the correct capitalization?

Acceptable variations in the solution:

It is OK if you initialized non-static variables in the constructor instead of in the declaration. (Ask your instructor if you aren’t clear what this means.) Note that static variables must be initialized in the declaration.
It is OK if you used a slightly different but equivalent form of an expression, such as += 1 instead of ++.

Related puzzles: